Bug 525376 - ibus.desktop should not be installed
Summary: ibus.desktop should not be installed
Alias: None
Product: Fedora
Classification: Fedora
Component: ibus
Version: 12
Hardware: All
OS: Linux
Target Milestone: ---
Assignee: Peng Huang
QA Contact: Fedora Extras Quality Assurance
Depends On:
TreeView+ depends on / blocked
Reported: 2009-09-24 05:54 UTC by A S Alam
Modified: 2013-07-03 00:53 UTC (History)
7 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Last Closed: 2009-12-01 05:38:55 UTC

Attachments (Terms of Use)
Attaching .imsettings.log File (7.10 KB, text/plain)
2009-09-24 05:55 UTC, A S Alam
no flags Details
Imsetting file (1.51 KB, application/octet-stream)
2009-09-25 08:01 UTC, A S Alam
no flags Details
Error Screenshot for iBus (352.88 KB, image/jpeg)
2009-10-08 07:07 UTC, A S Alam
no flags Details
parent process graph for ibus (1.75 KB, text/plain)
2009-10-29 04:28 UTC, A S Alam
no flags Details

Description A S Alam 2009-09-24 05:54:30 UTC
Description of problem:
after Each login, there is error (or just) message that "Unable to keep Input Method Running" (and more detail). But IBus was working Normal after this message. 

Version-Release number of selected component (if applicable):

How reproducible:

Steps to Reproduce:
1. login to local language desktop
2. you will get message if not please follow
3. System->Preferences -> Input Method
4. There was nothing Selected
5. Try to Enable Input Method
Actual results:
message will be there on Right Top Corner

Expected results:
Default Should be enabled as Ibus was working or no such message

Additional info:

Comment 1 A S Alam 2009-09-24 05:55:42 UTC
Created attachment 362432 [details]
Attaching .imsettings.log File

Comment 2 Akira TAGOH 2009-09-24 07:39:01 UTC
which version of imsettings are you using?

Comment 3 A S Alam 2009-09-24 08:36:50 UTC

Comment 4 Akira TAGOH 2009-09-24 09:47:42 UTC
Can you have the real steps to reproduce this issue? as the log file you've attached at Comment #1 said, this message appears because ibus-daemon is already running. in other words, the key point is how you can see ibus-daemon running after even logged out.

FWIW there were a bug that imsettings couldn't terminate it properly in the older version. so if you've tried on rawhide box live-updated from the older imsettings, this issue may occurs. and there are no way of preventing it unfortunately.

Otherwise please give me more info how to reproduce that.

Comment 5 A S Alam 2009-09-24 10:10:51 UTC
ok, it was upgrade, also produced when upgrade from Fedora 10 to Fedora 11.
Steps are same, as I login each time, it shows same message, but only with
upgrade (fedora 10 to fedora 11 or fedora 11 ->rawhide).

Please close bug as you find more relevant type (to close)

Comment 6 Akira TAGOH 2009-09-24 10:24:26 UTC
Okay. please make sure you don't see this issue after killing ibus-daemon manually or just reboot your machine. if you still see, please reopen this.


Comment 7 A S Alam 2009-09-25 03:23:56 UTC
Sorry, but it is appearing with each login (even after restart also)

Comment 8 Akira TAGOH 2009-09-25 05:06:33 UTC
Sure. please check if:

1. you're sure no ibus-daemon is running at first.
2. ibus-daemon is running once you log into the desktop and log out. you can see that from the console say. press alt+ctrl+Fn on gdm to switch VT.

then attach .imsettings.log again _before_ logging into the desktop again. also describe what you did during the desktop session is alive.

Comment 9 A S Alam 2009-09-25 08:01:00 UTC
Created attachment 362635 [details]
Imsetting file

after reboot machine, I login once, did Nothing (message was there), 
just logout. copy .imsettings.log file from VT without GUI login.

Let me know if any step was wrong to redo.

Comment 10 Akira TAGOH 2009-09-25 12:39:19 UTC
Did you see that message with even the first login after rebooting? hmm, then please check if ibus-daemon is running after rebooting. if it's there, who's the parent of its process?

Comment 11 Akira TAGOH 2009-10-06 06:25:44 UTC
(In reply to comment #9)
> after reboot machine, I login once, did Nothing (message was there), 
> just logout. copy .imsettings.log file from VT without GUI login.

To clarify more, what kind of the message did you see?

Comment 12 A S Alam 2009-10-08 07:07:03 UTC
Created attachment 364061 [details]
Error Screenshot for iBus

"Unable to keep Input Method Running..."
Screenshot is not very clear, but message is like that

Comment 13 Akira TAGOH 2009-10-08 07:38:06 UTC
Aha. didn't you reboot your machine before this testing? then please read comment #10. I'm not quite sure where that process was being brought up from.

Any further information are welcome too. at least it works for me on GNOME desktop with the users newly created.

Comment 14 sangu 2009-10-25 11:14:22 UTC
The same problem happens in my linux.

locale : ko_KR.UTF-8
$ cat .xinputrc 

if test -f /usr/lib/qt4/plugins/inputmethods/libqtim-ibus.so || \
   test -f /usr/lib64/qt4/plugins/inputmethods/libqtim-ibus.so;


Comment 15 Akira TAGOH 2009-10-26 08:54:30 UTC
Can anyone give me the useful information as I told at comment #10?

Comment 16 A S Alam 2009-10-29 04:28:36 UTC
Created attachment 366544 [details]
parent process graph for ibus

Comment 17 Akira TAGOH 2009-10-29 04:58:00 UTC
Thanks. I guess you've enabled a kind of the self-running feature with XDG's autostart before. you may have ibus.desktop or something like that in $HOME/.config/autostart ?

Comment 18 Akira TAGOH 2009-10-29 05:10:53 UTC
After the talk with Alam on IRC, my guess is correct. since we don't use this feature in Fedora at least, it may be a good idea to get rid of that file automatically if available. reassigning to ibus for that.

Comment 19 Bug Zapper 2009-11-16 12:50:27 UTC
This bug appears to have been reported against 'rawhide' during the Fedora 12 development cycle.
Changing version to '12'.

More information and reason for this action is here:

Comment 20 Peng Huang 2009-11-25 05:44:53 UTC
I have removed auto start feature in current ibus. Probably this file was created by early version. Please remove it by self. Thanks.

Comment 21 Akira TAGOH 2009-11-25 06:02:04 UTC
Right. but it's not that reasonable to remove by the hand since this causes not working ibus. I don't know how many people used that feature though, the fix in ibus should be easier than the cost of the problem.

Plus, any version of ibus doesn't provide any solutions for *this* issue since the bug reporter complains ibus.desktop introduced the issue ibus not running. so closing as CURRENTRELEASE is wrong at least.

Comment 22 Peng Huang 2009-12-01 03:58:18 UTC
Hi Tagoh-san,

Actually, this feature has been removed for a long time (Only 0.1.x has this feature). 1.1.x and 1.2.x do not have it. I think it is not necessary to remove it automatically. If really need it, I suggest do it in xinit script (For exmaple /etc/X11/xinit/xinitrc.d/50-xinput.sh). ibus can not remove it before X init scripts.

If you agree, I will move this bug to imsettings, and we fix it in /etc/X11/xinit/xinitrc.d/50-xinput.sh, or I will close it as wontfix.

Comment 23 Akira TAGOH 2009-12-01 05:27:00 UTC
(In reply to comment #22)
> Hi Tagoh-san,
> Actually, this feature has been removed for a long time (Only 0.1.x has this
> feature). 1.1.x and 1.2.x do not have it. I think it is not necessary to remove
> it automatically. If really need it, I suggest do it in xinit script (For
> exmaple /etc/X11/xinit/xinitrc.d/50-xinput.sh). ibus can not remove it before X
> init scripts.

ibus isn't brought up before xinit script right. there are no reasons ibus can't remove it.

The problem is, two ibus instance is going to run. and ibus.desktop is prior to imsettings'. so you can do change the logic in ibus like if there are ibus.desktop under $HOME/.config/autostart, remove it and just exit. this would resolves this issue and imsettings successfully can brings up ibus then.

Comment 24 Peng Huang 2009-12-01 05:38:55 UTC
I still think it is not good to do it in ibus.
Users also have right to use gnome-sesstion-properties to create it by self. So I will close it as wontfix. Thanks.

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