Bug 511471

Summary:	KWallet can end up not auto unlocked caused by various conditions (e.g. temporarily read-only home) and then there's no obvious way to fix it
Product:	[Applications] kwalletmanager	Reporter:	Ellie <el>
Component:	general	Assignee:	Valentin Rusu <valir>
Status:	REPORTED ---
Severity:	normal
Priority:	NOR
Version First Reported In:	25.08.1
Target Milestone:	---
Platform:	postmarketOS
OS:	Linux
URL:	https://discuss.kde.org/t/i-broke-my-kwallet-auto-login/40205
Latest Commit:		Version Fixed/Implemented In:
Sentry Crash Report:

Description Ellie 2025-11-01 16:29:46 UTC

SUMMARY

It seems like KWallet can end up not auto unlocked caused by various conditions (e.g. temporarily read-only home), as this discussed here: https://discuss.kde.org/t/i-broke-my-kwallet-auto-login/40205 As you can see, multiple users seem to have run into this, and there doesn't seem to be any obvious way to fix it. Instead, KWallet is locked up when the session opens, and any program accessing it will lead to a manual kwallet password prompt which is cumbersome, but even worse, e.g. wifi auto connect apparently won't work.

Regarding the fixing, here are ways I found of not fixing it: 1. there is no "Reset KWallet situation" button in the autostarts pane in the KDE system settings. 2. The "Defaults" button in the KDE wallet pane in the KDE System Settings doesn't repair this situation either. 3. Rebooting doesn't help either.

STEPS TO REPRODUCE

1. Unknown exact condition that results in KWallet auto unlock not being set up on some systems
2. Try to fix KDE Wallet auto unlock

OBSERVED RESULT

There seems to be no working and obvious way to get it fixed.

EXPECTED RESULT

There is a working and obvious way to get it fixed.

SOFTWARE/OS VERSIONS

Windows: 
macOS: 
(available in the Info Center app, or by running `kinfo` in a terminal window)
Linux/KDE Plasma: postmarketOS Edge
KDE Plasma Version: 6.5.1
KDE Frameworks Version: 6.19.0
Qt Version: 6.9.3

ADDITIONAL INFORMATION

Comment 1 Ellie 2025-12-20 03:31:20 UTC

It seems like auto-connecting to a wifi is also affected by this, even with "All users may connect to this network" enabled. I wonder, isn't there some sort of command to have KDE reinitialize all the startup scripts and services a session should have, without downright nuking everything?

Whatever is missing doesn't seem to be part of the visible "user-specified startup items", since the "Autostart" section of KDE on one of my other machines where KWallet unlock and wifi auto-connect works as intended, says: "No user-specified autostart items, Click the Add New button to add some"