Description of problem: I don't remember any recent update on ibus or anthy (but also I don't always put particular attention to all the updates), but I can't use it anymore. ibus still works. I have other input methods like the Korean one, which still work. But when I try to switch to the Anthy input method (whatever by the usual shortcut or by clicking with the mouse the Anthy input in the contextual menu), I can't seem to make it work either (ibus just hangs for a few seconds, then goes back to previous input). I tried to restart ibus, no luck either there. It didn't change a thing (once it even crashed apparently because it did not come back up again). I also tried in various applications where it usually works (Firefox, LibreOffice, Konsole, etc.) to be sure that was not related somehow to the toolkit. Same everywhere. And now I am unsure of how to diagnose. Also how do you check which packages have recently be installed to make sure of regressions in some package? Version-Release number of selected component: - anthy 9100h-25.20110409.1.mga2 - ibus-anthy 1.2.6-1.mga2 - ibus 1.4.1-1.mga2 Steps to Reproduce: 1. Go into any program where you know it used to work; 2. start the ibus-anthy input the way you used to do (contextual menu in the task bar, shortcut, etc.). 3. See it doesn't work. Note: I set this as major, because I considered that the possibility to write a full language is a major feature. Hope that's ok.
Hello, I have a friend who installed a Mageia 2 just yesterday and she installed also the ibus-anthy for Japanese input, she gets same as me! She can't write in Japanese! But same as me, she can still use ibus for Korean input. Just to say I am not alone. I guess that makes this bug quite reproducible.
Does ibus-anthy-1.3.99.20120327-1.mga2 works better?
Status: NEW => ASSIGNED
I just tried to install it, that told me: A requested package cannot be installed: ibus-anthy-1.3.99.20120327-1.mga2.x86_64 (due to unsatisfied typelib(Anthy)) I am not sure what this "typelib(Anthy)" means. Does Anthy has to be updated too? I could not find an update for it in updates_testing.
typelib(Anthy) is provided by lib64anthy-gir9000, you sure enable the whole updates_testing repository to install new ibus-anthy.
https://wiki.mageia.org/en/Enabling_the_Testing_media
Thanks Claire! That was exactly the link I needed! I indeed was not able to set updates testing as update source and was installing directly through the package file (hence no dependency resolution). Anyway Funda: I installed it, it did not fix the issue. I still can use all input but Anthy. :-/
By the way, if you have any idea which package I could revert to get back to a working Japanese input, I would be grateful. I won't mind from time to time re-update to newer versions of whatever is broken when you need logs, investigation or tests. But in the meantime, I'd love to have working input. Right now I have to go all the time to some crappy web service with Japanese input, then do copy pasting. That sucks. ;-(
Hi! I don't want to look like an ass or something, but seriously, is there a way to downgrade whatever was upgraded in Mageia in the last 2 weeks or so? I really need Japanese, and my friend needs Japanese daily even more. She is complaining to me every day and all I can tell her is I am looking into it. :-/ Could you imagine if you could not write one of your main language, for instance if you were not able to write English in Mageia anymore for the last week (and for how long more, you have no idea)? Also my mother (who is Japanese, lives and works in Japan), I told her not to run any automatic update anymore for now. So she has to stay without update for as long as we can't have this working. That's really really blocking for people needing to write Japanese. :-/
Created attachment 3631 [details] Terminal output when running ibus-setup, then anthy settings. Hello, I started ibus-setup on terminal, which outputs the following warnings: ----------------------------------------------- ** (process:23996): WARNING **: Trying to register gtype 'GMountMountFlags' as enum when in fact it is of type 'GFlags' ** (process:23996): WARNING **: Trying to register gtype 'GDriveStartFlags' as enum when in fact it is of type 'GFlags' ** (process:23996): WARNING **: Trying to register gtype 'GSocketMsgFlags' as enum when in fact it is of type 'GFlags' ----------------------------------------------- Then when I run the preferences for the anthy input method, I have a whole bunch of ibus-warnings about dbus errors. I guess this may be linked to the problem. Basically this kind of errors: ----------------------------------------------- (main.py:21504): IBUS-WARNING **: org.freedesktop.IBus.Config.GetValue: GDBus.Error:org.freedesktop.DBus.Error.Failed: Config value [engine/anthy/thumb_typing_rule/kb231_f_fmv_table:0] does not exist. (main.py:21504): IBUS-WARNING **: org.freedesktop.IBus.Config.GetValue: GDBus.Error:org.freedesktop.DBus.Error.Failed: Config value [engine/anthy/thumb_typing_rule/kb231_f_fmv_table:3] does not exist. (main.py:21504): IBUS-WARNING **: org.freedesktop.IBus.Config.GetValue: GDBus.Error:org.freedesktop.DBus.Error.Failed: Config value [engine/anthy/thumb_typing_rule/kb231_f_fmv_table:=] does not exist. (main.py:21504): IBUS-WARNING **: org.freedesktop.IBus.Config.GetValue: GDBus.Error:org.freedesktop.DBus.Error.Failed: Config value [engine/anthy/thumb_typing_rule/kb231_f_fmv_table:-] does not exist. (main.py:21504): IBUS-WARNING **: org.freedesktop.IBus.Config.GetValue: GDBus.Error:org.freedesktop.DBus.Error.Failed: Config value [engine/anthy/romaji_typing_rule/default:pyu] does not exist. ----------------------------------------------- The full log of terminal errors/warnings are attached. When searching the web for similar errors, I found last years similar issues on OpenSuse (http://lists.opensuse.org/opensuse-m17n/2012-06/msg00000.html), where users were ibus-anthy stopped to work either, some with ibus-anthy 1.4.99, others with 1.3.99 (as in Mageia). I also found this one on Archlinux bug tracker: https://bugs.archlinux.org/task/32293 Not sure this is the same, because I don't have import errors in my log though, but there is something similar, it is also about ibus-anthy and that's recent. On RedHat bug tracker, I found this ticket: https://bugzilla.redhat.com/show_bug.cgi?id=522047 That's a much older ticket and ibus-anthy is an older version too, but that's about missing references from the thumb module, and I note that in my output too, many config value in error are "thumb" related, though not all. Maybe there is a hint? I don't know the code, architecture or anything of Anthy or ibus, so I can't really investigate much more right now because I'm not sure where to look. But know that I can do any necessary test and log output if you tell me the steps. The impossibility to write Japanese becomes more and more unbearable every day and I really need this fix. ;-(
This message is a reminder that Mageia 2 is nearing its end of life. Approximately one month from now Mageia will stop maintaining and issuing updates for Mageia 2. At that time this bug will be closed as WONTFIX (EOL) if it remains open with a Mageia 'version' of '2'. 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 prior to Mageia 2's end of life. Bug Reporter: Thank you for reporting this issue and we are sorry that we may not be able to fix it before Mageia 2 is end of life. If you would still like to see this bug fixed and 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. 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. -- The Mageia Bugsquad
Blocks: (none) => 11709
Mageia 2 changed to end-of-life (EOL) status on ''22 November''. Mageia 2 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Mageia please feel free to click on "Version" change it against that version of Mageia and reopen this bug. Thank you for reporting this bug and we are sorry it could not be fixed. -- The Mageia Bugsquad
Status: ASSIGNED => RESOLVEDResolution: (none) => OLD