http://bugzilla.opensuse.org/show_bug.cgi?id=932787 http://bugzilla.opensuse.org/show_bug.cgi?id=932787#c6 Arun Persaud <arun@gmx.de> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |arun@gmx.de --- Comment #6 from Arun Persaud <arun@gmx.de> --- I'm experiencing something similar since recent updates (last few weeks) on Tumbleweed. When I try to log in, gdm returns to the login screen. When I boot the computer no wm works. I can then go to a terminal, stop gdm (systemctl stop gdm), then kill all jobs run by gdm, and then restart gdm. Once I have done these steps, I'm able to log in using the normal gnome session, i3 and "gnome on wayland" still don't work though. I'm running tumbleweed on two computers, and they behave slightly different. On the second computer I also need to kill all gdm jobs after a reboot, but after that I can log in using i3. However, if I do a "zypper up" I every now and then get logged out and gdm get's into an endless loop of trying to restart (which I can only stop by ssh'ing in and killing gdm). This doesn't seem to happen on the other computer I have. Seems to be a Wayland issue? However, if I set Wayland=false in /etc/gdm/custom.conf the above behavior doesn't change. Here are some error message from the log Mar 11 08:27:41 localhost systemd-logind[1634]: Failed to apply ACLs: Invalid argument (repeated many times) Mar 11 08:28:04 localhost gnome-session-binary[2336]: Unrecoverable failure in required component gnome-shell-wayland.des Mar 11 08:28:08 localhost systemd-coredump[2366]: Process 2344 (gnome-shell) of user 108 dumped core. (user 108 is gdm) Happy to upload some log files if needed. -- You are receiving this mail because: You are on the CC list for the bug.