Created attachment 57222 [details] Screenshot of the empty kdewallet Version: unspecified (using KDE 4.5.1) OS: Linux At startup, I was asked for my wallet password, as usual. But now the kdewallet is completely empty, no folders for password, input fields, anything. (See attached) I don't see any error messages on the screen, but then again, I've no idea which log file(s) to look in for kwallet errors. Reproducible: Didn't try
Created attachment 57238 [details] Autostart script that triggers the bug The problem appears to be with an autostart script that talks to kwallet over dbus in order to get the pass phrase for my ssh key. When I disabled the script and restarted, everything is in order with the wallet. Putting the attached file into ~/.kde/Autostart will reproduce the bug.
Not that it's the second invocation of kwallet-askpass.sh in the autoscript that causes the error. Having only one (for the default identity) works fine.
Created attachment 57239 [details] The script that talks to kwallet over DBUS The autostart script from attachment #57238 [details] relies on this script to actually talk to kwallet over DBUS.
Possibly a duplicate of 254198
@Davor are you still able to reproduce this ? I didn't manage to reproduce the crash using your scripts with KDE 4.10.5. Maybe I did something wrong: the script never returns any password. Could you try again ?
(In reply to comment #4) > Possibly a duplicate of 254198 FYI, bug 254198 is fixed in KDE SC 4.11.2
Sorry, I can't test with a more recent version of KDE because I don't use it any more. Davor On 2013-10-04, at 3:27 PM, Vincent Petry <PVince81@yahoo.fr> wrote: > https://bugs.kde.org/show_bug.cgi?id=266228 > > Vincent Petry <PVince81@yahoo.fr> changed: > > What |Removed |Added > ---------------------------------------------------------------------------- > CC| |PVince81@yahoo.fr > > --- Comment #5 from Vincent Petry <PVince81@yahoo.fr> --- > @Davor are you still able to reproduce this ? > > I didn't manage to reproduce the crash using your scripts with KDE 4.10.5. > Maybe I did something wrong: the script never returns any password. > > Could you try again ? > > -- > You are receiving this mail because: > You reported the bug.
Sorry to hear about that, but still thanks for your feedback.
This morning when turning on my laptop and logging in to KDE this issue happened again. At startup I had knetworkmanager (wifi password) + owncloud client that were accessing kwallet. ownCloud is using dbus and the string I saw in the dialog was the one from ownCloud. This caused kwallet to bug again, with the following symptoms: 1) Couldn't connect to the internet as knetworkmanager was unable to retrieve the password 2) ownCloud couldn't connect either 3) When I tried kwalletmanager, it also also asked for the password but upon entering it my wallet appeared empty. I think this ticket should be reopened. I'll activate debugging for next time this happens (it doesn't always happen, race condition). It seems it's more likely to happen when the computer has just been turned on and the kde libs haven't all be preloaded yet.
This is on KDE 4.10.5 on openSUSE 12.3. ownCloud client is version 1.4.1 and is using libqtkeychain0-0.20130221 to access kwallet through dbus.
Has happened to me too. kdewallet is empty. I use ownCloud, too. I had some trouble getting it to work again yesterday. I reinstalled kwallet. But what it yesterday and actually just now reenabled was disabling and reenabling it in the system settings. BTW: Kwalletmanager was open in this process and crashed ( went to a non reactive state trying over and over again to connect to kwalletd ). Ctrl-C in shell where I started it from took care of that.
Additional irregular behaviour in this situation described in https://bugs.kde.org/show_bug.cgi?id=327086
Error messages repeating in shell: kwalletmanager(4953)/kdeui (Wallet): Couldn't start kwalletd: "KDEInit kann „/usr/bin/kwalletd“ nicht starten"
I am experiencing the same issues kwallet is broken, wifi won't connect because it is waiting for authorization. I was doing a workaround to open manage connections/kde control module for network connections. I get an error "did not receive a reply. possible causes include the remote application did not send a reply" I then click ok enter the password for the wifi access point I need to connect to and then it connects. I have temporarily disabled the kwallet but would like this fixed so that owncloud and wifi work again. willing to test to get it working again.
Dear Bug Submitter, This bug has been stagnant for a long time. Could you help us out and re-test if the bug is valid in the latest version? I am setting the status to NEEDSINFO pending your response, please change the Status back to REPORTED when you respond. Thank you for helping us make KDE software even better for everyone!
Dear Bug Submitter, This is a reminder that this bug has been stagnant for a long time. Could you help us out and re-test if the bug is valid in the latest version? This bug will be moved back to REPORTED Status for manual review later, which may take a while. If you are able to, please lend us a hand. Thank you for helping us make KDE software even better for everyone!
Thank you for reporting this issue 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!
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!
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!