Ancestors

Toot

Written by cyberwolfie@lemmy.ml on 2024-12-15 at 15:34

KDE Wallet suddenly acting up

https://lemmy.ml/post/23610018

=> More informations about this toot | More toots from cyberwolfie@lemmy.ml

Descendants

Written by MyNameIsRichard@lemmy.ml on 2024-12-15 at 15:38

The password could be the same as your login password?

=> More informations about this toot | More toots from MyNameIsRichard@lemmy.ml

Written by cyberwolfie@lemmy.ml on 2024-12-15 at 15:38

I would have assumed so, but it is not accepted.

=> More informations about this toot | More toots from cyberwolfie@lemmy.ml

Written by MyNameIsRichard@lemmy.ml on 2024-12-15 at 16:01

Hmm, the only other thing I can think of is that the wallet somehow got corrupted. Did you do a normal shutdown / restart? Is this after an update?

=> More informations about this toot | More toots from MyNameIsRichard@lemmy.ml

Written by cyberwolfie@lemmy.ml on 2024-12-15 at 16:07

I did an update over the week end, but I am pretty sure I rebooted between then and startup today. It is a long time since I’ve had to force shutdown.

=> More informations about this toot | More toots from cyberwolfie@lemmy.ml

Written by Ephera on 2024-12-15 at 16:20

Just to be sure, you didn’t either change your login password since your last reboot, right?

=> More informations about this toot | More toots from Ephera@lemmy.ml

Written by cyberwolfie@lemmy.ml on 2024-12-15 at 16:26

Nope.

=> More informations about this toot | More toots from cyberwolfie@lemmy.ml

Written by Natanael on 2024-12-15 at 16:04

You need kwallet_pam installed and configured right to make auto unlock work

=> More informations about this toot | More toots from Natanael@slrpnk.net

Written by cyberwolfie@lemmy.ml on 2024-12-15 at 16:10

Auto unlock seems to work completely fine with the new wallet I set up. And it tries to unlock the one I am having issues with (called “Default keyring”), but it seems the password just isn’t accepted anymore (whatever it was).

I don’t have any process named kwallet_pam running (only kwalletd6), and could not find anything related to kwallet_pam as an executable at least.

=> More informations about this toot | More toots from cyberwolfie@lemmy.ml

Written by ikidd@lemmy.world on 2024-12-15 at 17:32

I have yet to understand why Kwallet does the things it does sometimes. It varies by distro, and sometimes you fix it by putting in your login password, sometimes by putting in no password, sometimes make a new wallet, sometimes wipe the database. It’s pretty frustrating.

If you can’t change the password on the original keychain, I don’t think there’s a way to recover anything stored in it.

=> More informations about this toot | More toots from ikidd@lemmy.world

Written by cyberwolfie@lemmy.ml on 2024-12-15 at 17:50

That is what I feared. I tried both my login password and a blank password, and it refuses to open. I’ll wait to see if anyone has previously found a way to magically open it again, but I will probably need to scrap my Signal database and relink my computer without the chat history. It’s a bummer, but not a major issue for me.

=> More informations about this toot | More toots from cyberwolfie@lemmy.ml

Written by UnfortunateShort on 2024-12-15 at 23:46

Probably doesn’t help for recovery, but you can set an empty password and use polkit-based access control for wallets. You just need to check the box that says programs need to ask for access in Settings (not KWalletManager). Afterwards you will get a popup the first time they do and can then choose to give them permanent access.

=> More informations about this toot | More toots from UnfortunateShort@lemmy.world