Comment 1 for bug 1632386

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!