Hi.

When gdm3 is restarted/stopped via it's init-script or systemd unit file,
perhaps after an upgrade when e.g. needrestart defaults to restarting it,
it doesn't handle this very gracefully, but rather kills any existing
sessions including all programs of the user running in them (without
any further question).

Of course restart/stop should actually do a restart/stop, but that should
be done more gracefully, especially.

Perhaps giving a desktop notification, that asks the user to relogin ASAP.


OTOH, a sysadmin should have a clean way to stop gdm and X via systemctl...
so putting control in the user's hand isn't the best thing either.


Any ideas how this could be handled properly?


Cheers,
Chris.