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 Desktop
Packages, 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"]
Status in gnome-shell package in Ubuntu:
Confirmed
Status in mutter package in Ubuntu:
Confirmed
Bug description:
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/gnome-shell/+bug/2069564/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
