Martin - 11.05.25, 10:09:52 CEST: > As I need to access the database manually at times, I installed > KeepassXC as a flatpak as "org.keepassxc.KeePassXC" in the same version > 2.7.10. When I quit the Debian packaged KeePassXC and start the Flatpak > one KeepassXC displays all groups and entries just fine. But then the > browser addon has no connection. I may look into trying to set up that > connection but I am not sure it will work with a Debian packaged > Firefox. If so I could work-around this issue completely by just > switching KeepassXC to the flatpak.
I got the browser connection to work and switched to the Flatpak of 2.7.10 of KeepassXC. That did work for a while. However now the Flatpak also showed that odd behavior. And I found a work-around or possibly fix: In the menu in Display / Design switch between automatic and light display. This worked for the Flatpak. Then I could switch to classic / platform native display and it still worked okay. Even across a fresh start of the application. My packaged KeepassXC had classic/platform native as design. I switched to automatic and it did not help. I switched from automatic to light and it helped. Then I was able to switch to classic / platform native again and I still saw all entries. So I am using the Debian packaged KeepassXC again. I will see how it goes from there. But it seems at least that there is a way to have it display entries again by playing around with display design setting. Writing here as it may help someone else how comes across the bug. I do not see the issue with a KeepassXC on a different laptop with a different KeepassXC password file. Not sure how to see what exactly triggers the issue. Let's see whether it happens again. And I may review the display design setting on that other laptop. Sorry, for not being more specific, but right now I still do not have a clue what triggers the issue. Of course this means this bug report is not really actionable at the moment from a packaging point of view. In case I would be the only one experiencing the issue, I'd be fine with closing the issue after a while. But maybe keep it open for some months to see whether someone else faces it. Cause not being able to see any password entries is quite an irritating issue. Best, -- Martin
