You are not logged in.
Pages: 1
I created an Arch SSO account, verified my email and sent an email to the specified address to have my account allowlisted, but have not gotten a response other than the automated one in a week's time. Does it usually take a while for this to happen or did my request get overlooked?
Offline
For me it's been 2 weeks. I guess we should wait.
---
Offline
If you've details on a bug I'll file it for you.
Offline
If you've details on a bug I'll file it for you.
It's not related to a bug at all. I was mainly wanting to weigh in on the discussion about the forum on GitLab.
Offline
Offline
Yes, that's the one.
Offline
Hello,
same for me, I also created an Arch SSO account a week ago and I am still waiting for the allowlisting. The long waiting period seemed unusual, so I searched how to contact someone about this and found this thread while doing so.
Two weeks like 5hridhyan mentions seems quite long to me, is Staff aware about this or is there a known issue?
(I have a regression on my system with kernel 6.19 and wanted to make a bug report)
Offline
I'm not defending the ridiculous gitlab account situation, but if there's a bug in the kernel, you should file a bug report on the kernel bug tracker. Filing a bug against the Arch Linux package is unlikely to accomplish much.
Sakura:-
Mobo: MSI MAG X570S TORPEDO MAX // Processor: AMD Ryzen 9 5950X @4.9GHz // GFX: AMD Radeon RX 5700 XT // RAM: 32GB (4x 8GB) Corsair DDR4 (@ 3000MHz) // Storage: 1x 3TB HDD, 6x 1TB SSD, 2x 120GB SSD, 1x 275GB M2 SSD
Making lemonade from lemons since 2015.
Offline
What's the nature of the regression specifically?
As WorMzy pointed out, unless it's explicitly a packaging bug or a problem with the few downstream patches or you want to pitch cherry-picking an upstream patch you'll have to report that upstream.
So we could check whether this is a known issue before you get eaten alive on lkml ![]()
Offline
Thanks for answering,
depending on how you read the docs, there is no right answer for this: Arch says report upstream, kernel.org says report to your vendor. So if I get chewed out either way, I guess I start at Arch ![]()
The nature of the regression is a non-working graphical environment (Xorg). It seems it's got to do with a change how the 6.19 kernel uses drivers for AMD graphics. The problem is reproducible with installing a 6.19 kernel, no other changes were made. I guess I'll create a thread so I don't hijack this one.
Offline
Check "uname -a" for whether you're actually booting the 6.19 kernel (the most common cause of described symptoms)
When opening a new thread please post your complete system journal for a 6.19 boot:
sudo journalctl -b | nc termbin.com 9999and your Xorg log, https://wiki.archlinux.org/title/Xorg#General after failing to start X11
Offline
Pages: 1