Bug 233487 - kwalletd begins 100% CPU when wifi connects, maked KDE to exit to KDM login screen
Summary: kwalletd begins 100% CPU when wifi connects, maked KDE to exit to KDM login s...
Status: RESOLVED WORKSFORME
Alias: None
Product: kdelibs
Classification: Unmaintained
Component: kwallet (show other bugs)
Version: 4.3
Platform: Ubuntu Linux
: NOR crash
Target Milestone: ---
Assignee: Michael Leupold
URL:
Keywords: triaged
Depends on:
Blocks:
 
Reported: 2010-04-06 14:17 UTC by BORGULYA Gábor
Modified: 2018-10-27 04:20 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 BORGULYA Gábor 2010-04-06 14:17:08 UTC
Version:            (using KDE 4.3.2)
OS:                Linux
Installed from:    Ubuntu Packages

When I connect to any wifi with credentials stored in the KDE wallet a process called "kwalletd" appears with 100% CPU usage and stays there. The wifi connects slower than usual. After a few minutes hard disk becomes extremely busy, after an other few minutes the computer becomes irresponsive. After a quarter of an hour the computer exits to the KDM login screen.

Killing the kwalletd process is a workaround.
Comment 1 Christoph Feck 2013-09-12 21:42:12 UTC
This crash report is at least 3 years old and there were no further comments or status updates since then.

Therefore we believe that this crash is already fixed in recent KDE 4 versions or the backtrace is no longer applicable to the current KDE 4 sources.

If the crash still happens with a recent KDE version (4.10.5 or 4.11), please add an updated backtrace or provide steps to reproduce. For more information, see http://techbase.kde.org/Development/Tutorials/Debugging/How_to_create_useful_crash_reports

(To prevent automatic closing of this bug in the future, please set the bug status to ASSIGNED or CONFIRMED)
Comment 2 Andrew Crouthamel 2018-09-24 02:09:41 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 set the bug status 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 3 Andrew Crouthamel 2018-10-27 04:20:03 UTC
Dear Bug Submitter,

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!