Created attachment 1983511 [details] Example of issue happening Description of problem: When I exit overview or switch workspaces, the character ± will be continuously typed if the new workspace is focused on an electron application. Version-Release number of selected component (if applicable): GNOME 44.3 How reproducible: Occationally starts happening when I switch to an electron application, once it happens, it keeps happening until I logout or restart Steps to Reproduce: 1. Switch to an electron application with 3 finger swipe or super+mouse scroll 2. Occationally, the character ± will start to be typed on the text field continuously 3. Once this happens once, it keeps happening every time Actual results: The character ± will be continuously typed if the new workspace is focused on an electron application. Expected results: I switch to the new workspace or exit overview, without anything more happening Additional info:
This component is maintained by the GNOME project. Issues with it should be reported directly to GNOME at https://gitlab.gnome.org/GNOME/. This issue should only be kept open if it: 1. Relates to Fedora packaging or integration with other Fedora components 2. Is required for Fedora release processes, such as blocker bugs and freeze exceptions If this issue isn't needed for either of these two reasons, please: * create an issue with GNOME * add a link to the GNOME issue here * close this issue as CLOSED/UPSTREAM Thank you!
Fedora Linux 38 entered end-of-life (EOL) status on 2024-05-21. Fedora Linux 38 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 Linux please feel free to reopen this bug against that version. Note that the version field may be hidden. Click the "Show advanced fields" button if you do not see the version field. If you are unable to reopen this bug, please file a new report against an active release. Thank you for reporting this bug and we are sorry it could not be fixed.