Description of problem: Unable to type text in search and other text-inputs fields on keepassxc from fresh boot, unless kepassxc is launched from the terminal with argument "-platform wayland" or keepassxc is restarted once. The problem is allready discussed there: https://github.com/keepassxreboot/keepassxc/issues/5608 Version-Release number of selected component (if applicable): KeepassXC V 2.6.4 (Problem present since about V 2.6.1) How reproducible: After each fresh boot. Steps to Reproduce: 1. install qt5-qtwayland and keepassxc; 2. launch and open/unlock a password database; 3. try to type text in search field. Actual results: No text appears in text-input-field. Expected results: Typed text appears in text-input-field. With each typed letter, filters the corresponding passwords entries below text-input-field. Additional info: Tried to uninstall qgnomeplatform (alone) ==> Doesn't solve the problem. Tried to uninstall qt5-qtwayland ==> Solves the problem.
This usually indicates an application issue/bug, triaging there. If problems persist, the application can be patched to use xcb mode even on wayland
This is an upstream problem, by the way could you please provide following infos - desktop environment you are using AND if it is a Wayland or GNOME session - KeepassXC Help menu->info->debug info
- DE: GNOME 3.38.3; - Session: how do I find that out? is it the Window Manager? (WM: Mutter); - KeePassXC debug info: KeePassXC - Version 2.6.4 Revision: 34a78f0 Qt 5.15.2 Debugging mode is disabled. Operating system: Fedora 33 (Workstation Edition) CPU architecture: x86_64 Kernel: linux 5.10.11-200.fc33.x86_64 Enabled extensions: - Auto-Type - Browser Integration - SSH Agent - KeeShare (signed and unsigned sharing) - YubiKey - Secret Service Integration Cryptographic libraries: - libgcrypt 1.8.7
(In reply to Germano Massullo from comment #2) > This is an upstream problem, by the way could you please provide following > infos > - desktop environment you are using AND if it is a Wayland or GNOME session I apologize, I made a mistake, I meant if you are using a Wayland or XOrg session. You can find out by running command echo $XDG_SESSION_TYPE
Don't apologize, I presume most of Bugfilers understand all of this better than I do. Thanks for the command! Session is wayland.
I am in contact with upstream developers, they are still figuring out if it is really a KeepassXC problem or not
removing qt5-qtwayland package solves the problem: it migtht be something there.
The problem doesn't appear in Fedora Workstation 34 beta.
This was my workaround for it: https://github.com/keepassxreboot/keepassxc/issues/4105#issuecomment-806940860 Basically, the desktop file needs this to support wayland: Exec=QT_QPA_PLATFORM=xcb keepassxc %f TryExec=QT_QPA_PLATFORM=xcb keepassxc
This comment clarified why we are experiencing these problems. I will release a fix soon https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org/message/3BVLBS4B3XHJEXFVGD7RK2ZMXZG6JQZT/
FEDORA-2021-a70c4b64b2 has been submitted as an update to Fedora 33. https://bodhi.fedoraproject.org/updates/FEDORA-2021-a70c4b64b2
FEDORA-2021-a70c4b64b2 has been pushed to the Fedora 33 testing repository. Soon you'll be able to install the update with the following command: `sudo dnf upgrade --enablerepo=updates-testing --advisory=FEDORA-2021-a70c4b64b2` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2021-a70c4b64b2 See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
Just tested the update: solves the bug for me. (https://bodhi.fedoraproject.org/updates/FEDORA-2021-a70c4b64b2) Thanks a lot for your work!
Good to ear!
FEDORA-2021-a70c4b64b2 has been pushed to the Fedora 33 stable repository. If problem still persists, please make note of it in this bug report.
Hi, can you check whether you can reproduce this issue on current Fedora 34? You can re-force wayland plugin by running "keepassxc -platform wayland". I wanted to investigate this issue, but I cannot reproduce it.
Hello Jan, Already did (https://bugzilla.redhat.com/show_bug.cgi?id=1925130#c8): the bug does not appear under Fedora Workstation 34. At least for me. Best regards nh