After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 121542 - each key press behaves like with Alt keys was pressed too
each key press behaves like with Alt keys was pressed too
Status: RESOLVED DUPLICATE of bug 116370
Product: gtk+
Classification: Platform
Component: Widget: Other
2.2.x
Other Linux
: Normal blocker
: ---
Assigned To: gtk-bugs
gtk-bugs
Depends on:
Blocks:
 
 
Reported: 2003-09-05 13:42 UTC by hales
Modified: 2004-12-22 21:47 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description hales 2003-09-05 13:42:32 UTC
In several gtk2 applications I have tried (galeon-1.3.7, gaim-0.68 and 
even the filesel example from gtk2) I have serious problem with 
simple key press.

Any time I press a key, the result is as if I have pressed the Alt key also.

I have compiled the filesel example with debug gtk2 and the relevant part of 
debug info is:

   Gdk-Message: key press  :        window: 41943043         key: c 99
   Gdk-Message:            length:    1 string: "c"
   Gtk-Message: Looking up keycode = 54, modifiers = 0x0000,
    keyval = 99, group = 0, level = 0, consumed_modifiers = 0x608b
   Gtk-Message:   found exact match, keyval = 99, modifiers = 0x0008
   Gtk-Message:   found exact match, keyval = 99, modifiers = 0x0008
   Gdk-Message: key release:         window: 41943043        key: c 99
   Gdk-Message:            length:    1 string: "c"

It seems to me, that the problem is between the 3rd and 4th message, where
the modifiers changes from 0x0000 to 0x0008.

I do not have a clue about how to correct this situation.
Comment 1 hales 2003-09-05 14:43:49 UTC
I have now compiled and installed new gtk2-2.2.4 and the problem 
dissappeared! super, thanks very much!

-- 
hales
Comment 2 Owen Taylor 2003-09-05 15:03:02 UTC
it's actually only coincidentally fixed by 2.2.4, the actual
bug here is a XFree86 bug.
Comment 3 Owen Taylor 2003-09-05 15:05:10 UTC

*** This bug has been marked as a duplicate of 116370 ***