Bug 359655

Summary:	kwalletd5 and kwalletd hanging around after session exited
Product:	[Frameworks and Libraries] kwallet-pam	Reporter:	Bernie Innocenti <bernie>
Component:	general	Assignee:	Plasma Bugs List <plasma-bugs-null>
Status:	RESOLVED WORKSFORME
Severity:	normal	CC:	derwesermann
Priority:	NOR
Version First Reported In:	5.5.4
Target Milestone:	---
Platform:	Other
OS:	Linux
Latest Commit:		Version Fixed In:
Sentry Crash Report:

Description Bernie Innocenti 2016-02-21 23:45:14 UTC

After logging out from a desktop session, the kwalletd processes are still running under my uid (and presumably still unlocked?).

Is there a way to get them automatically killed?

Reproducible: Always

Steps to Reproduce:
1. configure pam_kwallet for your desktop session
2. log into KDE or other desktop from sddm or other display manager
3. kill the session (for example, with CTRL-ALT-BS)
4. login as root from the console and type "ps afxu | grep <your username>

Comment 1 derwesermann 2016-11-07 11:55:00 UTC

Hy
I'm not sure if i do this right posting in this thread but:

I got an issue with the kwalletmanager after starting it.
I saw: Lots of CPU usage. Sysgard showed me kwalletmanager,kwalletd5, AND kwallet starting 'n stoping and repaet. Seems to me like kwalletmanager is trying to start kwalletd while kwalletd5 is running. 

My openSuSE is also asking for a Wifi-key directly after resume from stand by. I can push cancel at the wifi-key dialog field and reconnect to the wifi with the networkmanager.

ok

Comment 2 derwesermann 2016-11-07 12:04:05 UTC

Solved:

I found kwalletmanager and kwalletmanager5 installed.
kwalletmanager is uninstalled, the kwalletmanager startmenu entry got deleted and everything is running fine.

Comment 3 Justin Zobel 2022-10-27 02:49:02 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 4 Bug Janitor Service 2022-11-11 05:18:11 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 5 Bug Janitor Service 2022-11-26 05:15:50 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!