Bugzilla – Bug 1216003
Apps opening as X11
Last modified: 2023-10-18 14:27:56 UTC
After entering my login information into GDM, the screen goes blank and then falls back to the login screen again. I discovered this was due to my .xinitrc file which had an xrandr command. After deleting the file, I can login but all my apps seem to be running as X11 apps instead of wayland. I confirmed this using xlsclients installed in a distrobox. I also started seeing a bunch of other issues. Very slow logout with a different logout screen. I also could not log in from a different virtual terminal. Doing a transactional-update rollback resolved the issue (apps now wayland again) but now I cannot update without seeing the issue repeated.
Okay...that doesn't happen here..do you have any debug information, logs, or other information that can possibly help identify why this is happening for you?
Created attachment 869958 [details] sudo journactl from this morning This log output is from when I woke my laptop this morning and covers the period I had issues and then the rollback.
(In reply to Richard Brown from comment #1) > Okay...that doesn't happen here..do you have any debug information, logs, or > other information that can possibly help identify why this is happening for > you? I added a log. I do not have any debug information. My computer is a Dell XPS 9300 with 1TB nvme and 16GB ram. I clean installed Aeon about a week and a half ago. I have not installed anything using transactional-update. Mainly use flatpaks and distrobox for the rest (non-root).
Created attachment 869984 [details] dmesg output
I am having possibly a related issue. Using the same mode laptop and after latest update to Tumbleweed, system logged into X11 rather than wayland. When checking GDM, wayland session was not available. I've attached dmesg output.
(In reply to Richard Wallwork from comment #5) > I am having possibly a related issue. Using the same mode laptop and after > latest update to Tumbleweed, system logged into X11 rather than wayland. > When checking GDM, wayland session was not available. I've attached dmesg > output. Hi Richard Can you look in your log (sudo journalctl). I have the following lines which seem to be where the issue is recorded? Oct 06 06:56:13 pluto systemd[3754]: GNOME Shell on Wayland was skipped because of an unmet condition check (ConditionEnvironment=XDG_SESSION_TYPE=wayland). Oct 06 06:56:13 pluto gnome-session[3927]: gnome-session-binary[3927]: GnomeDesktop-WARNING: Could not create transient scope for PID 3951: GDBus.Error:org.freedesktop.DBus.Error.UnixProcessIdUnknown: Process with ID 3951 does not exist. Oct 06 06:56:13 pluto gnome-session-binary[3927]: GnomeDesktop-WARNING: Could not create transient scope for PID 3951: GDBus.Error:org.freedesktop.DBus.Error.UnixProcessIdUnknown: Process with ID 3951 does not exist. Oct 06 06:56:13 pluto systemd[3754]: Starting GNOME Shell on X11...
The issue may be due to a bad Mesa update from 1:23.1.8-1 -> 1:23.2.1-1 (https://bbs.archlinux.org/viewtopic.php?id=289333). Seems to affect Ice Lake which would explain the issue being on XPS 9300. I am not a developer. Do I wait for an upstream fix? I tried putting a lock on Mesa but just got a black screen when I updated to the latest snapshot.
Hi Yes I think it is Mesa. I am on a freshly installed system, so downgraded (probably unwisely but hey ho) using http://download.opensuse.org/history/20231001/tumbleweed/repo/oss/ and Wayland works fine now.
From what I've read here https://gitlab.freedesktop.org/mesa/mesa/-/issues/9889 this has been resolved on other distros with an update to Mesa, but the latest snapshot of Tumbleweed, the problem is still present.
Fixed in latest snapshot