You are not logged in.
About 3 out of 5 logins I only have a black screen with an X cursor at the bottom right. I have already deactivated all extensions, reactivated individually. But no luck. I can't find a pattern.
I have already deleted the /etc/X11/xorg.conf that I created myself. it didn't help either. I have now created it again.
What always helps is to switch to a virtual console, restart gdm with systemctl restart gdm.service, switch back to gdm and then the login works. GNOME starts.
I'm scratching my head right now. At the moment I really don't know what to do next.
uname -a
Linux elysion 6.7.6-arch1-1 #1 SMP PREEMPT_DYNAMIC Fri, 23 Feb 2024 16:31:48 +0000 x86_64 GNU/Linuxgnome-shell --version
GNOME Shell 45.4Last edited by freanux (2024-04-20 07:44:34)
Offline
I had the same problem, in this thread we discussed it, maybe it could help, if not, sorry.
https://bbs.archlinux.org/viewtopic.php?id=293112
// Edit: Wait, I was too fast, looks like you are on X11 and it happens, we had this problem with Wayland, are you on Nvidia?
Last edited by micronetic (2024-02-24 15:16:59)
Offline
Thanks for quick reply.
Yes, I am on X11 and NVIDIA. And this problem is relatively new.
EDIT:
Graphics Processor: NVIDIA GeForce RTX 4070
NVIDIA Driver Version: 545.29.06
Last edited by freanux (2024-02-24 15:35:04)
Offline
Thanks for quick reply.
Yes, I am on X11 and NVIDIA. And this problem is relatively new.EDIT:
Graphics Processor: NVIDIA GeForce RTX 4070
NVIDIA Driver Version: 545.29.06
This is funny because on Xorg I had no problems after GDM login, but problems with Wayland.
I hope someone with more knowledge comes here because I am no help here :-( sorry
Offline
Get rid of the simpledrm device by enabling KMS on nvidia: https://wiki.archlinux.org/title/NVIDIA … de_setting -- note to explicitly use the kernel parameter variant, not the modprobe one.
Offline
Get rid of the simpledrm device by enabling KMS on nvidia: https://wiki.archlinux.org/title/NVIDIA … de_setting -- note to explicitly use the kernel parameter variant, not the modprobe one.
I have used the kernel parameter variant for almost 2 years and the stuff came out of nowhere with GDM not able to login to Wayland. But it looks like the latest Nvidia/Kernel update fixed it? I don't know but I am able to get in the Wayland session again.
The most funny part was that the dash changed to underscore:
from
nvidia-drm.modeset=1to
nvidia_drm.modeset=1Last edited by micronetic (2024-02-24 17:03:45)
Offline
Thanks V1del.
In fact, I tinkered with these settings to get Wayland to work. But in my daily production environment, Wayland is currently not an option for many reasons. So I switched back to X11. But I guess I didn't reset all the settings. So now it looks like this:
$ cat /proc/cmdline
BOOT_IMAGE=/vmlinuz-linux root=UUID=b36971be-9d14-4475-8ca3-7d0e9425073b rw loglevel=3 quiet nvidia_drm.modeset=1and
# cat /sys/module/nvidia_drm/parameters/modeset
YBut no luck. As before, GNOME still gets stuck after GDM login.
New logs:
http://0x0.st/H5D7.txt
EDIT:
As previously. It doesn't always stick. But about 3 out of 5 login attempts.
Last edited by freanux (2024-02-24 17:07:15)
Offline
Thanks V1del.
In fact, I tinkered with these settings to get Wayland to work. But in my daily production environment, Wayland is currently not an option for many reasons. So I switched back to X11. But I guess I didn't reset all the settings. So now it looks like this:
$ cat /proc/cmdline BOOT_IMAGE=/vmlinuz-linux root=UUID=b36971be-9d14-4475-8ca3-7d0e9425073b rw loglevel=3 quiet nvidia_drm.modeset=1and
# cat /sys/module/nvidia_drm/parameters/modeset YBut no luck. As before, GNOME still gets stuck after GDM login.
New logs:
http://0x0.st/H5D7.txtEDIT:
As previously. It doesn't always stick. But about 3 out of 5 login attempts.
Seth told me this is the stuff which is killing it (You're for some reason using libEGL_mesa and that derails wayland and X11 alike.) the libEGL_mesa
Offline
After updating to GNOME 46, this issues seems to have dissappeared. Even after restarting several times everything is fine. I still have no idea what the actual problem was. I'm setting this topic to SOLVED.
Offline