Community Packages

Please read this before reporting a bug:

Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.

REPEAT: Do NOT report bugs for outdated packages!

FS#71820 - Giant icons in keepassxc

Attached to Project: Community Packages
Opened by Tim Jones (tsj) - Thursday, 12 August 2021, 19:22 GMT
Last edited by Andreas Radke (AndyRTR) - Tuesday, 31 August 2021, 19:03 GMT
Task Type Bug Report
Category Packages
Status Assigned
Assigned To Balló György (City-busz)
Bruno Pagani (ArchangeGabriel)
Architecture All
Severity Low
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 0%
Votes 2
Private No


Icons are rendered too large in keepassxc.

See screenshot in upstream bug report here:

Upstream believes it to be a Qt bug for certain distributions. Upstream bug report is closed.

Affecting version 2.6.6

Steps to reproduce:
1. Create and open database
2. Add entries
3. Observe large icons for entries

A workaround is to launch with `QT_SCALE_FACTOR=1.01`
This task depends upon

Comment by Tim Jones (tsj) - Wednesday, 18 August 2021, 17:26 GMT
A solution that worked for me was posted in the upstream bug report. Remove all deepin packages. I had deepin-screen-recorder and a number of others, probably just dependencies.

Unclear on if this is a bug in keepassxc, deepin software, Qt, or Arch's build/config surrounding any of those.
Comment by Bruno Pagani (ArchangeGabriel) - Saturday, 07 May 2022, 15:32 GMT
Does this issue still happen?
Comment by Tim Jones (tsj) - Sunday, 08 May 2022, 01:09 GMT
Yes, whenever some deepin package is installed, I don't know which one(s) exactly.

I just tested with keepassxc 2.7.1-1. With no deepin packages installed, i.e. "pacman -Qs deepin" returns nothing, icons look normal.

If I install community/deepin-screen-recorder 5.10.15-1, this pulls in:

Restart keepassxc, many icons are oversized. Removing all the deepin stuff again, icons go back to normal.
Comment by Christoph D'Hanis (SunBlade_ger) - Thursday, 30 June 2022, 19:15 GMT
Still happening with up-to-date packages.
For me the offending package was 'deepin-qt5integration'.