I have my own keyboard layout with Caps Lock turned to other modifier key, like shift or alt, to write more kinds of character, like Greek letters. With Qt, X or <Gtk+-2.10.11 it worked, after upgrade, the Gtk apps don't receive these characters. They do not appear in the input line, but they can be copied into it and show alright, so I guess it is in the input, not in fonts or rendering. I'm using the xim input method for GTK (GTK_IM_MODULE="xim"). If the configs are of any use, they can by found as http://vorner.pretel.cz/xkbconf.tar.bz2 - I took everything that is above standard xkb configs, there may be some files that are not used by this particular setup. Any other information I could provide? Or should I put the report somewhere else? Thank you
I was playing around a little bit with the code and traced the problem to file modules/input/gtkimcontextxim.c. I diffed it against some old working version and found only these 2 changes: 580c580 < else --- > else if (context_xim->im_info->im) 730a731,734 > if (event->state & > (gtk_accelerator_get_default_mod_mask () & ~(GDK_SHIFT_MASK | GDK_CONTROL_MASK))) > return FALSE; > With this file (only the file, nothing else) downgraded to the original version, the characters started working. I'm going to trace which of these 2 changes caused the problem and will try to find out, why this change happened.
So I identified it to the second longer change (the "if (event->state & ..."). It is revision 17446 (http://svn.gnome.org/viewcvs/gtk+?view=revision&revision=17446). Do you think I should put this bug to the gtk's bugzilla? It seems like all gtk will do this, not just gentoo one. Thank you
I suggest you open a bug upstream and post the url here. Upstream gtk devs will probably be know why this change was made. Thanks :)
Ok, it is submitted to bugzilla.gnome.org as bug #458259.
Michal, Is this still an issue? Could you try pinging upstream again (or closing the bug if it's fixed) ? Thanks
Good morning > Is this still an issue? Could you try pinging upstream again (or closing the > bug if it's fixed) ? Yes, the problem is still valid with gtk+-2.12.9-r2 package. I wrote to the gnome bugzilla again today and hope they will do something about it.
Still the case with 2.18?
Please don't hesitate to reopen this bug if you can still reproduce with an updated version of gtk+. Thanks