KeepassXC UI Too Big in Fedora-Based Vault AppVM (2560x1440 1x Scaling)

User Support General
,
1

Hello everyone.

I am new to Qubes. I have a 4k monitor and have set the resolution of dom0 to 2560x1440 (16:9) with 1x scaling in order to get dom0 and VMs at a comfortable viewing size for me. Browsers all look perfect in their respective VMs but when I try to fire up KeepassXC in the default vault VM (running fedora-40-xfce template) it is all far too big. The menus and other UI elements like buttons seem too big.

If I create a new qube with no networking based on debian-12-xfce then it all looks much better. UI elements sized as expected and much more usable.

Is there any reason that Fedora was chosen as the default vault template and would it be a mistake using the Debian template for a vault qube to run KeepassXC?

And is this a known problem with/without a solution for Fedora?

Many thanks.

1 Like
2

What do you means too big?
I have 2560x1440 screen and I don’t think it’s too big

Screenshot_2025-02-14_22-24-05
Screenshot_2025-02-14_22-24-05829Ă—484 73.7 KB

1 Like
3

It might be possible to adjust scaling on a per-VM basis using xrandr in the VM.

1 Like
4

Here is the Fedora template where the GUI elements appear too big -

fedora
fedora800Ă—624 34.9 KB

1 Like
5

And on Debian -

debian
debian806Ă—625 35.6 KB

6

Debian looks much better -

debian
debian806Ă—625 35.6 KB

1 Like
7

Thanks - yes I had been playing with DPI scaling for ages before experimenting with different templates. I couldn’t get DPI scaling to work at all in the qube. I was reading a lot of different advice previously posted online with a lot of different methods.

1 Like
8

Ah, ok, i didn’t had direct comparison.
It’s different UI in both cases.
It might be Gnome/Xfce thing.

1 Like
9

I’ve been playing around again with this but still can’t find a cause or solution. Both Fedora and Debian templates are the default xfce. I could use Debian for my vault but it means lagging behind with the KeepassXC version.

If I run 2.7.9 via AppImage on Debian the GUI still looks good, so it’s not that they’ve broken the newer versions on xfce unless its the build. But having said that firefox on the fault looks good.

Any other suggestions welcome.

1 Like
10

Turns out this is caused by qt5ct on the Fedora template which is missing on the Debian template.

Added unset QT_QPA_PLATFORMTHEME to ~/.profile on Fedora vault AppVM and KeepassXC looks fine now.

2 Likes
11

If using a .desktop file in ~/.config/autostart, change the Exec line to:

Exec=env QT_QPA_PLATFORMTHEME= keepassxc

As the ~/.profile may be run after the app was already auto started.

1 Like
12

After implementing this fix, I get the following error message while trying to start KeePassXC through the desktop file:
Failed to add a plugin to the panel -- GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name is not activatable

It works when starting KeePassXC from the command line using QT_QPA_PLATFORMTHEME= keepassxc.

Does anyone else have this problem?

1 Like
13

Welp, the answer is “don’t try to be smarter than the people helping you”.

I also changed the TryExec= line directly below the Exec one and that caused the issue.
Now the desktop file is working as expected. :slight_smile:

1 Like
14

Hi, sorry if I’m unearthing an old thread.
I am using Qubes4.3 and a vault AppVM with template fedora-42-xfce.

I have an autostart configuration set up for KeePassXC in this qube, so I followed the fix given by equbes here for .desktop file in ~/.config/autostart:

It works perfectly when keepassxc autostarts on qube boot.
Yet, if I close the app and open it from the application list in qubes app menu, it still appears wrong. I also added unset QT_QPA_PLATFORMTHEME to my ~/.profile file in the AppVM but it did not change anything, including after running source .profile and rebooting the qube.

In another vault AppVM with no autostart configuration (i.e. no .desktop file), the fix unset QT_QPA_PLATFORMTHEME does not change anything either.

Any chance someone is having the same issue or has any idea of another fix, or why the fix proposed by Glimmer868 does not work ?

1 Like