…cue lots of discussion…
Unless we change the way we start Unity8 (which I've yet to convince
people we should), we - tragically - can't pass an fd to unity on
startup.
What we *can* do is hand off an FD to logind, and have unity8 pull it
from there. Keeping that fd away from non-Unity processes is then left
as an exercise for AppArmour confinement profiles written by the
security team.
Adding appropriate tasks.
** Also affects: systemd (Ubuntu)
Importance: Undecided
Status: New
** Also affects: unity8 (Ubuntu)
Importance: Undecided
Status: New
** Also affects: lightdm (Ubuntu)
Importance: Undecided
Status: New
** No longer affects: systemd (Ubuntu)
** No longer affects: unity8 (Ubuntu)
** No longer affects: unity-system-compositor (Ubuntu)
** Changed in: lightdm (Ubuntu)
Status: New => Triaged
** Changed in: lightdm (Ubuntu)
Assignee: (unassigned) => Chris Halse Rogers (raof)
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to lightdm in Ubuntu.
https://bugs.launchpad.net/bugs/1322300
Title:
[enhancement] Please move /tmp/mir_socket to /run/mir_socket (or
similar)
Status in Mir:
Opinion
Status in “lightdm” package in Ubuntu:
Triaged
Bug description:
/tmp/mir_socket is created by unity-system-compositor. It is easy to
prevent mir from starting by creating this file before hand. Eg:
# stop lightdm ; touch /tmp/mir_socket ; start lightdm
lightdm fails to start. It would be better if /run/mir_socket (or some
other root-owned directory) were used.
To manage notifications about this bug go to:
https://bugs.launchpad.net/mir/+bug/1322300/+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
