https://bugs.kde.org/show_bug.cgi?id=504312
--- Comment #24 from michaelk83 <[email protected]> --- Created attachment 189003 --> https://bugs.kde.org/attachment.cgi?id=189003&action=edit Analysis of the DBus log from comment 23 (In reply to Jan Torben Heuer from comment #22) > Same timeout observed and nothing stored in keepassxc. But I noticed a popup > asking for the creation of a new keepass file Based on your log, it looks like Network Manager specifically asks for "kdewallet", but your Secret Service database was `.../secrets/collection/Passwords` with label "Passwords". That's why you saw the create DB dialog. Later in the log you ended up creating a "Passwords_2a11" DB, with label "kdewallet". It also looks like you don't have a DBus autostart file for org.freedesktop.secrets. See my comment 19. Without this, DBus doesn't know how to start org.freedesktop.secrets (KeePassXC) on demand. This shouldn't be an issue if KeePassXC is already running anyway (which seems to be the case here), but worth noting. The detailed analysis is attached. @Marco Martin: From what I can see, `KWalletD::openInternal()` doesn't try to resolve "kdewallet" as the default alias. Though I'm not sure what the behavior should be if the default alias points to a collection that has a _different_ label than "kdewallet" (as in this case). If we're treating "kdewallet" as the legacy equivalent of the default alias, then I think the actual label shouldn't matter. It also looks like Network Manager doesn't listen for KWallet's `walletCreated` and `walletListDirty` signals. It's only waiting for `walletAsyncOpened`, which KWallet never sends out for a new wallet. So it just sits there waiting for the wallet to be opened (until it times out, I guess), completely oblivious that a new wallet has been created. -- You are receiving this mail because: You are watching all bug changes.
