Re: compose key works in xterm/gimp/firefox/etc, but not in *any* Qt/KDE app
- Date: Tue, 13 May 2008 18:26:33 +0200
- From: Thiago Macieira <thiago@xxxxxxx>
- Subject: Re: compose key works in xterm/gimp/firefox/etc, but not in *any* Qt/KDE app
On Tuesday 13 May 2008 18:00:11 Melchior FRANZ wrote:
> Hi,
>
> could anyone imagine a reason why the compose key would fail
> in any Qt application, e.g. konsole/assistant/scribus etc.,
> while it works in non-Qt apps (started from konsole)?
>
> Qt is configured with -xkb (and configure confirms the viability).
> Compose works correctly in xterm/xedit/firefox/gimp ("a produces ä)[1],
> but in Qt-based apps it just yields "a, both with Qt 3.3.8 and
> Qt 4.4!
>
> I've disabled everything that could, in my imagination, have an
> effect, such as QT_IM_... stuff, but nothing helps.
>
> When running xterm and konsole through strace, I get this:
>
> $ strace -fF -eopen xterm 2>&1|grep ompose
> open("/home/m/.XCompose", O_RDONLY) = 6
> open("/var/cache/libx11/compose/l4_[...]
> open("/home/m/.XCompose", O_RDONLY) = 6
> open("/usr/share/X11/locale/en_US.UTF-8/Compose", O_RDONLY) = 7
> $
> $ strace -fF -eopen konsole 2>&1|grep ompose
> $
>
> So konsole doesn't even pretend to be interested in composing.
> What could cause that?
Like I told you on IRC, it must be something local.
Qt 3.3.8:
$ strace -fF -eopen konsole 2>&1|grep ompose
open("/home/tmacieir/.XCompose", O_RDONLY) = -1 ENOENT (No such file or
directory)
open("/usr/share/X11/locale/compose.dir", O_RDONLY) = 12
open("/usr/share/X11/locale/pt_BR.UTF-8/Compose", O_RDONLY) = 12
open("/home/tmacieir/.XCompose", O_RDONLY) = -1 ENOENT (No such file or
directory)
open("/usr/share/X11/locale/compose.dir", O_RDONLY) = 12
open("/usr/share/X11/locale/pt_BR.UTF-8/Compose", O_RDONLY) = 12
Qt 4.4.0/4.4.1:
$ strace -fF -eopen ~/KDE4/bin/konsole 2>&1|grep ompose
[pid 25223] open("/home/tmacieir/.XCompose", O_RDONLY) = -1 ENOENT (No such
file or directory)
[pid 25223] open("/usr/share/X11/locale/compose.dir", O_RDONLY) = 17
[pid 25223] open("/usr/share/X11/locale/pt_BR.UTF-8/Compose", O_RDONLY) = 17
[pid 25223] open("/home/tmacieir/.XCompose", O_RDONLY) = -1 ENOENT (No such
file or directory)
[pid 25223] open("/usr/share/X11/locale/compose.dir", O_RDONLY) = 17
[pid 25223] open("/usr/share/X11/locale/pt_BR.UTF-8/Compose", O_RDONLY) = 17
There are no hits for "Compose" in Qt source code, so it is libX11's doing.
--
Thiago Macieira - thiago (AT) macieira.info - thiago (AT) kde.org
PGP/GPG: 0x6EF45358; fingerprint:
E067 918B B660 DBD1 105C 966C 33F5 F005 6EF4 5358
Attachment:
signature.asc
Description: This is a digitally signed message part.
>> Visit http://mail.kde.org/mailman/listinfo/kde-devel#unsub to unsubscribe <<
- Follow-Ups:
- Re: compose key works in xterm/gimp/firefox/etc, but not in *any* Qt/KDE app
- From: Melchior FRANZ
- Re: compose key works in xterm/gimp/firefox/etc, but not in *any* Qt/KDE app
- References:
- compose key works in xterm/gimp/firefox/etc, but not in *any* Qt/KDE app
- From: Melchior FRANZ
- compose key works in xterm/gimp/firefox/etc, but not in *any* Qt/KDE app
- Prev by Date: compose key works in xterm/gimp/firefox/etc, but not in *any* Qt/KDE app
- Next by Date: Re: compose key works in xterm/gimp/firefox/etc, but not in *any* Qt/KDE app
- Previous by thread: compose key works in xterm/gimp/firefox/etc, but not in *any* Qt/KDE app
- Next by thread: Re: compose key works in xterm/gimp/firefox/etc, but not in *any* Qt/KDE app
- Index(es):