https://bugs.kde.org/show_bug.cgi?id=422322
S. Bryant <st...@bawue.de> changed:
What |Removed |Added
----------------------------------------------------------------------------
Resolution|NOT A BUG |---
Status|RESOLVED |REOPENED
Ever confirmed|0 |1
--- Comment #9 from S. Bryant <st...@bawue.de> ---
> This report has become a mix of too many conflicting things.
I must disagree. Given that a number of programs that used to terminate no
longer do so, it seems reasonable to assume there is a common problem. That
problem may be outside of ksmserver, however. It would be nice to narrow
things down. Can you (David) confirm that no processes linger on your system?
Here's a list of lingering programs after logout on this system (now with
Plasma 5.19.2):
/usr/lib/systemd/systemd --user
(sd-pam)
/usr/bin/dbus-daemon --session --address=systemd: --nofork --nopidfile
--systemd-activation --syslog-only
/usr/lib/gvfs/gvfsd
/usr/lib/gvfs/gvfsd-fuse /run/user/1026/gvfs -f -o big_writes
/usr/lib/at-spi2/at-spi-bus-launcher
/usr/bin/dbus-daemon
--config-file=/usr/share/defaults/at-spi2/accessibility.conf --nofork
--print-address 3
/usr/bin/kwin_x11
/usr/lib/dconf-service
/usr/bin/baloo_file
/usr/lib/bluetooth/obexd
/usr/bin/ksystemstats
/usr/bin/ksysguardd
/usr/lib/GConf/2/gconfd-2
/usr/lib64/libexec/kf5/kio_http_cache_cleaner
> If gvfs lingers, that lies with gvfs.
Is that true for the others too?
> If logout scripts are broken make a new report.
Fair enough, let's ignore those in this bug report.
Given that it's not possible to log in after logging out (unless the processes
are manually killed), the "not a bug" status is incorrect.
BTW: the original report mentioned shutdown waits for 2 minutes. This is after
the display manager has exited - it's one of the system scripts waiting for
user processes to terminate so partitions can be unmounted. It's not Plasma
waiting for 2 minutes.
--
You are receiving this mail because:
You are watching all bug changes.
