SUMMARY After booting up and logging in via sddm, kded5 tries to open my wifi connection with password stored in kwallet. I am getting following prompt: The application kded5 has requested to open the wallet 'kdewallet'. Please enter the password for this wallet below. STEPS TO REPRODUCE 1. Just start the system OBSERVED RESULT Wifi connection is blocked until i manually enter the password. EXPECTED RESULT kwallet is automatically unlocked via kwallet-pam at user login. SOFTWARE/OS VERSIONS Operating System: Arch Linux KDE Plasma Version: 5.26.1 KDE Frameworks Version: 5.99.0 Qt Version: 5.15.6 Kernel Version: 6.0.2-arch1-1 (64-bit) Graphics Platform: X11 Processors: 24 × AMD Ryzen 9 3900X 12-Core Processor Memory: 62.7 GiB of RAM Graphics Processor: NVIDIA GeForce RTX 2060/PCIe/SSE2 Manufacturer: TUXEDO Product Name: TUXEDO_Book_XA1510 ADDITIONAL INFORMATION I set up a new kwallet according to https://wiki.archlinux.org/title/KDE_Wallet login password is the same as kwallet password. kwallet name is kdewallet. I dont use auto-login. > journalctl -b | grep wallet > Oct 20 16:35:58 eedev03 systemd[1095]: Started Unlock kwallet from pam credentials. > Oct 20 16:36:01 eedev03 dbus-daemon[1109]: [session uid=892001943 pid=1109] Activating service name='org.kde.kwalletd5' requested by ':1.11' (uid=892001943 pid=1180 comm="/usr/bin/kded5") > Oct 20 16:36:02 eedev03 dbus-daemon[1109]: [session uid=892001943 pid=1109] Successfully activated service 'org.kde.kwalletd5' > Oct 20 16:36:02 eedev03 kwalletd5[1468]: Application ' "kded5" ' using kwallet without parent window! Content of /etc/pam.d/sddm #%PAM-1.0 auth include system-login -auth optional pam_gnome_keyring.so auth optional pam_kwallet5.so account include system-login password include system-login -password optional pam_gnome_keyring.so use_authtok session optional pam_keyinit.so force revoke session include system-login -session optional pam_gnome_keyring.so auto_start session optional pam_kwallet5.so auto_start I tried a lot, as it is a pretty popular problem, but every forum entry i read either quoted that the bug was fixed, or didnt exactly match my behaviour. The only way i got it to work was not setting a password at all for the wallet (what i dont want to do). Hope someone can help.
Sorry for getting back to this very late. Can you still reproduce this on plasma 6.5?