SUMMARY Unable to use keyboard to type operating KTouch under Fedora 33 Gnome (Wayland). STEPS TO REPRODUCE 1. Open KTouch. 2. Use mouse to Start training. 3. Typing has no effect on on application. Mouse is still able to be used. OBSERVED RESULT Although I can continue to use the mouse, and navigate around the application, I am unable to type. EXPECTED RESULT I am able to type and continue my lessons. SOFTWARE/OS VERSIONS Operating on Fedora 33 Silverblue using Gnome (Wayland) DE. Details from `flatpak info`: ID: org.kde.ktouch Ref: app/org.kde.ktouch/x86_64/stable Arch: x86_64 Branch: stablemy Version: 20.12.1 License: GPL-2.0+ Origin: flathub Collection: org.flathub.Stable Installation: system Installed: 8.7 MB Runtime: org.kde.Platform/x86_64/5.15 Sdk: org.kde.Sdk/x86_64/5.15 ADDITIONAL INFORMATION Note that I switch to Fedora Silverblue from Fedora KDE and retained the ~/.var/app/org.kde.ktouch/* files. The following is from the command line. Once application has started I navigate to the next lesson and begin typing ... but nothing happens. $ flatpak run org.kde.ktouch QSocketNotifier: Can only be used with threads started with QThread qCoreApp Application(0x7fff19d21580) kf.i18n: "0 instead of 1 arguments to message {Do you really want t...} supplied before conversion." qrc:/ktouch/qml/trainingscreen/TrainingScreenToolbar.qml:53:5: QML Connections: Implicitly defined onFoo properties in Connections are deprecated. Use this syntax instead: function onFoo(<arguments>) { ... } qrc:/ktouch/qml/homescreen/HomeScreen.qml:33:5: QML Connections: Implicitly defined onFoo properties in Connections are deprecated. Use this syntax instead: function onFoo(<arguments>) { ... } qt.qpa.wayland: Wayland does not support QWindow::requestActivate() qt.qpa.wayland: Wayland does not support QWindow::requestActivate()
Typing in this typing application doesn't work on Wayland, see https://bugs.kde.org/show_bug.cgi?id=422088
*** Bug 447618 has been marked as a duplicate of this bug. ***
*** This bug has been marked as a duplicate of bug 422088 ***