package 422758 uim
forcemerge 377808 400871 412053 422758
retitle 377808 uim crashing depends on .xinput.d
fixed 377808 1:1.3.1-1
thanks
--
Regards,
dai
GPG Fingerprint = 0B29 D88E 42E6 B765 B8D8 EA50 7839 619D D439 668E
signature.asc
Description: Digital signature
reassign 422758 uim
forcemerge 377808 400871 412053 422758
tags 377808 fixed-in-experimental
thanks
sorry for my mistake.
--
Regards,
dai
GPG Fingerprint = 0B29 D88E 42E6 B765 B8D8 EA50 7839 619D D439 668E
signature.asc
Description: Digital signature
Package: uim
Version: 1:1.2.1-9
Followup-For: Bug #377808
Greetings maintainers, developpers, and bug victims :)
I suffered from this bug on a freshly installed Etch system, with
symptoms in iceweasel and nautilus:
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=412053
http://bugs.debian.org
This bug can be closed as it does not occur anymore in uim 1.2,
provided QT_IM_MODULE and GTK_IM_MODULE are set to uim.
The present version of im-switch still sets them both to xim,
however.
Regards, Jan
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble?
On 7/18/06, Jan Willem Stumpel [EMAIL PROTECTED] wrote:
Etsushi Kato wrote:
On 7/18/06, Etsushi Kato [EMAIL PROTECTED] wrote:
I committed the changes for gtk+ and Qt immodule on
freedesktop's svn repository while ago. Now you can use all
compose sequences and ~/.XCompose with gtk+
Etsushi Kato wrote:
On 7/18/06, Etsushi Kato [EMAIL PROTECTED] wrote:
I committed the changes for gtk+ and Qt immodule on
freedesktop's svn repository while ago. Now you can use all
compose sequences and ~/.XCompose with gtk+ (Mozilla, Firefox,
Thunderbird, Gedit and so on) and Qt (Kate,
On 7/16/06, Jan Willem Stumpel [EMAIL PROTECTED] wrote:
I'm one of the developer of uim. As far as I can tell, you can
avoid this complete freeze of X by using --async option of
uim-xim.
Thank you!!! This indeed works. In Debian Sid, I set
XIM_ARGS=--async in
Etsushi Kato wrote:
Hmm... It it known that --async option has a side effect (and
also SCIM's x11 has) in inputting characters into Tck/Tk
widget.
This is true, unfortunately; I installed tkpaint and no input was
possible. In fact X froze. I had to go to the console to kill
tkpaint. Tcl/tk
On 7/17/06, Jan Willem Stumpel [EMAIL PROTECTED] wrote:
Two reasons:
1 - the compose sequences. [..]
2 - xim always works. [..]
I see. For 1, I've implemented X11's equivalent compose
mechanism in uim-xim, so it should work as if it doesn't exist
:).
Yes; uim-xim apparently uses the
On 7/18/06, Etsushi Kato [EMAIL PROTECTED] wrote:
4) uim - implement X's equivalent compose mechanism in uim's
gtk+ immodule and Qt immodule. It is fairly easy since
we already have it in uim-xim. And I just tested to port this
in uim's
Etsushi Kato wrote:
I'm one of the developer of uim. As far as I can tell, you can
avoid this complete freeze of X by using --async option of
uim-xim.
Thank you!!! This indeed works. In Debian Sid, I set
XIM_ARGS=--async, and indeed it works now exactly as you said: CPU
usage goes to 100%
(Sorry, hit the send button too soon)
Etsushi Kato wrote:
I'm one of the developer of uim. As far as I can tell, you can
avoid this complete freeze of X by using --async option of
uim-xim.
Thank you!!! This indeed works. In Debian Sid, I set
XIM_ARGS=--async in
Hi,
I'm one of the developer of uim. As far as I can tell, you can avoid
this complete freeze of
X by using --async option of uim-xim.
I think this bug is caused from invalid use of filter key event in
mozilla in the address bar widget. Even if you use uim-xim --async
(or maybe SCIM's x11
Package: uim
Version: 1:1.1.0-1.2 (also earlier versions)
Severity: important
See bug 366390. When uim is running (in 'direct' input mode) mis-hitting
keys causes Mozilla and Firefox to crash, freezing the entire X. Fortunately
X still responds to control-alt-Fn, so it is possible to go to a VT
tags 377808 moreinfo
tags 377808 unreproducible
severity 377808 normal
thanks
2006/7/11, Jan Willem Stumpel [EMAIL PROTECTED]:
Mozilla/Firefox do not do this when uim is not running.
Probably this bug comes from uim. But I cannot reproduce.
See bug 366390. When uim is running (in 'direct'
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).
First, list up your environment variables. I cannot find out
which method - XIM or GTK+
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
Masahito Omote wrote:
Hi.
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.
OK. At the moment I am in X (icewm) and have uim running (test: 世
界に今日は, or
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
19 matches
Mail list logo