Hi Thomas,
Thomas Liske wrote:
> restarting dbus kills any graphical user session.
I wouldn't say that. But it's probably true for most modern desktop
environments and systemd -- unfortunately.
> >in the (used) default config, systemd restarted dbus:
>
> Are you able to kill your X session by calling `systemctl
> daemon-reexec` manually?
Nope, can still work in that session. :-)
> >Nov 25 11:18:57 c-cactus systemd[1]: Activated swap /dev/…/swap.
>
> At this point `systemctl reexec` should have been finished.
That's also where the log ended after the manual "systemctl
daemon-reexec".
> >Nov 25 11:18:57 c-cactus systemd[1]: Stopping Accounts Service...
> >Nov 25 11:18:57 c-cactus systemd[1]: Stopping Avahi mDNS/DNS-SD Stack...
> >Nov 25 11:18:57 c-cactus systemd[1]: Stopping Bluetooth service...
> >Nov 25 11:18:57 c-cactus systemd[1]: Stopping Regular background program
> >processing daemon...
> >Nov 25 11:18:57 c-cactus systemd[1]: Starting Regular background program
> >processing daemon...
> >Nov 25 11:18:57 c-cactus systemd[1]: Started Regular background program
> >processing daemon.
> >Nov 25 11:18:57 c-cactus systemd[1]: Stopping D-Bus System Message Bus...
> >Nov 25 11:18:57 c-cactus systemd[1]: Starting Accounts Service...
> >Nov 25 11:18:57 c-cactus systemd[1]: Starting Bluetooth service...
> >Nov 25 11:18:57 c-cactus systemd[1]: Stopping OpenBSD Secure Shell server...
> >Nov 25 11:18:57 c-cactus systemd[1]: Stopping Journal Service...
> >Nov 25 11:18:57 c-cactus systemd[1641]: Stopping Default.
> >Nov 25 11:18:57 c-cactus systemd[1641]: Stopped target Default.
> >Nov 25 11:18:57 c-cactus systemd[1641]: Stopping Basic System.
> >Nov 25 11:18:57 c-cactus systemd[1641]: Stopped target Basic System.
> >Nov 25 11:18:57 c-cactus systemd[1641]: Stopping Paths.
> >Nov 25 11:18:57 c-cactus systemd[1641]: Stopped target Paths.
> >Nov 25 11:18:57 c-cactus systemd[1641]: Stopping Timers.
> >Nov 25 11:18:57 c-cactus systemd[1641]: Stopped target Timers.
> >Nov 25 11:18:57 c-cactus systemd[1641]: Stopping Sockets.
> >Nov 25 11:18:57 c-cactus systemd[1641]: Stopped target Sockets.
> >Nov 25 11:18:57 c-cactus systemd[1641]: Starting Shutdown.
> >Nov 25 11:18:57 c-cactus systemd[1641]: Reached target Shutdown.
> >Nov 25 11:18:57 c-cactus systemd[1641]: Starting Exit the Session...
> >Nov 25 11:18:57 c-cactus systemd[1]: Starting OpenBSD Secure Shell server...
> >Nov 25 11:18:57 c-cactus systemd[1]: Started OpenBSD Secure Shell server.
> >Nov 25 11:18:57 c-cactus systemd[1641]: Received SIGRTMIN+24 from PID 12082
> >(kill).
> >Nov 25 11:18:57 c-cactus systemd[1]: Started Trigger Flushing of Journal to
> >Persistent Storage.
> >Nov 25 11:18:57 c-cactus systemd[1]: Starting Daemon for power management...
> >Nov 25 11:18:57 c-cactus systemd[1]: Starting LSB: Starts and stops Wicd...
> >Nov 25 11:18:57 c-cactus systemd[1]: Starting D-Bus System Message Bus...
> >Nov 25 11:18:57 c-cactus systemd[1]: Started D-Bus System Message Bus.
> >Nov 25 11:18:57 c-cactus systemd[1]: Started Bluetooth service.
> >Nov 25 11:18:57 c-cactus systemd[1]: Starting Hostname Service...
> >Nov 25 11:18:57 c-cactus systemd[1]: Started Accounts Service.
> >Nov 25 11:18:57 c-cactus systemd[1]: Started Daemon for power management.
> >Nov 25 11:18:57 c-cactus systemd[1]: Starting User Manager for UID 1000...
> >Nov 25 11:18:57 c-cactus systemd[1]: Starting Login Service...
> >Nov 25 11:18:57 c-cactus systemd[1]: Started Hostname Service.
> >Nov 25 11:18:57 c-cactus systemd[1]: Started Login Service.
> >Nov 25 11:18:57 c-cactus systemd[1]: Started User Manager for UID 1000.
> >Nov 25 11:18:58 c-cactus systemd[1]: Starting Session c1 of user abe.
> >Nov 25 11:18:58 c-cactus systemd[1]: Started Session c1 of user abe.
> >Nov 25 11:18:59 c-cactus systemd[1]: Starting LSB: start or stop the WINGs
> >display manager...
> >Nov 25 11:18:59 c-cactus systemd[1]: Started LSB: start or stop the WINGs
> >display manager.
> >Nov 25 11:18:59 c-cactus systemd[1]: Starting X11 Display Manager.
> >Nov 25 11:18:59 c-cactus systemd[1]: Reached target X11 Display Manager.
>
> It might be an dependency issue... "X11 Display Manager" depends on
> something that needrestart did suggest to restart.
Compared to "modern" login managers, wdm's dependencies are rather lightweight:
Depends: libc6 (>= 2.11), libpam0g (>= 0.99.7.1), libselinux1 (>=
1.32), libwings2 (>= 0.95.0), libwraster3 (>= 0.95.0), libwutil2 (>=
0.95.0), libx11-6, libxau6, libxdmcp6, libxinerama1, libxmu6, debconf
(>= 1.5.20) | debconf-2.0, libpam-runtime (>= 0.76-13.1),
libpam-modules, psmisc, x11-apps, x11-common, x11-xserver-utils,
x11-utils
> Are you able to remember which service were selected?
Not at all, because I had set "$nrconf{restart} = 'a'" and systemd
doesn't care to tell me what it does -- compared to needrestart on a
system with good old sysvinit. Meh.
> If you did not run needrestart in the meanwhile you might find your
> selection still in debconf:
>
> $ grep -A 8 'needrestart/ui-query_pkgs$' /var/cache/debconf/config.dat
This looks very suspicious:
→ grep -A 8 'needrestart/ui-query_pkgs$' /var/cache/debconf/config.dat
Name: needrestart/ui-query_pkgs
Template: needrestart/ui-query_pkgs
Value: dbus.service, lxc
Owners: unknown
Flags: seen
Variables:
OUT = Services to be restarted:
PKGS = dbus.service, lxc, wdm.service
Name: needrestart/ui-query_pkgs_title
> $ grep -A 8 'needrestart/ui-query_pkgs$' /var/cache/debconf/config.dat-old
→ grep -A 8 'needrestart/ui-query_pkgs$'
/var/cache/debconf/config.dat-old
Name: needrestart/ui-query_pkgs
Template: needrestart/ui-query_pkgs
Value: dbus.service, lxc
Owners: unknown
Flags: seen
Variables:
OUT = Services to be restarted:
PKGS = dbus.service, lxc, wdm.service
Name: needrestart/ui-query_pkgs_title
So why the heck are there wdm and dbus listed?
JFTR: I'm using needrestart's default config:
→ debsums -e needrestart
/etc/needrestart/hook.d/90-none OK
/etc/needrestart/hook.d/10-dpkg OK
/etc/needrestart/notify.d/README.needrestart OK
/etc/needrestart/notify.d/100-write OK
/etc/needrestart/needrestart.conf OK
/etc/needrestart/hook.d/20-rpm OK
/etc/dpkg/dpkg.cfg.d/needrestart OK
/etc/apt/apt.conf.d/99needrestart OK
/etc/needrestart/conf.d/README.needrestart OK
/etc/needrestart/notify.d/110-notify-send OK
with only one exception:
→ cat /etc/needrestart/conf.d/abe.conf
#$nrconf{restart} = 'a';
$nrconf{ui} = 'NeedRestart::UI::stdio';
(The $nrconf{restart} has been commented out after the last incident.)
HTH.
Regards, Axel
--
,''`. | Axel Beckert <[email protected]>, http://people.debian.org/~abe/
: :' : | Debian Developer, ftp.ch.debian.org Admin
`. `' | 1024D: F067 EA27 26B9 C3FC 1486 202E C09E 1D89 9593 0EDE
`- | 4096R: 2517 B724 C5F6 CA99 5329 6E61 2FF9 CD59 6126 16B5
--
To UNSUBSCRIBE, email to [email protected]
with a subject of "unsubscribe". Trouble? Contact [email protected]
