Offer some information for those who don't use an DE: I am a bit surprised that I hit this problem too as I thought non-DE users are immune to such problems as they can decide if turn on the input method or not by .xsession. Fact is .xsession no longer have control over what input method to run or in which mode (IM_MODULE/XIM).
I don't use gnome at all on my Ubuntu Maverick 32-bit and what I use for XIM is decided in .xsession (which launches fluxbox), now having this 100% cpu problem, I commented out everything related to xim daemon: #export GTK_IM_MODULE="ibus" #export XMODIFIERS="@im=ibus" #/usr/bin/ibus-daemon --xim & and that doesn't help. With all these commented out, ibus run as usual, means I will not have control over xim daemon like I used to. My preference of using xim (instead of *K_IM_MODULE) is so that I still have control over it in .xsession. It seems things changed now. -- ibus python 100 % cpu for ever https://bugs.launchpad.net/bugs/637671 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
