https://bugs.kde.org/show_bug.cgi?id=509680
--- Comment #26 from CarlosE <[email protected]> --- I can't comment on the linked PR due to "Your account has been blocked.", but it seems not to work on my machine. I instructed pam_kwallet to invoke a wrapper that logs ksecretd's debug output, and got this: Jan 17 12:26:16 kf.wallet.ksecretd: ksecretd5: Checking for pam module Jan 17 12:26:16 kf.wallet.ksecretd: ksecretd5: Got pam-login param Jan 17 12:26:16 kf.wallet.ksecretd: ksecretd5: Waiting for hash on 14 Jan 17 12:26:16 kf.wallet.ksecretd: ksecretd5: waitingForEnvironment on: 15 Jan 17 12:26:17 kf.wallet.ksecretd: ksecretd5: client connected Jan 17 12:26:17 kf.wallet.ksecretd: ksecretd5: client disconnected Jan 17 12:26:17 kf.iconthemes: Icon theme "" not found. Jan 17 12:26:17 kf.imageformats.plugins.hdr: Unknown HDR format: "" Jan 17 12:26:17 kf.imageformats.plugins.xcf: XCF: read called on non-XCF file Jan 17 12:26:17 kf.crash: Could not find drkonqi in search paths: QList("/usr/bin", "/usr/lib/qt6", "/usr/lib") Jan 17 12:26:17 kf.wallet.ksecretd: D-Bus activated with PAM kwallet configured, deferring to PAM instance... Jan 17 12:26:22 kf.wallet.ksecretd: No PAM instance detected after wait, proceeding with D-Bus activation Jan 17 12:26:22 QThreadStorage: entry 8 destroyed before end of thread 0x55a460611320 Jan 17 12:26:22 QThreadStorage: entry 7 destroyed before end of thread 0x55a460611320 Jan 17 12:26:22 QThreadStorage: entry 1 destroyed before end of thread 0x55a460611320 Jan 17 12:26:22 QThreadStorage: entry 0 destroyed before end of thread 0x55a460611320 ksecretd from D-Bus activation still has a head start, and since both are waiting for the same amount of time, it still wins. -- You are receiving this mail because: You are watching all bug changes.
