| 2014-09-19 13:12:41 |
Alexandros Frantzis |
bug |
|
|
added bug |
| 2014-09-19 13:20:11 |
Launchpad Janitor |
branch linked |
|
lp:~afrantzis/unity8/fix-1371597-remove-stale-trusted-socket |
|
| 2014-09-19 14:09:53 |
Alexandros Frantzis |
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. Normally Mir is able to clean up the sockets even when the server crashes. We need to investigate why this isn't happening in this case. |
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. |
|
| 2014-09-19 14:24:21 |
Alexandros Frantzis |
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. |
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). |
|
| 2014-10-01 09:58:24 |
Launchpad Janitor |
branch linked |
|
lp:ubuntu/utopic-proposed/unity8 |
|
| 2014-10-01 10:43:57 |
Launchpad Janitor |
unity8 (Ubuntu): status |
New |
Fix Released |
|
