Description of problem: "Shift" key appears stuck in VNC session on F13 VNC server. Version-Release number of selected component (if applicable): F13 server: tigervnc-1.0.90-0.8.20100219svn3993.fc13.x86_64 F12 viewer: tigervnc-1.0.0-3.fc12.x86_64 How reproducible: Every time. Reproduced using fresh account and VNC server on the F13 box. Steps to Reproduce: 1. ssh <f13box> vncserver -geometry 1680x1050 2. vncviewer <f13box>:1 3. Shift key is stuck, drastically reducing functionality ('Enter' key in dialog boxes, arrow keys, etc.) More information available up on request, if helpful.
Would it be possible to retest this issue with the latest tigervnc packages, 1.0.90-0.9-20100420svn4030, from the updates-testing repo, please? If it is still broken please run "/usr/bin/xev" utility inside vnc session and try to press some keys with/without shift and attach output & key sequence here, please.
The bug does not appear when using the vino server from within a GNOME session (i.e. port 5900). It still appears when using the actual Xvnc port (5901), even under the new build 1.0.90-0.9-20100420svn4030.
Previous Xvnc (1.0.90-0.9-20100420svn4030) was completely busted (bug #585930). Please retest this issue with the latest tigervnc-server-1.0.90-0.10.20100420svn4030.fc13. Thank you in advance.
Problem still occurring with 1.0.90-0.10.20100420svn4030.fc13. When using the vino server from within a GNOME session on port 5900, no problems. When using the Xvnc port 5901, keys act as if the Shift key is stuck.
(In reply to comment #4) > Problem still occurring with 1.0.90-0.10.20100420svn4030.fc13. > > When using the vino server from within a GNOME session on port 5900, no > problems. When using the Xvnc port 5901, keys act as if the Shift key is > stuck. Would it be possible to attach xev output, as written in comment #1, please? In my opinion this is same issue as bug #586406.
Created attachment 412940 [details] Log of /usr/bin/xev activity Typed Shift+a, Shift+b, Shift+c, a, b, c, Shift+Left, Shift+Left, Shift+Left, Left, Left, Left.
Although symptoms are different from bug #586406 fix is same. You can test fixed package from https://bugzilla.redhat.com/show_bug.cgi?id=586406#c3, update will be available soon.
*** This bug has been marked as a duplicate of bug 586406 ***