![](https://seccdn.libravatar.org/avatar/3035b38ff33cf86f480bb169b8500b80.jpg?s=120&d=mm&r=g)
http://bugzilla.suse.com/show_bug.cgi?id=1062068
http://bugzilla.suse.com/show_bug.cgi?id=1062068#c6
--- Comment #6 from Franck Bui
I guess it could be. If systemd-logind would send some signal saying "Hey I am going away and not coming back any time soon.", we could listen for that.
It does not solve the case when systemd-logind crashes, but in my opinion we shouldn't try too hard in that case. If such important component crashes, I would expect anything can happen, so why should X server have some special safety against it.
Might be worth to ask if upstream would accept to implement such signal.
With BindsTo I am observing this: * If B is stopped, then A is stopped. Good, we want that. * If B is restarted, then A is restarted. Bad, we don't want that.
Hmm... I'm not sure what the right behavior should be: currently I dont see the point to restart A if B is restarted. A should be stopped in case the restart of B fails though. -- You are receiving this mail because: You are on the CC list for the bug.