Why is kwalletmanager sucking up 100% of cpu? See this screen-shot:

- - http://www.upquick.com/temp/kwalletmgr.jpg - -

The whole kwallet thing seems like a nuisance to me and I disabled it. But today, my system slowed down to almost a halt and 'top' revealed that kwallet was apparently the cause. How could it still be causing such problems when it has been disabled?

I was able to find the process with 'ps -ef' and kill it, but I do not understand why kubuntu/kde implements (forces the use of) so many nuisance things like this (and many others) as default functions instead of offering them as options.

You are not forced to use KWallet at all, in fact it can be disabled. But the 100% CPU issue may be a result of different factors: first of all, is it intermittent or frequent? Secondly, if it appears again, would you be able to reproduce the issue on a new user account? Thirdly, are there any suspicious messages in ~/.xsession-errors?

Thank you for your response to the first part of my question.

I did not see any suspicious messages, but will report back if/when this occurs again.

Regarding the second part of my question: ". . . why does KDE impose so many things like this as default functions instead of offering them as options?"

kwallet is, indeed a nuisance (for me, and I suspect for a lot of other people). It is counter-productive to Linux/KDE adoption to force what should be discretionary options on users, especially when such "defaults" create problems and impede progress in trying to implement systems.

The web is awash with complaints about code-jockey inventions being made "defaults" and coercing their use until users can find out how to disable them. Things like forcing the annoying cashew and needless fancy effects on everyone is definitely *not* user-friendly. Some of this annoying stuff can be disabled, but why should users be forced to have to find out how to disable this annoying stuff? And why is there not even an option to get rid of garbage like the annoying, intrusive cashew with no way to get rid of it. Such stuff should not have to be disabled, but rather should be offered as options.

Coerced implementation of non-essential functions is not helpful.

Write if this post einar helped .

Secondly, if it appears again, would you be able to reproduce the issue on a new user account?

Most errors you will have in /var/log
search any txt file , like Xorg.0.log, xdm.log, user.log, pm-powersave.log, kdm.log, dmesg
Xorg.0.log and kdm.log may be the most important.
- How find error?
You can use option "Find" in text editor. Search word error
You can also find in KSystemLog from menu softaware if you have installed. ( In KSystemLog clic 2x or 1x in error for more inf. )
You will know error. Next, you can try debug kwallet
Open terminal and copy from menu command like:
kwalletmanager %u
You can istall strace and try use ( sometimes help where soft stopped )
strace kwalletmanager %u
You can install and use valgrind ( this works very slow, and You need know how use this -I don't know how use)
valgrind -v kwalletmanager %u
( we have also ddd and gdb debugers )

( PS: I use PClinux , You too? ,For me kwallet not working , but this can be dri problem. Kwallet package name's kde-utils-kwallet, you can uninstall if you like,. What driver and graphics card you used?)
Sorry, some interfering.
Please debug this kwalletmanager, I have like error, maybe you have too?
viewtopic.php?f=66&t=102251
quote

Nepumuk (virtuoso-t) often uses a lot of CPU

With regards to KWalletManager using excessive amounts of CPU - I suspect this was one off bad behaviour, likely caused by you disabling KWallet and it attempting to do something at the same time, causing it to go into a loop.

Note that if you find KWallet 'annoying' but still want passwords to be saved, I would suggest using a wallet with a blank password (which will lead KWallet to not prompt you for passwords at all).

tele wrote:Write if this post einar helped .

Secondly, if it appears again, would you be able to reproduce the issue on a new user account?

Most errors you will have in /var/log
search any txt file , like Xorg.0.log, xdm.log, user.log, pm-powersave.log, kdm.log, dmesg
Xorg.0.log and kdm.log may be the most important.
- How find error?
You can use option "Find" in text editor. Search word error
You can also find in KSystemLog from menu softaware if you have installed. ( In KSystemLog clic 2x or 1x in error for more headshots inf. )
You will know error. Next, you can try debug kwallet
Open terminal and copy from menu command like:
kwalletmanager %u
You can istall strace and try use ( sometimes help where soft stopped )
strace kwalletmanager %u
You can install and use valgrind ( this works very slow, and You need know how use this -I don't know how use)
valgrind -v kwalletmanager %u
( we have also ddd and gdb debugers )

( PS: I use PClinux , You too? ,For me kwallet not working , but this can be dri problem. Kwallet package name's kde-utils-kwallet, you can uninstall if you like,. What driver and graphics card you used?)
Sorry, some interfering.
Please debug this kwalletmanager, I have like error, maybe you have too?
viewtopic.php?f=66&t=102251
quote

Nepumuk (virtuoso-t) often uses a lot of CPU

Installed valgrind also, do not know how to implement it.

If you can no longer reproduce the behaviour, there is no reason to worry about Valgrind or strace. If you are still experiencing this issue, then generating a backtrace using GDB (with debug symbols available) once it has entered this loop will be more helpful.

Another thing you could look out for is other processes with abnormally high CPU usage, such as kded4.

Valgrind and strace are tools usually used by developers (or others triaging a issue) to determine the resource usage of an application and how it is behaving, and can be particularly helpful in determining why memory leaks are occurring for instance.