Version: Version 1.2.4 (enterprise 0.20070907.709405) (using KDE 4.0.0) Installed from: Ubuntu Packages OS: Linux Hi Not sure if this is the right place for this - but it occurs when Kontact starts up. Feel free to move it to the correct place if it doesn't belong here. When starting Kontact in KDE4.0, the application prompts for the KDE3 wallet manager password, where all my mail passwords are stored. On entering the correct password, Kontact becomes unresponsive. Soon after that kded (kde 3) starts using 99% CPU. To fix this I have to open a shell and "kill -KILL <kded 3 pid>". When that happens Kontact becomes responsive and prompts for all the various passwords for my mail accounts. To get Kontact using the wallet again, I have to: 1.close Kontact 2.kill kwalletmanager if it is running and run /usr/bin/kwalletmanager --kwalletd again 3.optionally kill kded (3) again if 2 doesn't work 4.run kontact again 5.go back to 1 and start again if it doesn't work. This problem is not evident in KDE3.5 so it's some sort of issue with KDE4 and kwalletmanager and kontact. One solution may be to get Kontact (or any KDE3 app that isn't yet KDE4) using the KDE4 wallet manager which works quite well. Is there any way for Kontact to do that ? If any other info is needed, please ask. It may be related to this: https://bugs.launchpad.net/ubuntu/+source/kdelibs/+bug/86168 Thanks!
This sounds a lot like a kdelibs bug or a some issue in your distribution, changing product and summary. This happens also for other KDE3 applications that use the wallet, right? >One solution may be to get Kontact (or any KDE3 app that isn't yet KDE4) using the KDE4 wallet manager This is not possible unfortunately, see also bug 156397.
Hi Thomas I don't know about other KDE3 apps as kontact is the only one I use. The weird thing is that kontact works fine in KDE3.5 but starting it up and using kwalletmanager take a few goes before it works with any stability. So it must be something to do with kwalletmanager (3) running in a KDE4.0 environment. I also get kwalletmanager (3) crashing at startup and emitting a SIGSEGV (i restart it manually). I assume that is the trigger. Getting Kontact and Kwallet running in KDE4.0 is royal pain because of this.
I tested with Kontact from openSUSE 10.3 using a self compiled KDE4 session. Kontact opens fine the KDE3 kwallet, no high CPU usage is visible. You might try to attach gdb to kded when that one goes crazy and get a backtrace.
Interestingly enough, I read about a similar issue I found while googling (http://ubuntuforums.org/showthread.php?t=428506) that involved kded eating 100% CPU and removing the kwallet and kwalletmanager config rc files: rm ~/.kde/share/config/kwalletrc rm ~/.kde/share/config/kwalletmanagerrc KDE/kwallet recreates these after logging in and out and starting Kontact after doing this doesn't cause any problems. Unfortunately I didn't save a copy of the files - Had a look at them before removing to check their wasn't anything major in their contents. It may reoccur if I boot back into KDE3.5 and then back into 4.0 - will test that. kwalletmanager (3) still crashes on 4.0 startup. HTH
Do you have a backtrace of the kwalletmanager(3) crash?
I'll install the debug packages and see what i get...
Does this bug still happen? I actually don't quite figure what might be causing this and I currently don't have an environment to test it. Actually the kwalletd kde3 module and the kde4 one shouldn't have interacted in the first place as the former is using DCOP, the latter DBUS (and kded and kded4 shouldn't have trouble running concurrently). Even if this was a problem it should have been fixed with KDE 4.1 where kwalletd is a separate binary. Does the bug still happen, did you have a chance to try kontact from KDE3 with kded4 from 4.1?
No, it doesn't happen anymore - I've upgraded to Kubuntu 8.10 (KDE 4.1.2) so am only using the KDE4 wallet. The only KDE3 app I use now is Quanta. Sorry I can't be of more assistance.
No problem. As you seem to have been the only one who has been able to reproduce this I'll close this for now. Anyone, please reopen if you face something similar (which is unlikely given that there's almost no KDE3 apps using the wallet that don't have their KDE4 equivalent yet).