unity8 does not always clear up the mir socket file
Bug #1236106 reported by
Thomi Richards
This bug report is a duplicate of:
Bug #1235159: Mir fails to start if there's a stale socket.
Edit
Remove
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Unity 8 |
New
|
High
|
Unassigned | ||
Bug Description
When bug lp:1236104 occurs, the unity8 process does not delete the /tmp/mir_socket file, which means that subsequent launches of unity8 will fail with the "address already in use" error message.
It would be nice if we could make sure that we clean up that file in our error handling code.
Revision history for this message
| Alan Griffiths (alan-griffiths) wrote | #1 |
To post a comment you must log in.
It is probably not feasible to remove the endpoint in all failure scenarios (although I'm trying to improve the Mir behaviour).
The most complete solution is probably for the unity8 upstart script to delete the file in pre-start and post-stop.