On yakkety, a unity crash and respawn kills all windows
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
unity (Ubuntu) |
Expired
|
Undecided
|
Unassigned |
Bug Description
So it used to be that when unity/compiz crash, which sadly happens to me about once a week, compiz would get respawned, causing maybe a few seconds of the session being frozen but then having everything back to normal.
This is unfortunately not the case with Yakkety. When the same issue happened to me again earlier, compiz did get respawned properly but I lost all my open windows.
I don't believe that this is the same issue as https:/
This may be related to the switch away from upstart user sessions over to systemd user sessions and the way systemd tracks and kills tasks.
I suspect this can be reproduced by killing (possibly with SIGSEG) unity-panel-service or even just compiz itself. Here it's usually unity-panel-service that's misbehaving, dies and takes compiz with it.
Changed in unity (Ubuntu): | |
assignee: | nobody → Martin Pitt (pitti) |
I cannot reproduce this. With "pkill -e -SEGV compiz" I get:
Okt 12 10:55:36 pid1 systemd[1001]: Starting Notification regarding a crash report...
Okt 12 10:55:36 pid1 systemd[1001]: Started Notification regarding a crash report.
Okt 12 10:55:44 pid1 systemd[1001]: unity7.service: Main process exited, code=dumped, status=11/SEGV
Okt 12 10:55:44 pid1 systemd[1001]: unity7.service: Unit entered failed state.
Okt 12 10:55:44 pid1 systemd[1001]: unity7.service: Failed with result 'core-dump'.
Okt 12 10:55:44 pid1 systemd[1001]: Starting Notification regarding a crash report...
Okt 12 10:55:44 pid1 systemd[1001]: unity7.service: Service hold-off time over, scheduling restart.
Okt 12 10:55:44 pid1 systemd[1001]: Stopped target User systemd services for the Ubuntu graphical session.
Okt 12 10:55:44 pid1 systemd[1001]: Stopping User systemd services for the Ubuntu graphical session.
Okt 12 10:55:44 pid1 systemd[1001]: Stopped Unity Shell v7.
Okt 12 10:55:44 pid1 systemd[1001]: Starting Unity Shell v7...
and then a lot of spew from compiz itself, but the session target or other units are unaffected. I also get all windows back (plus the apport crash notification). "pkill -ef -SEGV unity-panel- service" does not even produce any screen flicker, but it just restarts.
So maybe that is a duplicate of bug 1613297 after all?
Can you reproduce this somehow? If so, please run "journalctl -f" on the side and copy&paste the output. Thanks!