https://bugs.kde.org/show_bug.cgi?id=509680
--- Comment #15 from michaelk83 <mk.mat...@gmail.com> --- So the sequence seems to be: 1. Qt initialization runs very early during login (and on each Qt app start). 2. It calls org.freedesktop.portal.Desktop to check for color picking support. 3. This triggers some internal dependencies in xdg-desktop-portal. 4. Which leads to an early call to org.freedesktop.impl.portal.desktop.kwallet (e.g. by calling org.freedesktop.portal.Secret). 5. And this launches ksecretd via the new DBus service autostart file, before kwallet-pam had a chance to unlock it. (6. kwallet-pam still runs, but is too late, and simply aborts.) This gives us the following workarounds, so far: - Set QT_NO_XDG_DESKTOP_PORTAL=1 (e.g. in /etc/environment): breaks Qt color picking functions (and maybe some other things), but all the portals should still work, in principle. Or: - Override org.freedesktop.impl.portal.desktop.kwallet.service (place a copy in your ~/.local/share/dbus-1/services/). Point its Exec at /usr/bin/false to let DBus know that something went wrong, or at /usr/bin/true to ignore it silently. This breaks KWallet auto-start when requested through the Secret portal (bug 508870). Or: - Disable the Secret portal itself in your ~/.config, as explained in https://wiki.archlinux.org/title/XDG_Desktop_Portal#Configuration . Or: - Leave things as is, which leaves kwallet-pam broken, but everything else works. A proper fix may need to focus on the internal dependencies in the xdg-destktop-portal-kde implementation (steps 3-4 above). Or on the SDDM -> kwallet-pam startup sequence, but that may be more difficult, and would only fix this with SDDM. -- You are receiving this mail because: You are watching all bug changes.
