Bug 360171 - orphaned and hanging kf5/plasma-processes after session end
Summary: orphaned and hanging kf5/plasma-processes after session end
Status: RESOLVED WORKSFORME
Alias: None
Product: frameworks-kded
Classification: Frameworks and Libraries
Component: general (show other bugs)
Version: unspecified
Platform: Other Other
: NOR normal
Target Milestone: ---
Assignee: David Faure
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2016-03-06 20:20 UTC by Johannes Hirte
Modified: 2022-11-25 05:22 UTC (History)
2 users (show)

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Johannes Hirte 2016-03-06 20:20:58 UTC
After loging out of a plasma session, there are still processes left over. The list usually contains:

kded5
kactivitymanage
kglobalaccel5
dconf-service
kuiserver5
kio_http_cache_
kwalletd5

The first three can only be quit with SIGKILL. On system shutdown/reboot, systemd is stopped by this.  Killing them by hand before make the system shutdown/reboot as expected.

Reproducible: Always
Comment 1 Matthias Dahl 2016-03-29 07:44:53 UTC
I am seeing the same thing here -- the list of dangling processes varies but kded5 usually stays around and needs to be killed with SIGKILL. And also, yes, systemd hangs for the specified timeout value during shutdown/reboot until it successfully kills those processes which is very unfortunate. :-(

Those dangling processes are an old issue (see bug 359651 for example) which I have noticed ever since I switched to KDE 5 (which was quite some time ago). But that some of them can only be killed and thus delay the shutdown, that is definitely new.

This is seen with Qt 5.6 (w/ the qtdbus fix for the spy stuff), KDE Frameworks 5.20.0 and Plasma 5.6 on an uptodate Gentoo ~amd64 system.

If there is anything more I can do to help diagnose this further, please let me know.
Comment 2 Justin Zobel 2022-10-26 03:07:22 UTC
Thank you for reporting this bug in KDE software. As it has been a while since this issue was reported, can we please ask you to see if you can reproduce the issue with a recent software version?

If you can reproduce the issue, please change the status to "REPORTED" when replying. Thank you!
Comment 3 Bug Janitor Service 2022-11-10 05:11:59 UTC
Dear Bug Submitter,

This bug has been in NEEDSINFO status with no change for at least
15 days. Please provide the requested information as soon as
possible and set the bug status as REPORTED. Due to regular bug
tracker maintenance, if the bug is still in NEEDSINFO status with
no change in 30 days the bug will be closed as RESOLVED > WORKSFORME
due to lack of needed information.

For more information about our bug triaging procedures please read the
wiki located here:
https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

If you have already provided the requested information, please
mark the bug as REPORTED so that the KDE team knows that the bug is
ready to be confirmed.

Thank you for helping us make KDE software even better for everyone!
Comment 4 Bug Janitor Service 2022-11-25 05:22:16 UTC
This bug has been in NEEDSINFO status with no change for at least
30 days. The bug is now closed as RESOLVED > WORKSFORME
due to lack of needed information.

For more information about our bug triaging procedures please read the
wiki located here:
https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

Thank you for helping us make KDE software even better for everyone!