Expected Behavior

After enabling the Secret Service integration for a database, KeepassXC exposes it via libsecret.

Current Behavior

When starting keepassxc from the command line, it will print the message "Another secret service provider is running". When enabling the Secret Service Integration for a database, KeepassXC shows the message:

Fdo Secret Service: Failed to register DBus service at org.freedesktop.secrets: another secret service is running

Possible Solution

Maybe this is just a misconception about the feature. Is KeepassXC supposed to act as a Keyring alongside the default Keyring (e.g. Seahorse) or is it supposed to replace it? In the latter case, the behavior described above might be expected and I would have to migrate all my credentials from Seahorse to KeepassXC and get rid of the former.

Steps to Reproduce

Tested with the snap and appimage versions.

Context

I am using Ubuntu (Gnome) with Seahorse installed (which it is by default, iirc).

Debug Info

KeePassXC - Version 2.5.1
Revision: 0fd8836
Distribution: Snap

Qt 5.9.5
Debugging mode is disabled.

Operating system: Ubuntu Core 18
CPU architecture: x86_64
Kernel: linux 5.3.0-22-generic

Enabled extensions:

• Auto-Type
• Browser Integration
• SSH Agent
• KeeShare (signed and unsigned sharing)
• YubiKey
• Secret Service Integration

Cryptographic libraries:
libgcrypt 1.8.1