[kde] [Bug 361471] GNOME services fail to clean-up after KDE "logout"

[James via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=361471

--- Comment #2 from James <james at nurealm.net> ---
Aha!  Apparently, KDE just needs to kill the still running dbus-daemon.

After startkde:
$ ps lU 1000
F   UID   PID  PPID PRI  NI    VSZ   RSS WCHAN  STAT TTY        TIME COMMAND
4  1000 30004     1  20   0  33960  4548 ep_pol Ss   ?          0:00
/usr/lib/systemd/systemd --user
5  1000 30005 30004  20   0 105628  1992 -      S    ?          0:00 (sd-pam)
4  1000 30014 29996  20   0  16696  4808 wait   Ss   tty1       0:00 -bash
0  1000 30152 30004  20   0  32844  3708 ep_pol Ss   ?          0:00
/usr/bin/dbus-daemon --session --address=systemd: --nofork --nopidfile
--systemd-activation
0  1000 30230 30004  20   0 478896 13588 poll_s Sl   ?          0:00
/usr/lib/telepathy/mission-control-5
0  1000 30239 30004  20   0 747796 32000 poll_s Sl   ?          0:00
/usr/lib/gnome-online-accounts/goa-daemon
0  1000 30247 30004  20   0 270808  6028 poll_s Ssl  ?          0:00
/usr/lib/gvfs/gvfsd
0  1000 30252 30004  20   0 338908  7572 futex_ Sl   ?          0:00
/usr/lib/gvfs/gvfsd-fuse /run/user/1000/gvfs -f -o big_writes
0  1000 30264 30004  20   0 280960  6276 poll_s Sl   ?          0:00
/usr/lib/gnome-online-accounts/goa-identity-service
0  1000 30298 30004  20   0 176600  4880 poll_s Sl   ?          0:00
/usr/lib/dconf/dconf-service
0  1000 30406 30014  20   0  34440  3136 -      R+   tty1       0:00 ps lUjames

Then:
$ kill 30152
$ ps lU 1000
F   UID   PID  PPID PRI  NI    VSZ   RSS WCHAN  STAT TTY        TIME COMMAND
4  1000 30004     1  20   0  34044  4564 ep_pol Ss   ?          0:00
/usr/lib/systemd/systemd --user
5  1000 30005 30004  20   0 105628  1992 -      S    ?          0:00 (sd-pam)
4  1000 30014 29996  20   0  16696  4808 wait   Ss   tty1       0:00 -bash
0  1000 30414 30014  20   0  34440  3092 -      R+   tty1       0:00 ps lUjames

And, that is back to the initial state.

The pivotal process is
/usr/bin/dbus-daemon --session --address=systemd: --nofork --nopidfile
--systemd-activation

and the parent process id for all of these "left-overs" here is 30004, the
original login "/usr/lib/systemd/systemd --user".  Hmm - so how could kde
deduce the pid of this "left-over" dbus-daemon process?  Then, "kill <pid>"
could just be added to the end of startkde.

And, is this a dbus or systemd bug, in some sense?  Since systemd starts these
processes with kde, but then just "leaves them around" after exit?  Or, did kde
"ask" for systemd to start these?

-- 
You are receiving this mail because:
You are the assignee for the bug.