Description of problem: This is part of a series of IBus and MCC localization bugs (Skype and 32-bit software https://bugs.mageia.org/show_bug.cgi?id=13168, Libreoffice https://bugs.mageia.org/show_bug.cgi?id=13169, chromium-browser https://bugs.mageia.org/show_bug.cgi?id=13170). The IBus IM system does not work by default with the gvim software (from the vim-X11 package). I do not know the solution. But this should be configured by MCC localization wizard automatically for the user. Reproducible: Steps to Reproduce:
The fix for this is to define the GTK_IM_MODULE_FILE environmental variable, as mentioned in bug #8731 (https://bugs.mageia.org/show_bug.cgi?id=8731). I've tested this on both 32 and 64-bit systems and it works. The package lib64gtk+2.0_0 or libgtk+2.0_0 needs to be installed on 64-bit and 32-bit systems respectively. For 64-bit, run: $ GTK_IM_MODULE_FILE=/etc/gtk-2.0/gtk.immodules.lib64 /usr/bin/gvim For 32-bit, run: $ GTK_IM_MODULE_FILE=/etc/gtk-2.0/gtk.immodules.lib /usr/bin/gvim To make this permanent for all users, add the following line to /etc/profile: export GTK_IM_MODULE_FILE=/etc/gtk-2.0/gtk.immodules.lib64
if there is an universal fix why do you spam the bugzilla ?
The solutions are not universal. Each IBus bug - 32-bit software on 64-bit systems, Libreoffice, and GTK2+ apps - has a different cause and a different fix. The exception might be one or two of the GTK2+ apps, but I'm seeing a different behaviour with gvim vs. firefox and chromium-browser. I was told in another bug report about firefox that these are separate IBus issues (https://bugs.mageia.org/show_bug.cgi?id=8731#c29). So I have submitted a bug report for each, and hope to also write the solution to each problem as I fix them. Would it be better to have one bug report covering all of the MCC IBus configuration issues in Mageia?
Note that setting the GTK_IM_MODULE_FILE environmental variable in Mageia 4 is fatal for GTK3 software including Gnome (https://bugs.mageia.org/show_bug.cgi?id=13170#c6).
see: https://bugs.mageia.org/show_bug.cgi?id=8731 seem solution as this bug..
Unfortunately not even close (https://bugs.mageia.org/show_bug.cgi?id=8731#c47).
This is working fine on a default install of Mageia 5, beta 2.
Blocks: (none) => 11709
CC: (none) => true.bugman
Mageia 4 changed to end-of-life (EOL) status on 2015-09-19. It is is no longer maintained, which means that it will not receive any further security or bug fix updates. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Mageia version. Bug Reporter: Thank you for reporting this issue and we are sorry that we weren't able to fix it before Mageia 4's end of life. If you are able to reproduce it against a later version of Mageia, you are encouraged to click on "Version" and change it against that version of Mageia. If it's valid in several versions, select the highest and add MGAxTOO in whiteboard for each other valid release. Example: it's valid in cauldron and Mageia 5, set to cauldron and add MGA5TOO. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Mageia release includes newer upstream software that fixes bugs or makes them obsolete. If you would like to help fixing bugs in the future, don't hesitate to join the packager team via our mentoring program [1] or join the teams that fit you most [2]. [1] https://wiki.mageia.org/en/Becoming_a_Mageia_Packager [2] http://www.mageia.org/contribute/
As announced over a month ago, Mageia 4 changed to end-of-life (EOL) status on 2015-09-19. It is is no longer maintained, which means that it will not receive any further security or bug fix updates. This issue may have been fixed in a later Mageia release, so, if you still see it and didn't already do so: please upgrade to Mageia 5 (or, if you read this much later than this is written: make sure you run a currently maintained Mageia version) If you are able to reproduce it against a maintained version of Mageia, you are encouraged to 1. reopen this bug report, by changing the "Status" from "RESOLVED - OLD" to "REOPENED" 2. click on "Version" and change it against that version of Mageia. If you know it's valid in several versions, select the highest and add MGAxTOO in whiteboard for each other valid release. Example: it's valid in cauldron and Mageia 5, set to cauldron and add MGA5TOO. 3. give as much relevant information as possible. If you're not an experienced bug reporter and have some time: please read this page: https://wiki.mageia.org/en/How_to_report_a_bug_properly If you see a similar issue, but are _not_sure_ it is the same, with the same cause, then please file a new bug report and mention this one in it (please include the bug number, too). If you would like to help fixing bugs in the future, don't hesitate to join the packager team via our mentoring program [1] or join the teams that fit you most [2]. [1] https://wiki.mageia.org/en/Becoming_a_Mageia_Packager [2] http://www.mageia.org/contribute/
Status: NEW => RESOLVEDResolution: (none) => OLD