keepassxc
patreon
KeePassXC 2.4.1 Released
🕑 Added 2019-04-17 02:33:38 +0000 UTCAfter the dust settled with the 2.4.0 release, we were hard at work fixing all the issues that were identified by our wide and varied customer base. We released 2.4.1 last week and are very proud of where the 2.4.x series has come. This is by far the most feature complete and best performing cross-platform password manager in the world. This is due in large part to your donations and support!
2.4.0 Release Blog Post - https://keepassxc.org/blog/2019-03-19-2.4.0-released/
2.4.1 Release Blog Post - https://keepassxc.org/blog/2019-04-13-2.4.1-released/
Comments
The KeePassXC Team
Not at all! We have been very busy with post release cleanup that I forgot to update you guys. I'll write a post mortem later this week for Patrons.
Sergiu Coroi
2.5 has been released quite awhile ago, Is Patreon an obsolete community for KeepassXC?
Lionel Laské
I've upgraded to 2.3.4 on macOS, thanks for the advice. I will retry on Unbuntu to be sure I've got the same issue. I can't adjust more the locking frequency: it locks the database only when I lock my session to take a break (and I must take a break sometimes :-) And I'm not at all in favor of leaving the database unlocked forever during the session.
The KeePassXC Team
I believe 3109 only affects macOS. Would you be able to adjust the locking frequency to lessen the impact of the bug? 2.4.1 is definitely superior to 2.3.2 (you really should be using 2.3.4 if possible).
Lionel Laské
Hi guys. Thanks for your work but unfortunately I had to revert back to 2.3.2 today. I'm stick with the issue regarding locked database (<a href="https://github.com/keepassxreboot/keepassxc/issues/3109)." rel="nofollow noopener" target="_blank">https://github.com/keepassxreboot/keepassxc/issues/3109).</a> My database is very often locked (at each screen lock on my Mac and every 4 min on my Linux) so because of this issue I need to manually copy login/password from KeePassXC most of the time. Worse: I don't find any way (expect by restarting Firefox) to reconnect correctly to the database once unlocked. Hope you could find a fix.
