Have to Keep Connecting to Database

[ThePapaw]

Have you searched for an existing issue?

• [x] Yes, I tried searching and reviewed the pinned issues

Brief Summary

Using portable version. After updating to latest version (v1.9.11), I am continuously having to re-connect to database in the Chromium based browsers. Tried bot Brave and Helium

Expected Versus Actual Behavior

No response

Steps to Reproduce

Install extension in Helium browser

KeePassXC-Browser Debug Information

KeePassXC - 2.7.11
KeePassXC-Browser - 1.9.11
Operating system: Win64
Browser: Chrome/Chromium 142.0.0.0

[varjolintu]

Please add any log messages from both content and background scripts.

[cube79]

I have the same problem, where can I find the logs?

[varjolintu]

https://github.com/keepassxreboot/keepassxc-browser/wiki/HowTo:-Special-situations-and-debugging

[ThePapaw]

I found my issue, it was a (new maybe?) setting under Security: "Lock database after inactivity"

[cube79]

I'm locking my databases o locksreen, and I would like to keep it that way. @varjolintu attached you will find the log from the console. If you need something, could you be more specific what shall I get out of there?

console-1764583408598.log

[varjolintu]

It's a known issue on KeePassXC side: https://github.com/keepassxreboot/keepassxc/issues/9880

[cube79]

Are you sure this is the same? I cannot Connect the database again in the browser. After Vivialdi restart it comes back

[varjolintu]

Hmm. Maybe it's not the same then. Gotta test this myself.

[cube79]

if you need any more info/logs, don't hesitate to ask. I'll do my best to help :-D

[varjolintu]

@cube79 So you are not using similar settings with the OP?

[Pavarottii]

This problem only occurs for me with the last update to 2.7.11. After reverting to 2.7.10 it's again working fine. I haven't changed any config settings. The only unusual factor is that I run multiple FireFox profiles, all connected to KeePassXC.

This bug renders the product almost unusable for me. I very much hope a fix will be forthcoming.

[varjolintu]

@Pavarottii Anything in the logs?

[Pavarottii]

I was not even aware that KeePassXC logged events. Please tell me where to find this (on Windows 10), assuming that my delete/reinstall to 2.7.10 wouldn't have erased them.

[varjolintu]

I was not even aware that KeePassXC logged events. Please tell me where to find this (on Windows 10), assuming that my delete/reinstall to 2.7.10 wouldn't have erased them.

Just look at the previous messages. https://github.com/keepassxreboot/keepassxc-browser/issues/2785#issuecomment-3595200663

[Pavarottii]

I very much appreciate your post, but I don't see how looking at an arbitrary FireFox tab today could help shed light on a problem from last week, using a since-removed version.

In any case, it seems from ThePapaw that there's been a change in the way the "Lock database after inactivity" setting is interpreted. I can assure you that it never used to trigger, and that it does so repeatedly under 2.7.11.

[droidmonkey]

Go into application settings, security tab, disable auto locking if you dont want it enabled. Simple.

[Pavarottii]

Thank you, droidmonkey. I can confirm that this setting is not checked when I use 7.2.10. I don't have the opportunity right now to update to 7.2.11 again, but there's now growing evidence that updating to 7.2.11 either introduces a problem with this setting, or turns it on uninvited. That should be enough for any developer to work with. IMHO.

[droidmonkey]

It was intentional to make it on by default. It is a common finding in security audits conducted on our software.

[Pavarottii]

So it was done on purpose? I guess that would be ok, as long as it was clearly documented in the release notes. I'm afraid that I didn't see that mentioned.

If I was responsible for any product with a user base the size of KeePassXC, I certainly wouldn't be making changes like this without giving a whole lot more thought to how users would handle the change. Disappointed that you guys don't have a bit more respect for your users' time.

[droidmonkey]

There is absolutely no need to be rude.

[Pavarottii]

You think that was rude? There I was thinking that I was being polite.

Allow me to rephrase. 900 seconds default is Completely Fucking Stupid.

And shows contempt for your users.

Better?

[cube79]

@cube79 So you are not using similar settings with the OP?

What do you mean by OP?

I have check the following checkboxes in the security tab:

• clear clipboard after 10s
• lock databases after 900s
• enable databases quick unlock with windows hello
• lock databases when session is locked.

I'm thinking about unchecking the 900s, usually I'm by the computer and if I go away I lock it by standard.

I'm currently at hospital, so likely i'll be rather not very responsive....

[varjolintu]

@cube79 And does this setting have anything to do with the dialog with the Connect button?

[cube79]

@cube79 And does this setting have anything to do with the dialog with the Connect button? I've been in the hospital. I'm slowly recovering and will let you know when I can work more on the computer.