| Summary: | Dangling user processes after KDE session crash | ||
|---|---|---|---|
| Product: | [Unmaintained] ksmserver | Reporter: | Bernie Innocenti <bernie> |
| Component: | general | Assignee: | Lubos Lunak <l.lunak> |
| Status: | RESOLVED FIXED | ||
| Severity: | crash | CC: | bugseforuns, colaboracs, dario, eric.donkersloot, kde, kde, mario+bugs.kde.org, nate, niels_ole, rdieter, steve |
| Priority: | NOR | ||
| Version: | 5.19.2 | ||
| Target Milestone: | --- | ||
| Platform: | Arch Linux | ||
| OS: | Linux | ||
| See Also: | https://bugs.kde.org/show_bug.cgi?id=244250 | ||
| Latest Commit: | https://invent.kde.org/plasma/plasma-workspace/commit/f377696bff39e35ae0f7ae6104d8732b3856744e | Version Fixed In: | 5.24 |
| Sentry Crash Report: | |||
|
Description
Bernie Innocenti
2016-02-21 22:21:00 UTC
This bug could be refiled under the kdeframeworks-kinit component. Not sure which one is responsible for session cleanup. Still present in Plasma 5.10.1. Also present in Archlinux. Even though the session is now managed by systemd, I still see an entire dangling session when logging out from a Plasma session: bernie 889 Ss /usr/lib/systemd/systemd --user bernie 890 S \_ (sd-pam) bernie 901 Ss \_ /usr/bin/ssh-agent -a /run/user/1000/ssh-agent.socket bernie 911 Ss \_ /usr/bin/dbus-daemon --session --address=systemd: --nofork --nopidfile --systemd-activation --syslog-only bernie 965 Sl \_ /usr/lib/dconf-service bernie 1048 Ssl \_ /usr/lib/gvfsd bernie 1058 Sl \_ /usr/lib/gvfsd-fuse /run/user/1000/gvfs -f bernie 1118 Ssl \_ /usr/lib/at-spi-bus-launcher bernie 1125 S | \_ /usr/bin/dbus-daemon --config-file=/usr/share/defaults/at-spi2/accessibility.conf --nofork --print-address bernie 1126 Ssl \_ /usr/lib/xdg-desktop-portal bernie 1131 Ssl \_ /usr/lib/xdg-document-portal bernie 1134 Ssl \_ /usr/lib/xdg-permission-store bernie 1203 Ssl \_ /usr/bin/pipewire bernie 1240 Ss \_ /usr/lib/bluetooth/obexd bernie 1039 Sl /usr/lib/geoclue-2.0/demos/agent Perhaps this bug will be fixed by this commit? https://github.com/sddm/sddm/commit/9ce5bd6e62b2fd1f96421b9797e64181883d15c3 David, do you reckon your recent commit to SDDM will fix this bug? Yeah but I might end up reverting it. Have you tried logind's KillUserProcesses option? This is still happening with latest sddm and plasma-workspace bernie2 11301 0.0 0.0 19552 10620 ? Ss 22:28 0:00 /usr/lib/systemd/systemd --user bernie2 11302 0.0 0.0 194380 3596 ? S 22:28 0:00 \_ (sd-pam) bernie2 11322 0.0 0.0 267340 3268 ? Ss 22:28 0:00 \_ /usr/bin/dbus-broker-launch --scope user bernie2 11323 0.0 0.0 5048 3200 ? S 22:28 0:00 | \_ dbus-broker --log 4 --controller 10 --machine-id 6ed6dbe65a274a909e5e7af2f4570b62 --max-bytes 100000000000000 --max-fds 25000000000000 --max-matches 5000000000 bernie2 11325 0.0 0.0 236908 7364 ? Ssl 22:28 0:00 \_ /usr/lib/gvfsd bernie2 11330 0.0 0.0 382412 7816 ? Sl 22:28 0:00 \_ /usr/lib/gvfsd-fuse /run/user/1001/gvfs -f bernie2 11423 0.0 0.0 154920 3624 ? Ssl 22:28 0:00 \_ /usr/lib/dconf-service bernie2 11554 0.0 0.0 44176 6820 ? Ss 22:28 0:00 \_ /usr/lib/bluetooth/obexd bernie2 11924 0.6 0.0 158500 9244 ? S<sl 22:29 0:00 \_ /usr/bin/pulseaudio --daemonize=no bernie2 11940 0.0 0.0 238104 9600 ? Sl 22:30 0:00 \_ /usr/lib/pulse/gsettings-helper bernie2 11451 0.0 0.1 268668100 26068 ? SNl 22:28 0:00 /home/bernie/kde/usr/bin/baloo_file bernie2 11501 0.0 0.0 234140 5036 ? Sl 22:28 0:00 /usr/lib/geoclue-2.0/demos/agent *** Bug 422322 has been marked as a duplicate of this bug. *** *** Bug 417889 has been marked as a duplicate of this bug. *** This is being worked in in a generic way via the systemd slices and cgroup work. *** Bug 427111 has been marked as a duplicate of this bug. *** This is reproducible under openSUSE Leap 15.2 with Plasma 5.19.90 (prebuilt RPMs). I have two systems here. The list of dangling processes on each is not identical to each other. I tested a little: on one machine, killing only kio_http_cache_cleaner resulted in the other dangling processes exiting without needing to be killed. This is reproducible on that machine. On the other machine, some processes still remained after killing kio_http_cache_cleaner. I was able to trigger them exiting by killing kwin_x11 I think (didn't make a note). Perhaps they don't exit because they're still waiting for the bus. *** Bug 362142 has been marked as a duplicate of this bug. *** *** Bug 244250 has been marked as a duplicate of this bug. *** Git commit f377696bff39e35ae0f7ae6104d8732b3856744e by Aleix Pol Gonzalez, on behalf of Aleix Pol. Committed on 09/11/2021 at 12:17. Pushed by apol into branch 'master'. startplasma: Make sure we terminate the processes we start Changes how plasma_session works. Instead of just starting the processes, plays the startup sound and stays around. This process then gets to be terminated as the session ends. Related: bug 433293 M +14 -23 startkde/CMakeLists.txt M +4 -6 startkde/plasma-session/CMakeLists.txt A +47 -0 startkde/plasma-session/sessiontrack.cpp [License: LGPL(v2.0)] A +22 -0 startkde/plasma-session/sessiontrack.h [License: LGPL(v2.0)] A +60 -0 startkde/plasma-session/signalhandler.cpp [License: LGPL(v2.0)] A +38 -0 startkde/plasma-session/signalhandler.h [License: LGPL(v2.0)] M +35 -3 startkde/plasma-session/startup.cpp M +15 -0 startkde/plasma-session/startup.h M +1 -1 startkde/startplasma-waylandsession.cpp M +18 -16 startkde/startplasma.cpp M +1 -1 startkde/startplasma.h M +9 -0 startkde/waitforname/main.cpp https://invent.kde.org/plasma/plasma-workspace/commit/f377696bff39e35ae0f7ae6104d8732b3856744e |