Version: (using KDE 4.3.0) OS: MS Windows Installed from: MS Windows Steps to reproduce: * run koqnueror * enter a password in some form * konqueror shows a message to store the password in wallet, ckick "Store". * the kwallet wizzard appears, process to create a new wallet. * after wallet is created there are several kwallet.exe processes eating up the memory. * after every visit of a page with a login form, a new instance of kwalletd.exe is added.
Thanks for reporting this bug. Unfortunately I don't have means to debug this. If you're able to debug this issue, I could give you some pointers though: Starting kwalletd.exe is managed by the application using it. The code to start it is in kdelibs/kdeui/util/kwallet.cpp:769. I assume that the application doesn't detect if the service is already started (isServiceRegistered("org.kde.kwalletd")) and thus starts a new instance for every call.
I can confirm this. This bug is very irritating because every kwalletd process is consuming quite big amount of memory. KWallerManager starts even more processes (infinitive?), I had to kill it to prevent system lock...
I can't reproduce it here, what compiler version are you using, msvc, mingw or mingw4?
I am using KDE 4.3.0 compiled for profile: End User - MSVC 32Bit. Windows XP SP3
I am using: KDE 4.3.0 compiled for profile: End User - MSVC 32Bit. Windows XP SP3 Clean install, I've removed all configs and I've installed it again.
Did you use the 4.3.0 installer to install KDE4 or compile yourself? We're really having trouble to reproduce here.
Hi, I used kde installer, End user, MSVC32bit. Windows XP, sp3
I can confirm this behaviour with Kopete. KDE4.3 Installed with installer, MSVC 32bit installed in end user mode.
I used installer. How kwallet processes are discovered? Via Dbus and its name? While testing I was not using any firewall or antivirus software.
After some test: I renamed kwalletd.exe to kwalletd2.exe, I run kwalletd2.exe and kwalletmanager.exe. Everything was fine, I could create new wallet, configure it etc. Disabling wallet subservice in configuration shuts down kwalletd process. QDBusVierer is showing "org.kde.kwalletd" and something like: ":1.521", I can read its properties. If I run another kwalletd it is presenting itself as something like: ":1.524" only.
Yeah, the client detects if kwalletd is running by checking for org.kde.kwalletd on the D-Bus. If it's there and it still doesn't detect it something's seriously borked here.
(In reply to comment #11) > Yeah, the client detects if kwalletd is running by checking for > org.kde.kwalletd on the D-Bus. If it's there and it still doesn't detect it > something's seriously borked here. I can't debug this, I am using KDE for Windows only in work, so I can't spend too much time on this issue :( As a workaround I've just renamed kwalletd.exe, I don't need this feature.
Hi there, I just wanted to confirm this bug - this time for amarok on windows (today's packages for amarok and VLC) I followed the direction on this page (http://amarok.kde.org/wiki/Download:Windows) to install. Used msvc version. I don't have KWallerManager, but kwalletd instances pile up while running amarok (at around 10MB virtual memory each). I have renamed kwalletd as a bit of a stopgap, as it didn't seem to be working properly for storing the lastfm password anyway.