Description of problem: If you invoke the GNOME virtual keyboard and try to type something, you'll soon discover that most letters don't work, they don't input anything. For example, from the top line "qwertyuiop", only "euio" are typed in, all other characters are ignored. Version-Release number of selected component (if applicable): gnome-shell-42~rc-3.fc36.x86_64 mutter-42~rc-5.fc36.x86_64 How reproducible: always Steps to Reproduce: 1. enable Screen Keyboard in GNOME Settings -> Accessibility 2. open e.g. Text Editor app 3. click inside, a virtual keyboard should pop up at the bottom of the screen 4. try to type letters, most don't do anything Additional info: I'm not sure whether this keyboard is integrated in gnome-shell, or whether this bug should be reported against some other package which provides that functionality.
Proposing as a Final blocker. Possibly these criteria could be related: https://fedoraproject.org/wiki/Fedora_36_Final_Release_Criteria#Default_application_functionality https://fedoraproject.org/wiki/Fedora_36_Final_Release_Criteria#Default_panel_functionality Please note that the accessibility menu is displayed by default on the login screen (referring to the "Default panel functionality" criterion). That means that you can't even log in using this virtual keyboard. (Also, the keyboard on the login screen disappears after each pressed letter, which is doubly annoying, but probably a separate issue).
garnacho says there's a fix for this upstream, linked.
Discussed during the 2022-03-28 blocker review meeting: [0] The decision to classify this bug as an "AcceptedBlocker (Final)" was made as it violates the following criterion: "A system installed with a release-blocking desktop must boot to a log in screen where it is possible to log in to a working desktop", in cases where use of the on-screen keyboard is necessary due to lack of a physical keyboard, or accessibility requirements. [0] https://meetbot.fedoraproject.org/fedora-blocker-review/2022-03-28/f36-blocker-review.2022-03-28-16.00.txt
Looks like that fix was actually merged in 42.0, so the pending megaupdate should fix this.
FEDORA-2022-a69718b1e1 has been submitted as an update to Fedora 36. https://bodhi.fedoraproject.org/updates/FEDORA-2022-a69718b1e1
oh, nope. that megaupdate somehow did not include a gnome-shell build...
FEDORA-2022-8b3e009de7 has been submitted as an update to Fedora 36. https://bodhi.fedoraproject.org/updates/FEDORA-2022-8b3e009de7
OK, fix confirmed here with that update I just created.
FEDORA-2022-8b3e009de7 has been pushed to the Fedora 36 testing repository. Soon you'll be able to install the update with the following command: `sudo dnf upgrade --enablerepo=updates-testing --advisory=FEDORA-2022-8b3e009de7` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2022-8b3e009de7 See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
FEDORA-2022-8b3e009de7 has been pushed to the Fedora 36 stable repository. If problem still persists, please make note of it in this bug report.