Dear Maintainer, dear Julian,

Just "important" as I expect it would already be reported a ton of times
in case it would affect everyone with Debian testing/unstable.

Since a while at first occassionally, now always when I open even a freshly
started KeepassXC with my standard password database, then I am greeted
with an empty window. The list of groups is empty. The list of entries in
a group is empty and entry details is also empty.

I started KeepassXC from console and there was no error output.

There is also no error message in the GUI. I just enter the pass phrase
and then I have this empty window. It remains that way after locking
the database manually and opening it again. Or after terminating the
process and starting KeepassXC again.

At the same time KeepassXC is still working in Firefox with the browser
addon installed through "addons.mozilla.org". So Firefox can auto
complete information from the KeepassXC database. It appears that this
is mostly kind of a visual problem in the GUI and no issue with the
password file.

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.

The styling of the application is minimally different as the Flatpak does
not seem to use the desktop color theme I set for my Plasma session.
Which is basically the regular Breeze. Colors seem to be a bit different
in the Flatpak.

The session is still running on X11 here with 150% fractional scaling.
But this has not been a problem for KeepassXC as packaged before and
it is no problem for the KeepassXC flatpak which respects the scaling.

My best guess at the moment would be that some dependency of KeepassXC
in Debian changed in a way that triggers this issue.

Unfortunately I do not remember exactly any more when exactly this issue
started to happen and whether it could be related to the upgrade to
version 2.7.10 of KeepassXC at 9th of April. I could try downgrading
KeepassXC to 2.7.9, however the Flatpak 2.7.10 is also working just fine.
And I believe it has not more than about 2 weeks that the issue first
happened.

I am reporting this in the hope someone else may have some insight.
At the moment I do not really have a clue on how to track this bug
down to its cause.

I am using my own self-compiled kernel since a while, but this issue
started as I was using the stock Debian kernel still. I will still
boot into the latest Debian kernel to make sure the issue is not related.
In the unlikely case it would disappear with the Debian kernel, I will
let you know.

This is on Devuan, but as KeepassXC does not seem to depend on any forked
packages, I don't think Devuan changes have any influence on this.

Devuan excalibur/ceres is based on Debian testing/trixie/unstable.

Best,
Martin

Martin - 11.05.25, 10:09:52 CEST:

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,