Secret Service integration broken

[moridius]

Overview

I cannot get passwords via the Secret Service integration anymore.

Steps to Reproduce

1. Unlock the database.
2. Use secret-tool to request a password.

Expected Behavior

Getting the password.

Actual Behavior

KeePassXC popup asks me to unlock the database (although it's already unlocked). If I give the correct master password the popup vanishes and nothing happens. After some time secret-tool reports a timeout.

Context

This worked fine before the update (probably with version 2.7.6 although I don't know).

KeePassXC - Version 2.7.7
Revision: 68e2dd8

Qt 5.15.11
Debugging mode is disabled.

Operating system: Void Linux
CPU architecture: x86_64
Kernel: linux 6.6.21_1

Enabled extensions:

• Auto-Type
• Browser Integration
• SSH Agent
• KeeShare
• YubiKey
• Secret Service Integration

Cryptographic libraries:

• Botan 2.19.3

Operating System: Void Linux
Desktop Env: i3 window manager
Windowing System: X11

[droidmonkey]

I think you might have two keepassxc's running at the same time? We only fixed a small crash bug with Secret Service integration that doesn't impact credential retrieval. Do a reboot and try again.

[tomfun]

I have the same problem on
Linux Mint XFCE
Linux sqdl-l 5.15.0-100-generic #110-Ubuntu SMP Wed Feb 7 13:27:48 UTC 2024 x86_64 x86_64 x86_64 GNU/Linux

you might have two keepassxc's running at the same time?

No.

some times it shows error:

[Taijian]

I have the same issue - it took me a while to figure this one out, but here's what's happening.

Secret Service support is configurable via the 'Database settings' menu dialogue.
For some reason, after the update to 2.7.7, this setting keeps reverting to 'Do not unlock this database' after some time elapses. I then have to go back to this setting, re-select the Group(s) I want to expose to the Secret Service Agent, confirm and then it works again... for a while.
Then it breaks again and I have to re-enable it again, etc...

[Taijian]

Investigating further, it seems that the permission revert happens whenever a changed shared database - via the KeyShare functionality - is merged back into the 'main' database, then the Secret Service permission setting gets reverted. So possibly related to #9371

[droidmonkey]

Yes this is a duplicate of that issue. No changes to FdoSecrets was made in 2.7.7 that would relate to this behavior.