touch-packages team mailing list archive
-
touch-packages team
-
Mailing list archive
-
Message #22528
[Bug 1371597] Re: Stale trusted socket may stop Unity8 from restarting after an abnormal exit
** Branch linked: lp:ubuntu/utopic-proposed/unity8
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to unity8 in Ubuntu.
https://bugs.launchpad.net/bugs/1371597
Title:
Stale trusted socket may stop Unity8 from restarting after an abnormal
exit
Status in “unity8” package in Ubuntu:
New
Bug description:
In some cases (like bug #1371593) unity8 crashes leaving the
mir_socket and mir_socket_trusted sockets in the filesystem. When
unity8 tries to restart it fails with "bind: address already in use"
because of the left over mir_socket_trusted.
There are two aspects to this bug:
1. The unity8 upstart script should clean up the trusted socket before starting, like it does for the normal socket
2. If Mir is instantiated using the mir::run_mir() helper function, it is able to clean up the sockets even when the server crashes. However unity8 doesn't currently use the helper (also see bug #1371621).
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/unity8/+bug/1371597/+subscriptions
References