[SOLVED] Stuck on GNOME Login Screen

iceeburr · 2023-07-29 10:26:25

Today I woke up to find myself stuck on the login screen. In simple terms, once you enter your password and hit enter, you see a black screen for a few seconds, and then it sends you back to the login screen. You also see that black screen when you try to actually log in, but when it works, it just works and lets me into the system. For me, though, nothing really worked out. I tried to find answers on my phone and stumbled across a similar problem, but the error is different from mine. I tried to search for my specific error, but I couldn't find anything that solved the issue. Other people have had it before. The full logs will be below in the pastebin. I tried to update my system after this bug happened; there were some updates, but still, after that, I have this issue. I tried many different solutions; none of them worked, and chatGPT couldn't help either. Any help will be really appreciated. If I'm wrong about anything, please correct me. I do want to note that if I pick "Gnome on Xorg" on the login screen, it all works fine, so this is an issue with Wayland.

Short logs: (what I suppose is the root cause)
Failed to setup: Unable to initialize the Clutter backend: no available drivers found.
org.gnome.Shell@wayland.service: Failed with result 'protocol'.
https://pastebin.com/q8r47Hi4
Full logs: (everything)
https://pastebin.com/CNjAYrGK

If you need more information, please ask.
I do have access to my system on Xorg, but I don't really want to use it or reinstall my whole system. I hope this can be fixed without a lot of struggle. Thanks in advance for any help.

Last edited by iceeburr (2023-07-29 21:34:05)

iceeburr · 2023-07-29 11:27:26

Temporary fixed, last resort solution. [Not Solved!]

A friend of mine told me to try to make another user account and set a password. I tried it, and I can log into the system on Wayland. This will be my last resort (copy dotfiles and stuff to a new user account and delete the old one).

This is a temporary last-resort solution, and I have not solved the main issue. If I had the issue once, it would probably appear again. Getting a new user account is very painful since I will also have to remember every single config file that I have changed and also change it there. This also means that I will probably encounter this issue again. A thing I noticed is that apps don't work on the new user account, probably because I haven't done anything to it; quite literally, I just added a new user and set a test password.

The file explorer errors, and it has a visual bug like flashing black colors all over the place. I'm pretty sure that can be fixed by just setting up the user properly.
If I don't find another proper solution, I will do this. If even that doesn't work, then I guess a full system reset would do its thing.

seth · 2023-07-29 12:48:31

I do want to note that if I pick "Gnome on Xorg" on the login screen, it all works fine, so this is an issue with Wayland.

You've a hybrid graphics setup, see https://wiki.archlinux.org/title/GDM#Wa … DIA_driver and I suspect supergfxd is relevant here, but the entire head of the "full logs" is missing, so it's hard to tell why the GPUs show up in the wrong order.

Either way it leads to

Jul 29 12:08:10 ice-arch gnome-shell[1164]: Running GNOME Shell (using mutter 44.3) as a Wayland display server
Jul 29 12:08:10 ice-arch gnome-shell[1164]: Device '/dev/dri/card0' prefers shadow buffer
Jul 29 12:08:10 ice-arch gnome-shell[1164]: Added device '/dev/dri/card0' (nvidia-drm) using atomic mode setting.
Jul 29 12:08:10 ice-arch gnome-shell[1164]: Failed to detect hardware rendering: eglMakeCurrent(): An EGLDisplay argument does not name a valid EGL display connection.
Jul 29 12:08:10 ice-arch gnome-shell[1164]: Device '/dev/dri/card1' prefers shadow buffer
Jul 29 12:08:10 ice-arch gnome-shell[1164]: Added device '/dev/dri/card1' (amdgpu) using atomic mode setting.
Jul 29 12:08:10 ice-arch gnome-shell[1164]: Enabling experimental feature 'scale-monitor-framebuffer'
Jul 29 12:08:10 ice-arch gnome-shell[1164]: Failed to initialize accelerated iGPU/dGPU framebuffer sharing: An EGLDisplay argument does not name a valid EGL display connection.
Jul 29 12:08:10 ice-arch gnome-shell[1164]: Created gbm renderer for '/dev/dri/card0'
Jul 29 12:08:10 ice-arch gnome-shell[1164]: Failed to initialize accelerated iGPU/dGPU framebuffer sharing: Not hardware accelerated
Jul 29 12:08:10 ice-arch gnome-shell[1164]: Created gbm renderer for '/dev/dri/card1'
Jul 29 12:08:10 ice-arch gnome-shell[1164]: GPU /dev/dri/card0 selected as primary
Jul 29 12:08:10 ice-arch gnome-shell[1164]: Failed to setup: Unable to initialize the Clutter backend: no available drivers found.

So elaborate on your approach to the hybrid system and post the *entire* journal.

The file explorer errors, and it has a visual bug like flashing black colors all over the place

I'm pretty sure this is the result of the altered GPU setting that allows you to run on wayland w/ that user itfp…

iceeburr · 2023-07-29 13:31:01

Here is the full log. (I hope it is)
https://pastebin.com/heBVJtJ4
Also I added that parameter in my grub config, but still nothing. Everything was working the day before and only now it broke, thanks for your suggestion, but I have already tried it. I have the "WaylandEnable=true" line in my gdm config, I have also tried to remove it (comment), set it to false, etc. but nothing..

seth · 2023-07-29 13:53:34

What parameter in your grub config? "nvidia-drm.modeset=1"?
Did you notice the part where you mask a udev rule and enable https://download.nvidia.com/XFree86/Lin … ement.html ?

your suggestion, but I have already tried it

What suggestion are you referring to here?
supergfxd is still in the logs

seth wrote:

elaborate on your approach to the hybrid system

And again: nvidia loads significantly before amdgpu.

Everything was working the day before and only now it broke

And what did you do inbetween?

iceeburr · 2023-07-29 14:54:22

1. Yes, I set it to that; it looks like this: GRUB_CMDLINE_LINUX_DEFAULT="loglevel=3 quiet nvidia-drm.modeset=1"
I have also added this to my /etc/mkinitcpio.conf: MODULES=(btrfs nvidia nvidia_modeset nvidia_uvm nvidia_drm). I did not forget to run mkinitcpio after updating.
2. I have installed most of the driver packages for both Nvidia and AMD cards. My laptop is the rog strix g17 with an AMD cpu and an integrated Radeon card, and my dedicated GPU is the nvidia rtx 3070 ti. I have the asusctl package for ASUS laptop support.
3. The last thing that did something with system files was me trying to get OBS's (open broadcast software) virtual camera feature to work. I followed several guides online, one of which is here:
https://gist.github.com/kiryasolod/4f9e … 4f216cc4fc
It uses the v4l2-loopback package.
I actually noticed a small warning, which was after "Failed to setup: Unable to initialize the Clutter backend: no available drivers found," regarding something from wireplumber that didn't exist. I remember that I set it up on dev/video10.
I thought that was the issue since it came right before the gnome error and it was in yellow and not white like the clutter fail. I reversed all the changes that I made and removed the packages I used; that warning is gone, and /dev/video* is no longer there. I don't have any other video input devices (I never had any). This is the last thing that I did before it broke. I don't remember if I restarted my computer or not during that time, but probably not; otherwise, I would have probably gotten this issue that I have now. I doubt it's actually because of this, but who knows?
I have used this laptop with many distributions, even with Hyprland, and there I had no issues with it; everything was fine. This is the first major issue I have come across. Usually I solve them with a few Google searches, or AI comes in to do the searching for me, but this exact issue seems to be hardware-based, I guess since no one has the "exact same" issue as me, but only similar errors.

seth · 2023-07-29 15:23:13

Remove the nvidia modules from the initramfs again and add amdgpu instead, disable supergfxd and post a journal that covers a login by your alternate user as well as a complete Xorg log to illustrate your HW and output config.

iceeburr · 2023-07-29 17:58:34

I did that as you said. Here are the exact steps I took: (In case I did something wrong, correct me.)

sudo systemctl disable supergfxd
sudo nano /etc/mkinitcpio.conf
Removed anything related to Nvidia in MODULES= and added amdgpu
Saved
sudo mkinitcpio -P
Reboot
I tried logging into my main profile with my Gnome profile (Wayland).
I tried logging into my main profile with my Gnome Xorg profile.
Logged out
I tried logging into the test account with Wayland.
tried logging into test with xorg
Now here's where it gets interesting: on my main profile, I can't login into Wayland.
but on my test profile, I can't login to Xorg. I have the same issue when I try to login to Xorg on my test profile. It's like it got flipped, but I'm pretty sure that this is probably some problem with missing dependencies or files on the test profile since I haven't done any configuration on it.
Even after this, still nothing, except that I found I couldn't get into an Xorg session on the test account.
Here are the logs: (The files were too big for Pastebin, so I had to upload them somewhere else.)
Journalctl Full log
https://cdn.discordapp.com/attachments/ … 696996.txt
Xorg.0.log
https://cdn.discordapp.com/attachments/ … 696996.log
I hope we can get to the root cause of this. Thanks again for any suggestions you gave me.

seth · 2023-07-29 20:25:36

X11 is running on the AMD chip (now) and that's also where the only output is attached (so that's good, the nvidia chip is sidelined and irrelevant here)
You might want to get rid of any xf86-video-* package.

The test users X11 session fails because of

Jul 29 19:58:19 ice-arch /usr/lib/gdm-x-session[3629]: (EE) Cannot open log file "/home/test/.local/share/xorg/Xorg.pid-3629.log"

Did you forget to add a $HOME to the user?

otoh, "test" has no issues w/

                                    Jul 29 19:58:00 ice-arch gnome-shell[2583]: Device '/dev/dri/card1' prefers shadow buffer
                                    Jul 29 19:58:00 ice-arch gnome-shell[2583]: Added device '/dev/dri/card1' (nvidia-drm) using atomic mode setting.
                                    Jul 29 19:58:00 ice-arch gnome-shell[2583]: Device '/dev/dri/card0' prefers shadow buffer
                                    Jul 29 19:58:00 ice-arch gnome-shell[2583]: Added device '/dev/dri/card0' (amdgpu) using atomic mode setting.
                                    Jul 29 19:58:00 ice-arch gnome-shell[2583]: Created gbm renderer for '/dev/dri/card1'
                                    Jul 29 19:58:00 ice-arch gnome-shell[2583]: Created gbm renderer for '/dev/dri/card0'
                                    Jul 29 19:58:00 ice-arch gnome-shell[2583]: Boot VGA GPU /dev/dri/card0 selected as primary
                                    Jul 29 19:58:00 ice-arch gnome-shell[2583]: Obtained a high priority EGL context
                                    Jul 29 19:58:00 ice-arch gnome-shell[2583]: Obtained a high priority EGL context

where ice-arch struggles

                        Jul 29 19:57:25 ice-arch gnome-shell[1164]: Running GNOME Shell (using mutter 44.3) as a Wayland display server
                        Jul 29 19:57:25 ice-arch gnome-shell[1164]: Device '/dev/dri/card1' prefers shadow buffer
                        Jul 29 19:57:25 ice-arch gnome-shell[1164]: Added device '/dev/dri/card1' (nvidia-drm) using atomic mode setting.
                        Jul 29 19:57:26 ice-arch gnome-shell[1164]: Failed to detect hardware rendering: eglMakeCurrent(): An EGLDisplay argument does not name a valid EGL display connection.
                        Jul 29 19:57:26 ice-arch gnome-shell[1164]: Device '/dev/dri/card0' prefers shadow buffer
                        Jul 29 19:57:26 ice-arch gnome-shell[1164]: Added device '/dev/dri/card0' (amdgpu) using atomic mode setting.
*****************************************************************
Jul 29 19:57:26 ice-arch gnome-shell[1164]: Enabling experimental feature 'scale-monitor-framebuffer'
*****************************************************************
                        Jul 29 19:57:26 ice-arch gnome-shell[1164]: Failed to initialize accelerated iGPU/dGPU framebuffer sharing: An EGLDisplay argument does not name a valid EGL display connection.
                        Jul 29 19:57:26 ice-arch gnome-shell[1164]: Created gbm renderer for '/dev/dri/card1'
                        Jul 29 19:57:26 ice-arch gnome-shell[1164]: Failed to initialize accelerated iGPU/dGPU framebuffer sharing: Not hardware accelerated
                        Jul 29 19:57:26 ice-arch gnome-shell[1164]: Created gbm renderer for '/dev/dri/card0'
                        Jul 29 19:57:26 ice-arch gnome-shell[1164]: GPU /dev/dri/card1 selected as primary
                        Jul 29 19:57:26 ice-arch gnome-shell[1164]: Failed to setup: Unable to initialize the Clutter backend: no available drivers found.
                        Jul 29 19:57:26 ice-arch systemd[1073]: org.gnome.Shell@wayland.service: Failed with result 'protocol'.
                        Jul 29 19:57:26 ice-arch systemd[1073]: Failed to start GNOME Shell on Wayland.

and I suspect the highlighted line about the experimental feature is kinda the killer?

iceeburr · 2023-07-29 21:33:23

Yeah that seems to fix it. Thank you for finding the correct solution. I will try to dig deeper into the logs next time I encounter an issue like this. I don't know how a simple restart can break it just like that over a night, but yeah, that was the whole issue. I would still consider switching to Xorg though. Now that fractional scaling is gone my eyes are just going to die faster. On Xorg I have no issues with scaling and HiDPI monitors. On Wayland I either had to use fractional scaling or find out how to scale each app individually, manually with some flag or through their native settings. I'll try out Xorg and see how it goes, if it's better then I'll stick to it. I don't think Wayland is ready yet, especially with the poor application support, maybe in a few years it will get better and I will switch back. The issue is solved.
Also yeah about the test user I haven't configured anything other than the password and I did expect it to break, next time I'll try to set the mandatory stuff for it to work so it's easier to find the root cause of the problem.

seth · 2023-07-29 21:38:34

Did you update gnome or clutter before the breaking reboot?

iceeburr · 2023-07-30 09:07:50

I don't remember, but probably not. I have installed packages during that time, but I haven't updated everything with sudo pacman -Syu. I ran it after I experienced the issue, and there was quite a lot to update, so I suppose I haven't updated for at least 2 days. Updating did not fix it, though, but disabling the experimental setting did!

Arch Linux

#1 2023-07-29 10:26:25

[SOLVED] Stuck on GNOME Login Screen

#2 2023-07-29 11:27:26

Re: [SOLVED] Stuck on GNOME Login Screen

#3 2023-07-29 12:48:31

Re: [SOLVED] Stuck on GNOME Login Screen

#4 2023-07-29 13:31:01

Re: [SOLVED] Stuck on GNOME Login Screen

#5 2023-07-29 13:53:34

Re: [SOLVED] Stuck on GNOME Login Screen

#6 2023-07-29 14:54:22

Re: [SOLVED] Stuck on GNOME Login Screen

#7 2023-07-29 15:23:13

Re: [SOLVED] Stuck on GNOME Login Screen

#8 2023-07-29 17:58:34

Re: [SOLVED] Stuck on GNOME Login Screen

#9 2023-07-29 20:25:36

Re: [SOLVED] Stuck on GNOME Login Screen

#10 2023-07-29 21:33:23

Re: [SOLVED] Stuck on GNOME Login Screen

#11 2023-07-29 21:38:34

Re: [SOLVED] Stuck on GNOME Login Screen

#12 2023-07-30 09:07:50

Re: [SOLVED] Stuck on GNOME Login Screen

Board footer