Uppon first opening an applications that tries to access the Freedesktop.Secrets service the user is asked to unlock his database with the following screen:

Password are accesible and everything works, but if you close the application, close the database and reopen the application (Remmina in this case) you are not asked to unlock the database again. Even after manually unlocking the database Remmina will not find any of it's stored secrets, you have to kill keepassxc and start from scratch.

The same behaviour can also be observed with secret-tool or python-keyring

Expected Behavior

Ask to unlock the keyring again/resume freedesktop.secrets service after locking/unlocking the database .

Steps to Reproduce

secret-tool store --label='Test' username testuser password testpassword
Password: Testpassword

#Keepassxc asks to unlock the database

libsecret-Message: 16:06:06.692: Remote error from secret service: org.freedesktop.Secret.Error.IsLocked: Error return with empty body:
secret-tool: Error return with empty body:

secret-tool store --label='Test' username testuser password testpassword
Password: Testpassword
# Works

secret-tool lookup username testuser
Testpassword
# Works

#Lock database

secret-tool lookup username testuser

#Not asked to unlock again
#Manually unlock database

 secret-tool lookup username testuser
# No secrets found...

Context

I'm forced to leave my database constanly unlocked, can't even lock it when I close the session, gnome-keyring had no problem with locking the keyring and asking to reopen it.

Debug Info

KeePassXC - Version 2.5.1
Revision: 0fd8836

Qt 5.13.2
Debugging mode is disabled.

Operating system: Arch Linux
CPU architecture: x86_64
Kernel: linux 5.4.2-arch1-1

Enabled extensions:

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

Cryptographic libraries:
libgcrypt 1.8.5