keepassxreboot / keepassxc

KeePassXC is a cross-platform community-driven port of the Windows application “Keepass Password Safe”.
https://keepassxc.org/
Other
21.39k stars 1.48k forks source link

Database auto-locks, even though it's disabled in preferences #11378

Closed dgnuff closed 1 month ago

dgnuff commented 1 month ago

Overview

In security settings, all three of "Lock database after inactivity ...", "Lock database when session is locked or lid is closed" and "Lock database after minimizing window" are unchecked.

Despite this, the database appears to auto-lock after a timeout of ten to fifteen minutes.

Steps to Reproduce

  1. Enter preferences, select "Security" and uncheck the three items listed in the overview
  2. Minimize KeepassXC and continue to use the computer for an hour or so.

Expected Behavior

The database should not be locked after an hour

Actual Behavior

The database is locked

Context

This is specific to one single system. I am running KeepassXC on two systems here, and have checked to make sure the settings on the preferences screens are identical between the two. Only one exhibits this behavior.

KeePassXC - Version 2.7.8 Revision: f6757d3

Qt 5.15.11 Debugging mode is disabled.

Operating system: Windows 11 Version 2009 CPU architecture: x86_64 Kernel: winnt 10.0.22631

Enabled extensions:

Cryptographic libraries:

Operating System: Windows Desktop Env: Explorer Windowing System:

Suggestion:

Is there some way I can turn on debug logging to get KeepassXC to tell me exactly why it is auto-locking the database. That would probably be a major help in resolving this issue.

droidmonkey commented 1 month ago

Are both systems Windows?

dgnuff commented 1 month ago

Yes. Both Windows 11, same build (23H2).

There's something weird going on here. I did another run through the settings and changed something else totally unrelated to database lock, to make it completely match the other system, and so far it's stayed open.

I'll keep an eye on this, but I may be able to close this as "no idea what the problem was, but it's gone away."

droidmonkey commented 1 month ago

Could be your config file didn't save properly for some reason