Bug 101340
Summary: | can type double quotes in certain apps when using gnome keyboard | ||
---|---|---|---|
Product: | [Retired] Red Hat Linux | Reporter: | Need Real Name <onzin> |
Component: | XFree86 | Assignee: | X/OpenGL Maintenance List <xgl-maint> |
Status: | CLOSED CURRENTRELEASE | QA Contact: | David Lawrence <dkl> |
Severity: | medium | Docs Contact: | |
Priority: | medium | ||
Version: | 9 | CC: | otaylor |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | i686 | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2004-10-01 06:05:28 UTC | Type: | --- |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
Need Real Name
2003-07-30 23:29:25 UTC
hmm, so mozilla and openoffice are broken, but gtk 2 applications seem to work. I can now confirm that the same problem exists in The Gimp, Dia and Xchat. So it's not just Mozilla and OpenOffice. I can't reproduce the problem; dead_diaresis+space works fine for me in xterm and other apps that use the standard Xlib compose tables. you might want to check with 'xev' whether the key is producing the dead_diaresis key symbol. If it is, then it's going to be a XFree86 problem; if not, then it would be a problem with the gkb keyboard maps. (The thing is a menace, it should be deleted from the distribution; you may want to install http://gswitchit.sourceforge.net/, which is vastly better implmentation-wise.) Hello Owen, you said that dead_diaresis+space works fine for you - meaning that it produces the desired double quote character? I have tried xev and this happens when I have my keyboard in deadkey mode, when I hit shift and the double quote on the keyboard: KeyPress event, serial 273, synthetic NO, window 0x3600001, root 0x48, subw 0x0, time 21371267, (-28,256), root:(845,827), state 0x10, keycode 62 (keysym 0xffe2, Shift_R), same_screen YES, XLookupString gives 0 bytes: "" KeyPress event, serial 273, synthetic NO, window 0x3600001, root 0x48, subw 0x0, time 21375230, (-28,256), root:(845,827), state 0x11, keycode 48 (keysym 0xfe57, dead_diaeresis), same_screen YES, XLookupString gives 2 bytes: "¨" KeyRelease event, serial 273, synthetic NO, window 0x3600001, root 0x48, subw 0x0, time 21375420, (-28,256), root:(845,827), state 0x11, keycode 48 (keysym 0xfe57, dead_diaeresis), same_screen YES, XLookupString gives 2 bytes: "¨" KeyRelease event, serial 273, synthetic NO, window 0x3600001, root 0x48, subw 0x0, time 21376452, (-28,256), root:(845,827), state 0x11, keycode 62 (keysym 0xffe2, Shift_R), same_screen YES, XLookupString gives 0 bytes: "" And in USA mode: KeyPress event, serial 126, synthetic NO, window 0x3600001, root 0x48, subw 0x0, time 21641784, (78,-11), root:(93,141), state 0x10, keycode 62 (keysym 0xffe2, Shift_R), same_screen YES, XLookupString gives 0 bytes: "" KeyPress event, serial 126, synthetic NO, window 0x3600001, root 0x48, subw 0x0, time 21642624, (78,-11), root:(93,141), state 0x11, keycode 48 (keysym 0x22, quotedbl), same_screen YES, XLookupString gives 1 bytes: """ KeyRelease event, serial 126, synthetic NO, window 0x3600001, root 0x48, subw 0x0, time 21642785, (78,-11), root:(93,141), state 0x11, keycode 48 (keysym 0x22, quotedbl), same_screen YES, XLookupString gives 1 bytes: """ KeyRelease event, serial 126, synthetic NO, window 0x3600001, root 0x48, subw 0x0, time 21644038, (78,-11), root:(93,141), state 0x11, keycode 62 (keysym 0xffe2, Shift_R), same_screen YES, XLookupString gives 0 bytes: "" You say it is now an XFree86 problem? It does not really matter to me, because like I said, I'm mostly a non-technical user - who just wants this thing fixed whatever the underlying trouble should be :) Isn't there anything that I can do about it, myself? Edit a little file or something? Hello Owen, you said that dead_diaresis+space works fine for you - meaning that it produces the desired double quote character? I have tried xev and this happens when I have my keyboard in deadkey mode, when I hit shift and the double quote on the keyboard: KeyPress event, serial 273, synthetic NO, window 0x3600001, root 0x48, subw 0x0, time 21371267, (-28,256), root:(845,827), state 0x10, keycode 62 (keysym 0xffe2, Shift_R), same_screen YES, XLookupString gives 0 bytes: "" KeyPress event, serial 273, synthetic NO, window 0x3600001, root 0x48, subw 0x0, time 21375230, (-28,256), root:(845,827), state 0x11, keycode 48 (keysym 0xfe57, dead_diaeresis), same_screen YES, XLookupString gives 2 bytes: "¨" KeyRelease event, serial 273, synthetic NO, window 0x3600001, root 0x48, subw 0x0, time 21375420, (-28,256), root:(845,827), state 0x11, keycode 48 (keysym 0xfe57, dead_diaeresis), same_screen YES, XLookupString gives 2 bytes: "¨" KeyRelease event, serial 273, synthetic NO, window 0x3600001, root 0x48, subw 0x0, time 21376452, (-28,256), root:(845,827), state 0x11, keycode 62 (keysym 0xffe2, Shift_R), same_screen YES, XLookupString gives 0 bytes: "" And in USA mode: KeyPress event, serial 126, synthetic NO, window 0x3600001, root 0x48, subw 0x0, time 21641784, (78,-11), root:(93,141), state 0x10, keycode 62 (keysym 0xffe2, Shift_R), same_screen YES, XLookupString gives 0 bytes: "" KeyPress event, serial 126, synthetic NO, window 0x3600001, root 0x48, subw 0x0, time 21642624, (78,-11), root:(93,141), state 0x11, keycode 48 (keysym 0x22, quotedbl), same_screen YES, XLookupString gives 1 bytes: """ KeyRelease event, serial 126, synthetic NO, window 0x3600001, root 0x48, subw 0x0, time 21642785, (78,-11), root:(93,141), state 0x11, keycode 48 (keysym 0x22, quotedbl), same_screen YES, XLookupString gives 1 bytes: """ KeyRelease event, serial 126, synthetic NO, window 0x3600001, root 0x48, subw 0x0, time 21644038, (78,-11), root:(93,141), state 0x11, keycode 62 (keysym 0xffe2, Shift_R), same_screen YES, XLookupString gives 0 bytes: "" You say it is now an XFree86 problem? It does not really matter to me, because like I said, I'm mostly a non-technical user - who just wants this thing fixed whatever the underlying trouble should be :) Isn't there anything that I can do about it, myself? Edit a little file or something? Actually, I was wrong about it working for me - it was hard to tell the difference between " and ¨ in ther font I was using in an xterm. If you want to work around the problem on your system you can change, in: /usr/X11R6/lib/X11/locale/en_US.UTF-8/Compose <dead_diaeresis> <space> : "¨" diaeresis to: <dead_diaeresis> <space> : "\"" quotedbl I'm reassigning the bug to the XFree86 component; this has been fixed in upstream XFree86 (Mike - see change to cvs/xc/nls/Compose on 2003/04/03), so we can probably just pull that change into our package. Great, thanks for the hint of editing the "Compose" file. """""""""" :) (and sorry for the double post of comments above, I was just browsing back and forth with Mozilla in the bug system, and somehow submitted the thing twice) FWIW, this issue is reported many times in bugzilla already, both ours and upstream's. I believe the patch is in rawhide already, if not it's in my patch queue which I'll be processing when I return from vacation. If someone tests latest rawhide and reports back here, please close bug if it works right in rawhide. Thanks. Since this bugzilla report was filed, there have been several major updates to the X Window System, which may resolve this issue. Users who have experienced this problem are encouraged to upgrade to the latest version of Fedora Core, which can be obtained from: If this issue turns out to still be reproduceable in the latest version of Fedora Core, please file a bug report in the X.Org bugzilla located at http://bugs.freedesktop.org in the "xorg" component. Once you've filed your bug report to X.Org, if you paste the new bug URL here, Red Hat will continue to track the issue in the centralized X.Org bug tracker, and will review any bug fixes that become available for consideration in future updates. |