I have configured kontact (akonadi) (4.13.3) for syncing my mails/contacts/addressbook with my owncloud. I also run an owncloud client (1.5.0). (under kubuntu 14.04 LTS) Every startup I got prompted to enter several passwords including the password for the kwallet. When I enter the kwallet password - closing all other password prompts - i got no more prompts again, so it seems that applications get there password from the wallet successfully. What I think about this bug is, that there is no queue (with an appropriate timeout, if it is even neccessary?!) for applications trying to get there password stored in the wallet, if the wallet is not open. As I want to use syncing my files/mails/calendar/addressbook every startup i get 5 password prompts. Reproducible: Always Steps to Reproduce: 1. start my kubuntu 14.04 LTS (with autologin) 2. that's it Actual Results: Got 5 password prompts, 4 from akonadi and owncloud client, one from kwallet. Expected Results: I want to get just one password prompt from kwallet and all the applications wait, until I enter the correct kwallet password. Getting the password should always run at first with kwallet. I have this bug for many versions of KDE SC. But now I thought it's time to tell you about it.
Is anyone out there who has the same problems? please help and please answer! Best regards, JR
Well, kwalletd actually has an internal queue and it should only prompt one password dialog upon start. Could you please do a test for me. Just upon session start, when you have the several password prompts, could let them like that, then open a konsole (or a terminal of your choice) and tell me how many kwalletd processes do you have on your system?
*** Bug 340135 has been marked as a duplicate of this bug. ***
I have similar issues, but with the Wifi password which I described here https://bugs.kde.org/show_bug.cgi?id=340135 (marked as duplicate) I'm getting two prompts: one from kwallet gpg and one for the wifi password. When I enter the gpg password and close the wifi password dialog, then I need to manually reconnect to the wifi network by clicking "Connect", which will then use the kwallet password. The kwallet timeout is possibly too short.
it's just one daemon: jr@x:~$ ps -ef|grep wallet jr 2789 1498 1 23:00 ? 00:00:00 /usr/bin/kwalletd jr 2884 2463 0 23:01 pts/2 00:00:00 grep --color=auto wallet jr@x:~$ it looks like a timeout or a full queue.
Today I had more time to test, but with the same result, just one daemon is running. And I have still a view password prompts. Today I entered the password to open the wallet and closed (cancelled) the others. It seems different applications have different behaviour. The owncloud client needs to login manually (or a restart) to get his password. On the other hand, the akonadi resource for the caldav calendar and addressbook, seems to try to get the password(s) from kwalletd again. But the dialogs for the passwords at boot time remain.
@Valentin Rusu: Do you know/find the problem?
I have the same problem. It's indeed quite annoying. I use the gpg backend, I don't know if this is related to the issue.
I have the same problem in Plasma 5 under archlinux. GPG based wallet, two dialogs: a pinentry one and the kwallet one. If I follow the archlinux wiki on how to set up gpg-agent to use pinentry-kwallet, initially I get only the kwallet dialog, but after a while I get one dialog per email account I have set up, plus a pinentry one. If I close all of the email ones, and type in the gpg password on the pinentry one, I get asked if I want to store that password in kwallet. I click on yes, and it doesn't store it. Then everything works fine until the next login. So far I have disabled gpg-agent, and I get "just" the two dialogs.
(In reply to Pedro from comment #9) > I have the same problem in Plasma 5 under archlinux. GPG based wallet, two > dialogs: a pinentry one and the kwallet one. > If I follow the archlinux wiki on how to set up gpg-agent to use > pinentry-kwallet, initially I get only the kwallet dialog, but after a while > I get one dialog per email account I have set up, plus a pinentry one. If I > close all of the email ones, and type in the gpg password on the pinentry > one, I get asked if I want to store that password in kwallet. I click on > yes, and it doesn't store it. Then everything works fine until the next > login. So far I have disabled gpg-agent, and I get "just" the two dialogs. Oops! If you store gpg PIN in kwallet, and the wallet is GPG-based, then you'll get a loop problem. As opening the wallet would require the PIN :-) On my system I'm using gpg-agent, but I let it use the usual pinentry tool that will ask me for the PIN only once during the entire session. Subsequent wallet opening occur silently.
(In reply to JR from comment #7) > @Valentin Rusu: Do you know/find the problem? This problem requires some important refactoring and I'm maintaining kwallet in my spare time. But I think I'll eventually fix it.
Thanks for the quick reply. I just didn't know if I was doing it right. It's no big deal, but I'm glad you are aware of the issue.
Mmh, I'm not sure, if my issue is the same: I'm using tumbleweed, Kmail, Kwallet, autologon and GPG based Kwallet encryption When I start the notebook and I go for a coffee, then the KwalletDialog is open for a while. Within my coffee-getting-time Kmail is starting, asking KWallet for the some password to open IMAP email boxes, some passwords. Because I didn't type in the Passphrase to encrypt the GPG key for starting up Kwallet, Kmail is not able to retrieve the requested passwords. After I open Kwallet, which means I put in the passphrase, Kmail is not requesting again the passwords; Kmail wants to have typed in the email-boxes passwords again :-( Same with the wifi connection. So I assume the issue is between the KWallet connector and the application managing their passwords in Kwallet.
Hi, I also have this problem. After start KDE kwallet ask me a several times a passoword. I am using: 1) kwallet 5.15.0-1 2) kwalletmanager 15.08.3-1 in arch linux. Regards.
same issue for ktp/telepathy-kde, it tries to connect anyway but fails as there are no credentials. I dont think this issue is minor as i breaks every app using kwallet.
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!
I think this still happens notably with Nextcloud using QtKeychain, it asks for the paswords but if it hits the timeout it just tries to get a new token. The symptoms depend on the app but the underlying issue is still there.