Hi, sorry for doubleness.
2006/7/12, Jan Willem Stumpel <[EMAIL PROTECTED]>:
Masahito Omote wrote:
The results of
uim-xim --trace > uimxim.txt &
and
uim-xim --trace-xim >uimxim2.txt &
are enclosed.
Thank you. But checking the outputs, uim-xim --trace/--trace-xim does
not work on your machine.
It is no use running secondery uim-xim process, it just exits.
If another uim-xim process is running, kill it first.
Checking the source code, uim-xim --trace --trace-xim is available.
Please try again with "uim-xim --trace --trace-xim".
> The easiest way to solve this problem is stop using XIM in
> Firefox and Mozilla
How? By changing the GTK_IM_MODULE environment variable, or by
something else?
GTK_IM_MODULE=uim :D
> until I can fix it. Both Firefox and Mozilla supports GTK+
> immodule. Are there any reasons not to use GTK+ immodule?
As I said in http://www.jw-stumpel.nl/stestu.html, the gtk+
immodule system is almost useless. Hardly any programs work with
it (not even Mozilla and Firefox). If you want international input
in all programs, you have to use xim. This even works in ancient
programs like xfig. Ming Hua recommends the same for scim.
Yes, it's true we have to use XIM if we support *all* programs running in X
or run in system call emulating system such as linuxlator in such as
FreeBSD and NetBSD because it's too difficult and complicated to use
GTK+/QT immodule.
But uim project does not make much of XIM implementation.
In uim project, we recommends using toolkit's input method framework directly,
such as GTK/QT immodule. uim-xim implementation was implemented for
backword compatibility like classic applications.
uim was developed as antithesis of IIIMF and XIM.
You can learn the background of uim by checking anthy-dev(written in
Japanse) ML (2002-2003) in sourceforge.jp .
> And you can also attach uim-xim process by using $ strace -p
> [uim-xim's pid] or $gdb uim-xim [uim-xim's pid] before starting
> firefox process.
So far, I did not have success with this, because when I make
Mozilla/Firefox crash (by putting my finger down half-way between
CapsLock and A) X becomes completely unusable.
Before stating Firefox/Mozilla, go to VT and run strace -p/gdb.
Summary
1. Kill all uim-xim process and uim-xim related X applications first.
And run new terminal.
2. uim-xim --trace --trace-xim> /path/to/output & in 1's new X terminal.
3. Go to VT and strace -p [uim-xim's pid] or gdb .
4. Run /usr/bin/firefox or /usr/bin/mozilla-browser
5. If crashed, go to VT, kill firefox/mozilla-browser process. If you
cannot go to
VT, use CTRL+ALT+BS.
6. Do 1-5 with using gdb /usr/bin/uim-xim [uim-xim's pid] insted of strace.
7. If you have a time to check, do Justin's debug solution written in
Bug#366390.
Thanks
--
Masahito Omote([EMAIL PROTECTED])
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
