Loïc Grenié composed on 2022-11-29 23:35 (UTC+0100):
> when I apt upgrade my system, I often (one every three, more
> or less) find myself brutally logged out of the window system,
> with systemd services painfully restarting (or failing to restart).
> The only way I can recover is usually to reboot. I've tried to
> manually stop, kill the leftover processes and restart the services,
> one after the other, but it's very long and does not always work.
> I have observed this situation for a few years (maybe two or three,
> maybe more, I'm slow to bore).
> Am I the only one? Is there a way to upgrade the system without
> rebooting as it used to be a few years ago? I remember updating
> libc.so without rebooting -- only the kernel needed reboot, and
> the window system, if specific files changed.
I learned many many moons ago to not trust any update/upgrade process to not
interfere with a running X session. I usually close apps I don't want data lost
from before beginning an upgrade process. That usually means I log all the way
out
of X entirely, then start the upgrade from a vtty.
What I have noticed in Debian that I do not at all like, is when I boot to
multi-user.target for the specific purpose of apt or apt-get upgrading, even
when
systemctl get-default returns multi-user.target, that if the DM is upgraded, X
gets started shortly following. :(
--
Evolution as taught in public schools is, like religion,
based on faith, not based on science.
Team OS/2 ** Reg. Linux User #211409 ** a11y rocks!
Felix Miata
