Hide Forgot
Description of Problem: I have a keyboard map that allows me to use Shift-Shift combination to switch between English and Cyrillic keyboard maps: % xmodmap -pk -pm | grep Shift shift Shift_L (0x32), Shift_R (0x3e) 50 0xffe1 (Shift_L) 0xfe0a (ISO_Prev_Group) 62 0xffe2 (Shift_R) 0xfe08 (ISO_Next_Group) Now if I start vncviewer, after the first time I use Shift (the single one, not the Shift-Shift), vncviwer will start sending Shift-xxx events instead of xxx events (for xxx in mouse click, Enter key press, etc). How Reproducible: Always Steps to Reproduce: 1. Run xmodmap -e "keysym Shift_L = Shift_L ISO_Prev_Group" -e "keysym Shift_R = Shift_R ISO_Next_Group" 2. Start vncviewer 3. Press Shift-A, then (after Shift is released) press Enter (or click mouse) Actual Results: You get Shift-Enter (or Shift-mouseclick) event in the remote VNC session. Expected Results: You get Enter (or mouseclick) event in the remote VNC session. Additional Information: - I am using XFree86 v4 and KDE desktop. I do not have any problems like that with any applications except for vncviewer. - If I press F8 or leave vncviewer window and come back, the vncviwer temporarily reverts to normal state (until I press Shift again). - If I chose to use Shift-CapsLock combination for switching groups instead of Shift-Shift: lock Caps_Lock (0x42) 66 0xffe5 (Caps_Lock) 0xfe08 (ISO_Next_Group) that everything works (but I have to get used to using a new key combination).
Created attachment 18572 [details] Remote xev output - "bad"
Created attachment 18573 [details] Remote xev output - "good"
Both xev outputs show what happens when I press the following keys: a; LShift-a; a; Enter The first output was produced after I ran (locally) xmodmap -e "keysym Shift_L = Shift_L ISO_Prev_Group" -e "keysym Shift_R = Shift_R ISO_Next_Group" before starting vncviewer; and the second one was produced when I ran modmap -e "keysym Shift_L = Shift_L" -e "keysym Shift_R = Shift_R" before starting vncviewer.
Red Hat Linux is no longer supported by Red Hat, Inc. If you are still running Red Hat Linux, you are strongly advised to upgrade to a current Fedora Core release or Red Hat Enterprise Linux or comparable. Some information on which option may be right for you is available at http://www.redhat.com/rhel/migrate/redhatlinux/. Red Hat apologizes that these issues have not been resolved yet. We do want to make sure that no important bugs slip through the cracks. Please check if this issue is still present in a current Fedora Core release. If so, please change the product and version to match, and check the box indicating that the requested information has been provided. Note that any bug still open against Red Hat Linux on will be closed as 'CANTFIX' on September 30, 2006. Thanks again for your help.
Have not seen this in a long time.