> 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 in *u4.1 it does not happen if /tmp/.X11-unix is owned by gdm.
We're missing something different in our set ups then because exact same procedure gives different results... I'm testing in a virtual machine. After 'systemctl stop gdm; rm -r /tmp/.X11-unix; systemctl start gdm': File: /tmp/.X11-unix/ Size: 80 Blocks: 0 IO Block: 4096 directory Device: 0,32 Inode: 276 Links: 2 Access: (1777/drwxrwxrwt) Uid: ( 120/ gdm) Gid: ( 122/ gdm) Access: 2025-02-27 08:35:02.481540724 +0100 Modify: 2025-02-27 08:35:02.861535505 +0100 Change: 2025-02-27 08:35:02.861535505 +0100 Birth: 2025-02-27 08:35:02.481540724 +0100 After logging in, same thing. By the way, I don't see > "Failed to start X Wayland: Wrong ownership for directory "/tmp/.X11-unix": 120.#012Ownership of "/tmp": 0.#012Current user: 1000." in your 4.2 log, but I see > (gnome-shell:9421): libmutter-ERROR **: 14:57:37.313: Failed to start X Wayland: Directory "/tmp/.X11-unix" is not writable in your 4.1 log, so looks like it's not the same failure Gre0 saw. > Should we move this to verification-failed? I think it is the safest to do. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, 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"] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/2069564/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
