https://bugs.kde.org/show_bug.cgi?id=509680
--- Comment #8 from CarlosE <[email protected]> --- (In reply to michaelk83 from comment #7) > So this looks like an internal initialization process within > xdg-desktop-portal, possibly triggered by kcminit_startup. I don't think > there's much we can do about that, nor about how SDDM interacts with KWallet > PAM. Can't kwallet-pam unlock the existing KDE wallet process? ksecretd provides a seemingly relevant org.kde.KWallet.pamOpen method. > 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). -- You are receiving this mail because: You are watching all bug changes.
