KeepassXC extension asks to connect to database as soon a second database is open (but not unlocked)

[cquike]

Have you searched for an existing issue?

• Yes, I tried searching and reviewed the pinned issues

Brief Summary

I have the following scenario:

• Database 1 which has been already connect to the browser extension.
• Database 2 which has not been connected to any browser extension.

If I have Database 1 open, then the extension works fine. As soon as I open Database 2, even before I try to unlock it, the browser extension icon grays out and says that it cannot connect to KeepassXC. The interesting thing is that if I click the tab in KeePassXC application with the Database 1 then the extension icon becomes green again and is usable. If I click on the Database 2 tab I am back to a dysfunctional browser extension. If I further unlock Database 2 then the extension remains disconnected even if I switch the tabs in the KeePassXC application.

All this seems to me like an unfortunate user interface, because Database 1 has remained open and unlocked all the time. Would it be possible to retain that connection with the extension still alive? It is fine if the extension offers to connect to Database 2 in addition, but without loosing the connection to Database 1.

Expected Versus Actual Behavior

The extension remains functional, still connected to Database 1.

Steps to Reproduce

1. Open and unlock Database 1
2. Browser extension is connected
3. Open Database 2
4. Browser extension is now disconnected even if Database 1 has not been closed or locked.

KeePassXC-Browser Debug Information

KeePassXC - 2.7.11
KeePassXC-Browser - 1.10.1
Operating system: Linux x86_64
Browser: Mozilla Firefox 147.0

[varjolintu]

Do you have the option "Search in all opened databases for matching credentials" enabled in KeePassXC? If not, is there any different with it?

[cquike]

Thanks for the suggestion.
The option was disabled. I enabled it and the behaviour is the same.

[cquike]

From a very quick cursory look at the code I found this function in src/browser/BrowserService.cp

void BrowserService::activeDatabaseChanged(DatabaseWidget* dbWidget)
{
    if (dbWidget) {
        if (dbWidget->isLocked()) {
            databaseLocked(dbWidget);
        } else {
            databaseUnlocked(dbWidget);
        }
    }

    m_currentDatabaseWidget = dbWidget;
}

I wonder whether this connection in the UI makes sense for the browser extension. Should the browser extension care about which database tab is active in UI?
Since this was a very quick look I might have misinterpreted the code, so apologies if this is completely misguided.

[varjolintu]

@cquike For now it does care. The old original code is not very flexible, which is why I have been making a new version of it where it doesn't matter which database tab is active in KeePassXC.

[varjolintu]

And quickly testing this I cannot reproduce the issue. Can you provide logs from the background scripts?

[cquike]

Which background scripts you mean? I don't really know how to get those logs you refer to...

[varjolintu]

https://github.com/keepassxreboot/keepassxc-browser/wiki/HowTo:-Special-situations-and-debugging#firefox-debug-background-scripts

[cquike]

This are the messages that appear in the debug console when I switch the tab in the KeePassXC application:

[Error keepass.js:256] KeePassXC-Browser - 1: Base de datos no abierta [global.js:168:13](moz-extension://32a250f0-cdd6-4fc7-af6d-0e9a9721176d/common/global.js)
[Error keepass.js:926] KeePassXC-Browser - No content script available for this tab. [global.js:168:13](moz-extension://32a250f0-cdd6-4fc7-af6d-0e9a9721176d/common/global.js)

Unfortunately it appears in Spanish, but basically "Base de datos no abierta" means "Database not open".

I see also a message appearing a bit after:

[Error event.js:12] KeePassXC-Browser - page.initSettings error: Error: Managed storage manifest not found [global.js:168:13](moz-extension://32a250f0-cdd6-4fc7-af6d-0e9a9721176d/common/global.js)

I hope this is useful information,

[varjolintu]

Those are normal messages. How is your KeePassXC installed? Via normal repository, PPA, Flatpak..?

[cquike]

KeePassXC is installed from the Debian 13 repositories:

ii  keepassxc-full                                           2.7.10+dfsg1-1                           
ii  webext-keepassxc-browser                    1.9.7+repack1-1+deb13u1

[varjolintu]

Check if the same happens with the latest KeePassXC 2.7.12.

[cquike]

I have installed KeePassXC from the git develop branch and the same behaviour appears.

[cquike]

Note that if both databases are unlocked and connected to the browser extension then the problem does not appear.
Did you try with a second database which is locked and has never been connected to the browser extension?