Clarifications needed on ibus-daemon command usages
கா. சேது | කා. සේතු | K. Sethu
I see that for an on-the fly ad-hoc use, ibus can be launched and used
with "ibus-daemon" command in the following two ways :
1). ibus-daemon -d
When daemonised with the above command usage, the loaded processes (as
shown by "ps -A |grep ibus") are as follows :
ibus-daemon
ibus-gconf
ibus-engine-m17
2). ibus-daemon -d -x
With the additional flag -x for the command I find that in addition to
the above 3 processes the following fourth process is also loaded:
ibus-x11
My questions:
a) What is the purpose of the additional process of ibus-x11?
b) Is ibus-x11 necessary for any application?
By "ad-hoc" use I mean not having ibus auto started through im-switch
or through startup applications setting or through scripts in .bashrc
or the likes but launching it only when needed during a session .
Both above command usages works to start ibus.
If needed we can right click on ibus daemon icon and use "Preferences"
to add keymaps.
We can also terminate ibus during the session by right click and press
"quit" . There is however a difference between the above two usages if
the we forget to quit before logging out.
With method 2 (i.e., ibus-xim is also loaded) without having quit from
ibus, logging out and logging in back again teh new session starts
without any of the 4 processes loaded. If ibus is needed again we can
then use the same command to launch ibus and use.
But with the method 1 (i.e., without ibus-xim loaded) without having
quit from ibus, on re-login it is found that the 3 processes persists
running in the background whereas the icon is not seen in the tray.
This leads to a buggy situation that any attempt to bring back the
icon with same command fails. The only way out seems to be to first
kill all the processes with the following command : "killall
ibus-daemon" and then launch with "ibus-daemon -d" command.
Any reason why in an ad-hoc use mode if ibus-xim is not loaded log-out
does not terminate the 3 processes ?
~Sethu
Peng Huang
I am testing ibus usages in Ubuntu 9.10 (Karmic Koala) / Gnome Desktop
I see that for an on-the fly ad-hoc use, ibus can be launched and used
with "ibus-daemon" command in the following two ways :
1). ibus-daemon -d
When daemonised with the above command usage, the loaded processes (as
shown by "ps -A |grep ibus") are as follows :
ibus-daemon
ibus-gconf
ibus-engine-m17
2). ibus-daemon -d -x
With the additional flag -x for the command I find that in addition to
the above 3 processes the following fourth process is also loaded:
ibus-x11
My questions:
a) What is the purpose of the additional process of ibus-x11?
b) Is ibus-x11 necessary for any application?
By "ad-hoc" use I mean not having ibus auto started through im-switch
or through startup applications setting or through scripts in .bashrc
or the likes but launching it only when needed during a session .
Both above command usages works to start ibus.
If needed we can right click on ibus daemon icon and use "Preferences"
to add keymaps.
We can also terminate ibus during the session by right click and press
"quit" . There is however a difference between the above two usages if
the we forget to quit before logging out.
With method 2 (i.e., ibus-xim is also loaded) without having quit from
ibus, logging out and logging in back again teh new session starts
without any of the 4 processes loaded. If ibus is needed again we can
then use the same command to launch ibus and use.
But with the method 1 (i.e., without ibus-xim loaded) without having
quit from ibus, on re-login it is found that the 3 processes persists
running in the background whereas the icon is not seen in the tray.
This leads to a buggy situation that any attempt to bring back the
icon with same command fails. The only way out seems to be to first
kill all the processes with the following command : "killall
ibus-daemon" and then launch with "ibus-daemon -d" command.
Any reason why in an ad-hoc use mode if ibus-xim is not loaded log-out
does not terminate the 3 processes ?
Grissiom
> ibus-daemon does not depend on X, it can also be used in console, so it will
> not exit with X server. But ibus-x11 is an X application, it will be
> terminated with X server. If ibus-x11 starts with --kill-daemon, it will
> also send a kill message to daemon during X exiting, so I think it is better
> to start it.
What's the difference between ibus-x11 and ibus-gtk(or purely ibus)?
How to build it from source?
--
Cheers,
Grissiom