Created attachment 812355 [details] Log generated from "xinput test-xi2" command output Description of problem: I observed that On-Screen Keyboard (OSK) applications iok, eekboard, cellwriter, florence all stopped working/sending key events to focused application. This looks like problem only in Gnome. I have successfully tested all above OSK applications in KDE, MATE. No issues. Version-Release number of selected component (if applicable): How reproducible: always in gnome DE Steps to Reproduce the bug: 1. start iok and click on any key 2. focused application will not display clicked key in iok UI Test case for attached output: 1. start gnome-terminal 2. run iok 3. open another tab in gnome-terminal 4. run "xinput test-xi2" 5. focus this xinput window 6. try to click on any key in iok 7. close the xinput Actual results: In Gnome any OSK application fails to send keyevents/client fails to display key character Expected results: In Gnome any OSK application should send keyevents/client should display key character Additional info:
Created attachment 812356 [details] KDE Log generated from "xinput test-xi2" command output
Created attachment 812357 [details] MATE Log generated from "xinput test-xi2" command output
Version-Release number of selected component (if applicable): xorg-x11-server-common-1.14.3-4.fc20.x86_64 xorg-x11-server-Xorg-1.14.3-4.fc20.x86_64 xorg-x11-server-devel-1.14.3-4.fc20.x86_64 xorg-x11-server-utils-7.7-2.fc20.x86_64
all those OSK apps worked fine on F19-updates system with xorg-x11-server-Xorg-1.14.3-1.fc19.x86_64
I also tried Fedora 20 Alpha and removed xorg-x11-server-common and xorg-x11-server-Xorg and installed initial 1.14.3-1 builds. But all those OSK applications still not working.
I now used Fedora 19 system and updated directly following rpm xorg-x11-server-common-1.14.3-4.fc20.x86_64 xorg-x11-server-Xorg-1.14.3-4.fc20.x86_64 I found that system is working fine, boot into gnome session and these OSK applications iok, eekboard worked fine.
libXtst is not changed from f19 to f20, its same 1.2.2 version. Not sure then if something in gtk3 package creating this bug. another thing caribou looks working fine which also uses libXtst library.
Works fine under metacity, which makes it unlikely that the X server is at fault.
Probably caused by https://git.gnome.org/browse/gnome-shell/commit/?id=93dc7a51c0e70a6ff5a03c3fd8ebba39d5a13978
I can confirm that upstream developer submitted patch is working fine in Fedora 20 now. Waiting for upstream patch commit and Fedora build.
Discussed this in 2013-10-21 Blocker Review Meeting [1]. Rejected as a freeze exception bug, as it does not seem to affect GNOME's own OSK, and others would have to be installed from repositories anyway so this can be fixed with an update. [1] http://meetbot.fedoraproject.org/fedora-blocker-review/2013-10-21/
please fix this before F20 Final freeze otherwise, onscreen keyboard applications will remain non-functional.
as per c#11, it really doesn't have much relation to freezes; no OSK but GNOME's is installed by default, so any other is always going to come from the repositories. This can be fixed with an update as well as before freeze.
I confirm this bug is not fixed in latest Fedora 20 Final TC4 release. Therefore, I request to add this bug on https://fedoraproject.org/wiki/Common_F20_bugs
Whoever is responsible for pushing new mutter updates, please include fix from https://bugzilla.gnome.org/show_bug.cgi?id=710296 which will fix this bug in F20.
mutter-3.10.2-4.fc20 has been submitted as an update for Fedora 20. https://admin.fedoraproject.org/updates/mutter-3.10.2-4.fc20
Package mutter-3.10.2-4.fc20: * should fix your issue, * was pushed to the Fedora 20 testing repository, * should be available at your local mirror within two days. Update it with: # su -c 'yum update --enablerepo=updates-testing mutter-3.10.2-4.fc20' as soon as you are able to. Please go to the following url: https://admin.fedoraproject.org/updates/FEDORA-2013-23182/mutter-3.10.2-4.fc20 then log in and leave karma (feedback).
mutter-3.10.2-4.fc20 has been pushed to the Fedora 20 stable repository. If problems still persist, please make note of it in this bug report.
It looks like this fix is breaking something else. "... Downgrading to mutter-3.10.2-2.fc20.x86_64 seems to have stopped the crashes." from https://bugzilla.redhat.com/show_bug.cgi?id=995785#c34
Yes. That bug seems more significant than this one, so I'm sending out a 3.10.2-5 update which simply reverts the 3.10.2-4 change (which was to add the patch for this bug). We can do a -6 with both this and #995785 fixed once the patches for #995785 are reviewed.
https://admin.fedoraproject.org/updates/mutter-3.10.2-5.fc20 will re-introduce this bug, that is expected and intended. I'll try to do a scratch build with the fixes for both this and #995785, but I'm not comfortable sending it to updates-testing without upstream review.
http://koji.fedoraproject.org/koji/taskinfo?taskID=6330186 is a scratch build which includes both the fix for this bug and the current upstream patches for #995785, if people want to test that.
OK, -6 reinstated the fix for this, and has gone stable, so closing again.
I'm not sure if it's fixed. Focusing still does not work properly. For instance, when I start SC2 through wine, the wine window is not made toplevel and it does not have focus. Switching focus with alt-tab sort of works, but the in game keys don't work. It did work well with mutter-3.10.2-2.fc20.
This bug is about on-screen keyboards, not about games in wine.
I've bisected mutter 3.10 branch, commit https://git.gnome.org/browse/mutter/commit/?h=gnome-3-10&id=844f4e9348e29be52ded19d83fdbd1e5e9ce5529 that fixed this report also broke https://bugzilla.redhat.com/show_bug.cgi?id=1047407