In the case that /tmp is owned by ourselves and it matches 0200 but not
0022, it is still writable but it would fail with the present error.
I do not know if this is actually an intended blockage and thus the
description is just not clear enough or if this is an edge case to
consider.
Nor do we know whether all the reports here would be solved by allowing
this scenario, namely {we are not root, /tmp is ours, /tmp/.X11-unix is
at least 0200}.
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-shell in Ubuntu.
https://bugs.launchpad.net/bugs/2069564
Title:
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/gnome-shell/+bug/2069564/+subscriptions
--
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
