Mir cannot restart after a crash because /tmp/mir_socket is not deleted
Bug #1236379 reported by
Eleni Maria Stea
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 | |
---|---|---|---|---|---|
Mir |
New
|
Undecided
|
Unassigned |
Bug Description
When mir crashes or exits abnormally /tmp/mir_socket is not deleted. Next time I try to start mir (I tried using "start lightdm") I get the following error in /var/log/
Dynamic exception type: boost::
std::exception:
$ ps aux | grep mir
eleni 12421 0.0 0.0 13644 964 pts/9 S+ 16:58 0:00 grep --color=auto mir
shows that xmir is not running.
If I manually delete /tmp/mir_socket, the problem is fixed and in next lightdm start or restart mir is up again.
To post a comment you must log in.