Description of problem: Several QT applications frequently ignore keyboard input. On picard, this is easily reproduced following the steps below. For texmaker, the conditions appear more random. Version-Release number of selected component (if applicable): qt5-qtwayland-5.13.2-2.fc31.x86_64 picard-2.3.0-1.fc31.x86_64 texmaker-5.0.4-2.fc31.x86_64 gnome-shell-3.34.4-1.fc31.x86_64 How reproducible: Steps to Reproduce: 1. Start picard, add an audio file to edit tags for, 2. Right-click in the tag area, select "add new tag", 3. In the "edit tag" dialogue that appears, select a tag type, 4. Double-click in the entry list, try to type. Actual results: No characters appear in the dialogue box Expected results: Characters appear in the dialogue box Additional info: To make Picard accept keyboard input, after step 4 use alt+tab to switch to a different window, then use alt+tab to switch back. Input now works for this tag, but will fail again when adding another tag. The terminal from which picard is started contains several instances of the following warning: qt.qpa.wayland: Wayland does not support QWindow::requestActivate() Finally, a work-around for this issue is to start picard with the QT_QPA_PLATFORM=xcb environment variable.
This message is a reminder that Fedora 31 is nearing its end of life. Fedora will stop maintaining and issuing updates for Fedora 31 on 2020-11-24. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a Fedora 'version' of '31'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 31 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
Fedora 31 changed to end-of-life (EOL) status on 2020-11-24. Fedora 31 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed.
Can still reproduce in Picard on Fedora 33.
I can reproduce with picard, but it might be an issue in picard itself. When I follow the steps you mentioned, even on X11 (xcb) I can see both text fields having focus, like both text fields have blinking cursor. I cannot reproduce this issue with any other app. I even tried keepassxc forcing the wayland plugin, but I cannot reproduce this issue anymore.
Jan, could you please look at this issue in Qutebrowser when you have a minute. It seems related. There, input isn't ignored but ends up the wrong window, which could even be on a different workspace: https://bugzilla.redhat.com/show_bug.cgi?id=2008937 Thanks very much,
Sorry, that was meant to be a request :) "Jan, could you please look at this issue in Qutebrowser when you have a minute? (It seems related)" Cheers,
I can't reproduce the issue with Picard on F35 and Picard 2.7.0.
This message is a reminder that Fedora Linux 34 is nearing its end of life. Fedora will stop maintaining and issuing updates for Fedora Linux 34 on 2022-06-07. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a 'version' of '34'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, change the 'version' to a later Fedora Linux version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora Linux 34 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora Linux, you are encouraged to change the 'version' to a later version prior to this bug being closed.
Fedora Linux 34 entered end-of-life (EOL) status on 2022-06-07. Fedora Linux 34 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. Thank you for reporting this bug and we are sorry it could not be fixed.