Hi. 2006/7/11, Jan Willem Stumpel <[EMAIL PROTECTED]>:
Masahito Omote wrote: > Probably this bug comes from uim. But I cannot reproduce.
In my case, I have been able to reproduce this very reliably for many months (see also my CC'd message to you, May 9th).
Umm..., I tested it again and again but it does not reproduce. Please check 'uim-xim --trace > /path/to/output1 &' and 'uim-xim --trace-xim
/path/to/output2' and give me their outputs.
And let me know what Window Manger and Session Manager you are using?
> First, list up your environment variables. I cannot find out > which method - XIM or GTK+ immodule you are using? I use xim. It is incredibly difficult to produce any backtrace, because X freezes completely. I sent some results a while ago to the Firefox maintainer (Justin Pryzby). As this is very technical, I suggest you discuss this issue with him. I can only tell you what happens, not why it happens.
The easiest way to solve this problem is stop using XIM in Firefox and Mozilla until I can fix it. Both Firefox and Mozilla supports GTK+ immodule. Are there any reasons not to use GTK+ immodule? 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. By these two ways, you can check uim-xim's behavior from VT, I think. Thanks, -- Masahito Omote([EMAIL PROTECTED]) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
