https://bugs.kde.org/show_bug.cgi?id=504312
--- Comment #6 from michaelk83 <mk.mat...@gmail.com> --- (In reply to Marco Martin from comment #3) > One ting i noted while using keepassXC is that every entry in the wallet is > separatedly locked, but what should happen in that case is keepassxc popping > up with some gui to unlock when networkmanager tries to access the network That's a good point, but one of the problems with that is that not all the relevant API methods support the Prompt interface. However, KeepPassXC may still try to show an unlock prompt to avoid some other problems. In that case, the call can still time out. See https://gitlab.freedesktop.org/xdg/xdg-specs/-/issues/101 and https://github.com/keepassxreboot/keepassxc/issues/4443 To avoid that, clients should never use `Collection.SearchItems()` with KeePassXC (`Service.SearchItems()` at least has a `locked` output array), and, if possible, should issue an explicit `Unlock()` call before trying any other operations. -- You are receiving this mail because: You are watching all bug changes.
