Closed abraxxa closed 3 years ago
Looks like a Qt bug
Also happens when I only have a local Keepass database open. Can you please link the Qt bug you're referring to?
See #6588
And this is it? It's a bug from the framework you use and you don't care? What's required to fix my issue? A newer Qt shipped by Ubuntu which you build against and which you can't influence or is keepassxc compiled against whatever version you want and bundled?
You want us to fix another vendor's software?
You have several options that might work:
This wasn't clear from your answer so I asked. I'll try the appimage tomorrow and report back if the issue is gone.
I've tested the AppImage now but it's compiled without wayland support:
$ ./KeePassXC-2.6.6-x86_64.AppImage
qt.qpa.plugin: Could not find the Qt platform plugin "wayland" in ""
This application failed to start because no Qt platform plugin could be initialized. Reinstalling the application may fix this problem.
Available platform plugins are: xcb.
Aborted (core dumped)
Overview
KeepassXC uses 100% cpu on one core after locking my Ubuntu 21.04 with sway (wayland) when I have a database open from a gvfs mounted directory (/run/user/1000/gvfs/$sharename).
Steps to Reproduce
Expected Behavior
CPU usage stays the same
Actual Behavior
CPU goes to 100% on one core after some time After unlocking Sway KeepassXC doesn't react any more to user input and needs to be killed with a SIGKILL.
Context
sudo strace -p $pid_of_keepassxc showed that it tries to open truetype fonts all the time:
KeePassXC - Version 2.6.6 Revision: 9c108b9
Qt 5.15.2 Debugging mode is disabled.
Operating system: Ubuntu 21.04 CPU architecture: x86_64 Kernel: linux 5.11.0-22-generic
Enabled extensions:
Cryptographic libraries:
Operating System: Linux Desktop Env: Sway Windowing System: Wayland