Description of problem: When the input point is in an EMACS window, ibus input methods cannot be activated. When clicking on the ibus icon, it does not show the input method selection menu, but a bare message of 'no input window' (没有输入窗口). This makes ibus unusable in EMACS. Version-Release number of selected component (if applicable): ibus-pinyin-1.2.0.20090915-1.fc12.noarch ibus-libs-1.2.0.20100111-1.fc12.i686 ibus-1.2.0.20100111-1.fc12.i686 ibus-gtk-1.2.0.20100111-1.fc12.i686 emacs-23.1-13.fc12.i686 How reproducible: Always. Steps to Reproduce: 1. Start EMACS, 2. Lose :( Actual results: Can't activate ibus input method in EMACS. Expected results: ibus should have worked with any GUI program that takes keyboard input. Additional info: I don't really know whether this is an ibus bug or one of EMACS. If anyone can identify the package at fault, please feel free to correct me. The GTK version is gtk2-2.18.5-4.fc12, if that is useful. Thanks.
OK, this is funny. Or not. My further tinkering with EMACS and ibus revealed the following pattern of the bug's occurrence. If I start EMACS from a terminal emulator, everything works fine; if EMACS is started from xfrun4 (XFCE's app launcher), then the bug is reproduced. I'm confused. Now we have a third possible offending component i.e. the XFCE4 libraries. What should I do?
Please make sure if you can see "XMODIFIERS: @im=ibus" in $HOME/.imsettings.log. also try to find out from /proc/<pid>/environ if the process has the certain XMODIFIERS.
(In reply to comment #2) > Please make sure if you can see "XMODIFIERS: @im=ibus" in > $HOME/.imsettings.log. > > also try to find out from /proc/<pid>/environ if the process has the certain > XMODIFIERS. Hi, Thanks for the reply. Just checked, that the line "XMODIFIERS: @im=ibus" was present in my .imsettings.log file. I also followed your advice of checking the environment variables. The EMACS process created from a shell had XMODIFIERS=@im=ibus in its list of environment variables, but the process created from xfrun4 did not have such a variable (along with other missing variables, e.g. IMSETTINGS_INTEGRATE_DESKTOP and IMSETTINGS_MODULE). Hope that helps. BTW: Other programs started by xfrun4 don't have XMODIFIERS environ. variable either, but the normal functionality of ibus with them is not affected by the absence of such a varialbe.
Well, because xfrun4 is raised through DBus and it doesn't inherit any environment variables the desktop has. guess nothing I can do in imsettings because imsettings can't run prior to the session bus since it also requires DBus. Reassigning to xfce-utils.
Added upstream bug here.
This message is a reminder that Fedora 12 is nearing its end of life. Approximately 30 (thirty) days from now Fedora will stop maintaining and issuing updates for Fedora 12. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as WONTFIX if it remains open with a Fedora 'version' of '12'. 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 Fedora version prior to Fedora 12'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 Fedora 12 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 Fedora please change the 'version' of this bug to the applicable version. If you are unable to change the version, please add a comment here and someone will do it for you. 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 Fedora release includes newer upstream software that fixes bugs or makes them obsolete. The process we are following is described here: http://fedoraproject.org/wiki/BugZappers/HouseKeeping
This is still present in even rawhide.
Sorry this has lingered around so long. From what I have read, this should be fixed in the upcoming 4.8 release. "The environment variables of commands launched from the Xfce run dialog were not set properly, so we fixed that so that commands launched from the dialog always inherit the environment of the Xfce session. " We can test this as soon as we land 4.7.x in rawhide. Thanks for your patience.
This should be fixed in rawhide. Can anyone confirm?
Yes, it looks good to me now. thanks!