https://bugs.kde.org/show_bug.cgi?id=359651
Bug ID: 359651
Summary: Dangling user processes after KDE session crash
Product: ksmserver
Version: 5.5.4
Platform: Fedora RPMs
OS: Linux
Status: UNCONFIRMED
Severity: crash
Priority: NOR
Component: general
Assignee: l.lu...@kde.org
Reporter: ber...@codewiz.org
After killing a KDE session, several processes remain dangling around:
bernie 877 0.0 0.0 45216 4816 ? Ss Feb20 0:00
/usr/lib/systemd/systemd --user
bernie 884 0.0 0.1 189548 13244 ? S Feb20 0:00
/usr/bin/kwalletd --pam-login 14 18 --nofork
bernie 21949 0.0 0.9 1660192 75676 ? Sl Feb20 0:25 kded5
[kdeinit5]
bernie 4295 0.0 0.0 0 0 ? Z 15:13 0:00 \_ [ibus]
<defunct>
bernie 22319 0.0 0.3 338740 26176 ? S Feb20 0:00
/usr/bin/kuiserver5
bernie 23897 0.0 0.0 170644 3028 ? Ss Feb20 0:02 gpg-agent
--homedir /home/bernie/.gnupg --use-standard-socket --daemon
bernie 4482 0.0 1.4 3168140 112336 ? Tl 15:16 0:05
/usr/bin/plasmashell -s --crashes 1
Reproducible: Always
Steps to Reproduce:
This scenario can easily be reproduced by killing the X server with
CTRL-ALT-BS.
Actual Results:
This leads to confusing / malfunctioning behavior in subsequent KDE sessions.
The only fix for non-technical users is rebooting the machine.
Expected Results:
The entire process tree under kdeinit / ksmserver should be killed.
--
You are receiving this mail because:
You are watching all bug changes.
