chandi Langecker
32d115d22e
Fix unexpected behavior of --lock when keepassxc is not running ( #8889 )
...
currently, when keepassxc is not running, the command `keepassxc --lock` opens a new keepass window and blocks until the window is closed.
Especially in locking scripts this is rather unexpected and Ican't think of a case where someone explicitly starts keepass with --lock and wants this behaviour.
Rather --lock should always ensure, that there are no unlocked instances and exiting afterwards
2023-02-18 14:04:28 -08:00
..
2021-09-28 15:50:27 +02:00
2022-03-21 00:26:07 +01:00
2022-10-29 15:07:50 -04:00
2022-10-23 17:56:57 +02:00
2022-10-29 15:07:50 -04:00
2022-10-29 15:07:50 -04:00
2022-10-29 15:07:50 -04:00
2022-10-29 15:07:50 -04:00
2022-10-29 15:07:50 -04:00
2022-10-29 15:07:50 -04:00
2023-02-18 14:04:28 -08:00
2022-10-29 15:07:50 -04:00
2022-10-22 17:37:47 -04:00
2022-10-29 15:07:50 -04:00
2022-10-29 15:07:50 -04:00
2022-10-29 15:07:50 -04:00
2022-10-29 15:07:50 -04:00
2022-10-23 17:56:57 +02:00
2022-10-29 15:07:50 -04:00
2022-10-29 15:07:50 -04:00
2022-10-29 15:07:50 -04:00
2022-10-29 15:07:50 -04:00
2022-10-29 15:07:50 -04:00
2022-10-29 15:07:50 -04:00
2022-10-29 15:07:50 -04:00
2022-10-29 15:07:50 -04:00
2022-10-29 15:07:50 -04:00
2022-10-29 15:07:50 -04:00
2022-10-29 15:07:50 -04:00
2022-10-29 15:07:50 -04:00
2022-10-29 15:07:50 -04:00
2022-10-29 15:07:50 -04:00
2022-10-29 15:07:50 -04:00
2022-10-29 15:07:50 -04:00
2022-10-23 17:56:57 +02:00
2022-10-29 15:07:50 -04:00
2022-10-29 15:07:50 -04:00
2022-10-29 15:07:50 -04:00
2022-10-29 15:07:50 -04:00
2022-10-22 17:37:47 -04:00
2022-10-29 15:07:50 -04:00
2022-10-22 17:37:47 -04:00