I think i find the reason:

I put @ibus-daemon -d --xim into /etc/xdg/lxsession/LXLauncher/autostart , and 
logout, login, ibus-pinyin does works well!

And i put @ibus-daemon -d --xim into /etc/xdg/lxsession/LXDE/autostart, and 
logout ,  login, yes, ibus-pinyin works well, too!

So, JM, help modify the autostart file on svn, and the 2.1release-zh_CN will be 
better!!

Thanks !


t 2013-11-22 09:03:42,"海鑫电脑" <[email protected]> wrote:
>Sorry, i make wrong.
>
>The Fact is: whether in lxlauncher or in LXDE session, i MUST run 
>ibus-setup FIRST, then ibus tell me must start ibus-daemon and then 
>popup the ibus-setup box, click OK, then i can use ibus-pinyin to input 
>chinese words in gedit or lxterm.
>
>I check /etc/X11/xinit/xinit.d/ibus, find something as following:
>
>...
>if [-e /usr/lib/gtk-2.0/*/immodules/im-ibus.so]; then
>     GTK_IM_MODULE=ibus
>else
>     GTK_IM_MODULE=xim
>fi
>
>if [-e /usr/lib/qt4/plugins/inputmethods/libqtim-ibus.so];then
>     QT_IM_MODULE=ibus
>else
>     QT_IM_MODULE=xim
>fi
>DEPENDS="ibus,ibus-gtk|ibus-qt4"
>
>
>And i can't find im-ibus.so under /usr/lib/gtk-2.0/2.10.0/immodule/, but 
>i find im-xim.so. Maybe this is the reason for ibus-pinyin can't run 
>automatlly?
>
>So, how can i do to help resolve the problem?
>
>:)
>
>On 2013/11/22 4:31, Jean-Michel Philippe wrote:
>> Hello,
>>
>>> Third, i put down Ctrl+Space, want to change the input engin to chinese
>>> input method, but when i type, STILL english. That mean: the ibus-pinyin
>>> can't run in the lxlauncher-session.
>>>
>>>
>>> Log out, then login the LXDE session, still no ibus icon. After running
>>> ibus-deamon, ibus icon appear on the bottom right label. And,
>>> ibus-pinyin input method run OK  when i type chinese words into gedit.
>>>
>>> So, what's wrong with the lxlauncher session????
>>>
>>> And, how can we resolve the problem?
>> Usually when a problem of this kind is happening, I try to compare the
>> list of running processes and environment variables in each session in
>> order to find what additional process or variable could be responsible
>> for making something work. You can get an exhaustive list of processes
>> and details with the following command:
>>
>> $ ps -ef
>>
>> And for the list of environment variables and their value, sorted:
>>
>> $ env | sort
>>
>> I'm sorry I can't tell you more, I'm really not used to input method
>> tuning. I'll try to have a look within few days if you can't find an
>> explanation.
>>
>> NB: on the contrary, triggering ibus-deamon at session start is quite
>> trivial.
>>
>
>
>
>_______________________________________________
>Doudoulinux-dev mailing list
>[email protected]
>https://mail.gna.org/listinfo/doudoulinux-dev
_______________________________________________
Doudoulinux-dev mailing list
[email protected]
https://mail.gna.org/listinfo/doudoulinux-dev

Reply via email to