https://bugs.kde.org/show_bug.cgi?id=509680
--- Comment #9 from michaelk83 <mk.mat...@gmail.com> --- (In reply to CarlosE from comment #8) > Can't kwallet-pam unlock the existing KDE wallet process? ksecretd provides > a seemingly relevant org.kde.KWallet.pamOpen method. Maybe, but if ksecretd needs to unlock as soon as it's launched, then you'd still get the password prompt before kwallet-pam runs. > > Maybe KWallet can delay its first non-PAM start for a sec or two to > > give PAM a chance to unlock it first... > > At least on my system, the delay between spawning ksecretd instances is > bigger than that (around five seconds). Yea, then that doesn't really solve it either. A 5 sec delay would definitely be noticeable to users, and could potentially cause other problems. If we need to change how xdg-desktop-portal (or its KDE backend) or kwallet-pam are launched and initialized, that could be a rather complex fix. For the moment, my recommended workaround is to copy the org.freedesktop.impl.portal.desktop.kwallet.service autostart file into ~/.local/share/dbus-1/services/ and set its Exec to /usr/bin/true. This is equivalent to removing the file, but won't be affected by package updates. -- You are receiving this mail because: You are watching all bug changes.
