Bug 555022 - XIM doesn't work on applications via xfrun4.
Summary: XIM doesn't work on applications via xfrun4.
Alias: None
Product: Fedora
Classification: Fedora
Component: xfce-utils
Version: rawhide
Hardware: All
OS: Linux
Target Milestone: ---
Assignee: Kevin Fenzi
QA Contact: Fedora Extras Quality Assurance
Depends On:
TreeView+ depends on / blocked
Reported: 2010-01-13 13:12 UTC by Cong Ma
Modified: 2011-01-17 17:09 UTC (History)
6 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Last Closed: 2011-01-17 17:09:50 UTC
Type: ---

Attachments (Terms of Use)

System ID Private Priority Status Summary Last Updated
Xfce 6178 0 None None None Never

Description Cong Ma 2010-01-13 13:12:50 UTC
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):



How reproducible:


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.


Comment 1 Cong Ma 2010-01-13 13:25:35 UTC
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?

Comment 2 Akira TAGOH 2010-01-14 05:32:00 UTC
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.

Comment 3 Cong Ma 2010-01-14 06:24:00 UTC
(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


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.

Comment 4 Akira TAGOH 2010-01-20 12:06:15 UTC
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.

Comment 5 Kevin Fenzi 2010-01-23 23:29:10 UTC
Added upstream bug here.

Comment 6 Bug Zapper 2010-11-04 01:05:29 UTC
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: 

Comment 7 Akira TAGOH 2010-11-19 02:31:44 UTC
This is still present in even rawhide.

Comment 8 Kevin Fenzi 2011-01-02 19:47:56 UTC
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.

Comment 9 Kevin Fenzi 2011-01-16 19:20:17 UTC
This should be fixed in rawhide. Can anyone confirm?

Comment 10 Akira TAGOH 2011-01-17 10:32:26 UTC
Yes, it looks good to me now. thanks!

Note You need to log in before you can comment on or make changes to this bug.