Yocto commit a8c25af9 ("matchbox-keyboard: export GTK_IM_MODULE_FILE location") broke gtk3 apps (they segfault in XSendEvent with gtk im stuff in backtrace). The commit uses GTK_IM_MODULE_FILE to set the module location, which breaks because the env var is used by _both_ gtk2 and gtk3 (and the modules obviously are not compatible). I think we need to fix the postinst script to generate the files in the right place to begin with. It should not be difficult (I think we can hard code the api-version-directory -- it's been 2.10.0 for gtk2 forever). Ross: can you confirm what the state of matchbox-keyboard-as-IM-for-gtk3 should be? My guess was that it can't do that (or at least that the im module is not implemented) but I think I never tried before...
Yeah matchbox-keyboard, specifically the bridge, needs porting to GTK+ 3.
I haven't checked the impact on gtk3 applications by that patch (GTK_IM_MODULE_FILE is used by both gtk2 and gtk3). Sorry for that. Yes, the proper way will be to fix gtk-immodules-cache.bbclass.
Patch sent to the oe-core ML: http://lists.openembedded.org/pipermail/openembedded-core/2016-February/116647.html
http://git.yoctoproject.org/cgit/cgit.cgi/poky/commit/?id=333dce483fc056512443a7a318f55abace7ca98a
(In reply to comment #4) > http://git.yoctoproject.org/cgit/cgit.cgi/poky/commit/ > ?id=333dce483fc056512443a7a318f55abace7ca98a Hi I need a little more details in order to verify this one.
We don't have any gtk3 apps in sato by default, so I think you need to take Jussi not reopening this as verification.
Based on Ross comments this can be closed.