SUMMARY After updating to https://invent.kde.org/frameworks/kwallet/-/commit/4af84b4e8908764439cfe27d71d1d44ae0cdd116, kwallet no longer autostarts via kwallet-pam. kwallet-pam calls /usr/bin/kwalletd6 --pam-login 13 14 as root and it crashes (This application failed to start because no Qt platform plugin could be initialized....). Should kwallet-pam start ksecretd now? STEPS TO REPRODUCE 1. Have pam-kwallet installed 2. Log in OBSERVED RESULT kwallet does not start, and secrets are not unlocked automatically. EXPECTED RESULT kwallet should start successfully and unlock the wallet at login via kwallet-pam. SOFTWARE/OS VERSIONS Windows: macOS: (available in the Info Center app, or by running `kinfo` in a terminal window) Linux/KDE Plasma: KDE Plasma Version: KDE Frameworks Version: Qt Version: ADDITIONAL INFORMATION
Confirmed. Since the move to ksecretd, kwalletd crashes early during the login, and that causes a delay of ~10-15 seconds to the login until the wallet window is displayed. Once the wallet is unlocked, the rest of the session starts.
(In reply to Luca Beltrame from comment #1) > Confirmed. Since the move to ksecretd, kwalletd crashes early during the > login, and that causes a delay of ~10-15 seconds to the login until the > wallet window is displayed. Once the wallet is unlocked, the rest of the > session starts. While Qt complains about being unable to load a platform plugin, I wonder if it's a red herring (happens on both X11 and Wayland sessions).
I built kwallet-pam with -DKWALLETD_BIN_PATH=/usr/bin/ksecretd and it seems to work fine.
The reason (thanks to Fabian Vogt for noticing) is that the `kwalletd6` command (the thin wrapper around ksecretd) dropped the --pam-login option, so it will no longer work as expected.
Might https://invent.kde.org/frameworks/kwallet/-/commit/d79ef6bfbc59aa82a7e22df883b70abc25b569a1 fix it?