@nteodosio: who owns /tmp/.X11-unix after you login? in the case I can reproduce it is owned by gdm, and I can confirm it is a regression compared to *u4.1 as it does not happen if /tmp/.X11-unix is owned by gdm, and if it is not owned by gdm nor root nor user, I am able to login into the desktop but only in X11 (no cogwheel present).
nvidia-driver-560 is used, just in case if it is relevant. I did a test on a (seemingly) Wayland session, I can see a cogwheel, but I cannot login in neither Wayland nor X11 session. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/2069564 Title: [SRU] gnome-shell crashed with SIGTRAP in meta_wayland_compositor_new() from meta_context_start() from main() ["Failed to start X Wayland: Directory \"/tmp/.X11-unix\" is not writable"] Status in mutter package in Ubuntu: Fix Released Status in mutter source package in Oracular: Fix Committed Status in mutter source package in Plucky: Fix Released Bug description: If you are hitting this bug, please write your case in https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/3984. [Impact] This causes one of the top Gnome-Shell crashes as caught by Ubuntu error tracker. It happens when /tmp/.X11-unix is accessible by the user but does not pass a stricter permission check Mutter makes. In the typical Ubuntu setup, both /tmp and /tmp/.X11-unix are root:root rwxrwxrwt, so it passes that stricter permission check. [Test case] 1. Stop GDM: systemctl stop gdm This will bring you to the virtual console (i.e. without a graphical environment, only command-line). 2. Install mutter, gir1.2-mutter-15, libmutter-15-0, mutter-common, mutter-common-bin from proposed (the exact steps to enable proposed are laid down by the SRU bot comment to this bug). 3. Execute: chmod 1007 /tmp/.X11-unix 4. Execute: MUTTER_DEBUG=all G_DEBUG=1 dbus-run-session -- gnome-shell --display-server --wayland &>log Gnome-Shell must start and Mutter (you can look for them in 'ps aux' output if you are not acquainted with the looks of those pieces of software). 5. Now open xterm and kill the graphical environment by executing: pkill wayland Verify that there are no mentions of the issue directory in the log, i.e. 'grep X11-unix log' returns nothing. [Where problems could occur] In Mutter or Gnome-Shell, particularly at launch phase. Also make sure Xorg applications behave normally (that's why xterm is included in test case), without failing to open or delays. --------------- The Ubuntu Error Tracker has been receiving reports about a problem regarding gnome-shell. This problem was most recently seen with package version 46.0-0ubuntu5.1, the problem page at https://errors.ubuntu.com/problem/a7dbd55723a8ea326d1ccf32e31fe307151786c2 contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker and are a software developer, you can request it at http://forms.canonical.com/reports/. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/2069564/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : [email protected] Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
