GNOME Bugzilla – Bug 116370
menus automaticly called when typing letters assigned as their shortcuts
Last modified: 2004-12-22 21:47:04 UTC
I'm using xfree86 4.3.0 and gtk-2.2.2. I have diferent layouts specified as: Option "XkbLaout" "us,cz" in XF86Config. when I switch to the cz layout and press a letter that is used as a menu shortcut in a given program, the menu is automaticly called. this leaves me unable to use some of the letters when using czech keyboard, which really annoys me:-) all gtk2 apps I have on my system do the same thing. apps using gtk1.2 work fine. So I guess it has to be in gtk2 lib. But I'm just a user.
I think this is the same as bug 100439 ... the problem is that your keyboard map is using some shortcut such as Control-Alt or Control-Shift as a modifier (probably to switch groups) If you configure a different group-switch method in your XF86Config, things will likely work better. *** This bug has been marked as a duplicate of 100439 ***
nope. I forgot to mention this before, I've already tried that. It does the same thing even when I set it to grp:menu_toggle. however when I change the order of the layouts to cz,us it works ok, but the us keyboard gets some keys redefined plus I want the us layout to be first. Right now, I'm using the old us+cz way to describe the layouts and it works ok, but again, the cz is the first.
It really has to be something with the handling of 'consumed modifiers' ... nothing else could cause such symptoms If someone want to debug into it and see *exactly* what is going on, and exactly what is causing the problem in a particular keyboard layout, I wouldn't object, but I think it's basically part of bug 100439.
It turns out this is actually a bit different from bug 100439 ... while I think whatever fix we come up with for bug 100439 will probably fix this, this problem seems to be an error in the XFree86 keyboard maps of some type. I've put some detailed analysis at: http://bugs.xfree86.org/show_bug.cgi?id=611
*** Bug 118233 has been marked as a duplicate of this bug. ***
*** Bug 121542 has been marked as a duplicate of this bug. ***