Description of problem: The IBus input method (IM) does not work by default for 32-bit programs on 64-bit systems. For this, the libibus1.0_5-1.5.4-4.mga4 package (the Mageia 4 version) needs to be installed. This is not installed on 64-bit systems - it is not a dependency of the 64-bit ibus package: $ urpmq ibus -d | grep ibus ibus ibus-gtk3 ibus-ui-gtk3 lib64ibus-gir1.0 lib64ibus1.0_5 $ The user should not have to manually hunt down such a problem and solution - it is incredibly frustrating as a web search for "skype ibus" will show! The problem can be easily solved in the MCC localization wizard. When 'IBUS' is selected as the 'Input method' on the second page of the wizard, it should install both lib64ibus* and libibus* on 64-bit systems. Just make the 64-bit ibus dependent on libibus1.0_5 as well. This will make the life of an IBus user much easier. Reproducible: Steps to Reproduce:
For reference, I mentioned this same problem in the bug #8731 report at https://bugs.mageia.org/show_bug.cgi?id=8731#c30.
Blocks: (none) => 11709
This works without problem on Mageia 5, beta 2.
closing then (you can do it too ;) ), thanks for the feedback.
Resolution: (none) => FIXEDStatus: NEW => RESOLVED
oups sorry, didn't check version
Resolution: FIXED => (none)Status: RESOLVED => REOPENED
Considering this affects many different GUI toolkits in different ways (https://bugs.mageia.org/show_bug.cgi?id=11709) and it is fixed in mga5 Cauldron, I'd guess the problem is simply the IBus version 1.5.4. The mga5 version is 1.5.8. Would it be possible to have IBus 1.5.8 ported into mga4 "Core Backports Testing" so I can check if this fixes the problems for Mageia 4? Cheers!
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: REOPENED => RESOLVEDResolution: (none) => OLD