https://bugs.kde.org/show_bug.cgi?id=524373
--- Comment #11 from Cherkah <[email protected]> --- The issue persists on Fedora 44 with kf6-kwallet-6.30.0-1.fc44 (KF 6.30), which should contain the d966c135 fix. Environment: - kf6-kwallet-6.30.0-1.fc44 - kf6-kwallet-libs-6.30.0-1.fc44 - pam-kwallet-6.30.0-1.fc44 - Plasma Login Manager - KeepSecret (Flatpak) pam_kwallet5 opens the session successfully and launches ksecretd with the expected socket path (/run/user/1000/kwallet5.socket). However, shortly after, xdg-desktop-portal activates a second ksecretd instance that lacks the PAM socket ("Lacking a socket, pipe: 0 env: 0"), and the wallet ends up locked from KeepSecret's perspective. Relevant log lines: ``` pam_kwallet5(plasmalogin:session): pam_kwallet5: pam_sm_open_session pam_kwallet_init: final socket path: /run/user/1000/kwallet5.socket ksecretd[2010]: Loaded style "breeze" from cached data ksecretd[3216]: Lacking a socket, pipe: 0 env: 0 xdg-desktop-portal: Backend call failed: Could not activate remote peer 'org.freedesktop.impl.portal.desktop.kwallet': unit failed ``` So the D-Bus activation race described in 509680 still seems to occur, or the state synchronization fix from d966c135 does not cover this case. Could you confirm whether this is a known remaining case, or whether a different fix is needed? Operating System: Fedora Linux 44 KDE Plasma Version: 6.7.5 KDE Frameworks Version: 6.30.0 Qt Version: 6.11.2 -- You are receiving this mail because: You are watching all bug changes.
