Closed siddhpant closed 6 days ago
This is normal behavior if you set KeePassXC as the secret service provider and you have not designated a default collection. You need to either disable KeePassXC as a provider or you need to establish a default collection in an existing database.
For reference the dbus call that does this is:
<method name="CreateCollection">
<arg type="o" direction="out"/>
<arg name="properties" type="a{sv}" direction="in"/>
<annotation name="org.qtproject.QtDBus.QtTypeName.In0" value="QVariantMap"/>
<arg name="alias" type="s" direction="in"/>
<arg name="prompt" type="o" direction="out"/>
</method>
How do I establish a default collection?
Application settings -> FDO Secrets tab
I see no such setting. Is it added in a newer version?
I just see "Exposed database groups", which lists the databases with None
besides all except the keyring db (as expected).
This is due to issue mentioned in #8479 and #8611.
Yes those would be the more relevant issue threads. I forgot you are using multiple databases.
Overview
When a program tries to modify (or maybe even access? I don't remember all the times it happened) an entry, keepassxc prompts to create a new database.
It does not happen always, so I don't know the reproduction steps.
It seems to happen when keepassxc is minimised to tray and I have the other tab opened (multiple dbs are opened). I fix this by opening and switching to the tab. (or maybe the tab is a red-herring)
Context
KeePassXC - Version 2.7.7 Revision: 68e2dd8
Operating System: Debian testing Desktop Env: Gnome Windowing System: Wayland