Created attachment 188385 [details] Screenshot of KDE Wallet service asking to create a new wallet Short: If I login, I am prompted to unlock my wallet via kwalletmenager. Side info: I use an OpenPGP smartcard for this, which works fine. However, if I do not enter the PIN in time, KWalletmanager goes haywire and wants to create a completely new wallet with a weird name: "Did not receive a reply. Possible causes include: the [...] was broken". See attached screenshot. This is very bad; in the PC of my wife I found such a .kwl/.salt file and could not comprehend how it happens. Now, here on my PC, I'm able to replicate this just by letting KWalletManager tun into a timeout. EXPECTED RESULT: If the user forgets to enter the unlock password / PIN, KWalletManager should recognize that and should kindly remind the user to unlock the wallet. Ideal: other software waiting for KWalletManager to provide them stored passwords should not misbehave (for that I have to file subsequent bug reports). STEPS TO REPRODUCE 1. Login 2. Ignore KWalletManager asking for the unlock credentials 3. Wait 10-30s for a window asking to create a weird new wallet SOFTWARE/OS VERSIONS Gentoo Linux kde-apps/kwalletmanager-25.12.1 kde-frameworks/kwallet-5.116.0-r3 kde-frameworks/kwallet-6.22.0 kde-plasma/kwallet-pam-6.5.4 (installed but not used) The PC of my wife has an older ("stable") combo of KDE/Plasma, which shows the same behavior. So, this bug was not recently added.
As a side note, my wife regularly is distracted by our kids and this stuff happens. Then, as another usability issue, KMail/Kontact starts asking for transport credentials which spawns a set of similar windows. Now, what happens: my wife sees these windows asking for a password, and she enters the PIN of the smartcard. Result: - Email is broken: the server denies the wrong login credentials - The stored passwords in KWalletManager were replaced with the PIN and are lost... if not stored somewhere else This happens a lot here (once a month), and is a user error. However, seeing this, for me that is a workflow issue of KWalletManager. The user should be protected better here.
Seems to be a duplicate of 514104
(In reply to Florian Evers from comment #2) > Seems to be a duplicate of 514104 Yep. (In reply to Florian Evers from comment #0) > Ideal: other software waiting for KWalletManager to provide them > stored passwords should not misbehave (for that I have to file subsequent > bug reports). Unfortunately, this would be difficult. If the wallet cannot be opened in time, either the wallet will return an error (once 514104 is fixed), or the request will time out at the system level. Either way, the client application's behavior at that point is out of KWallet's hands. A well-behaved app may try again, but that's not guaranteed. *** This bug has been marked as a duplicate of bug 514104 ***