compose key works in xterm/gimp/firefox/etc, but not in *any* Qt/KDE app
- Date: Tue, 13 May 2008 18:00:11 +0200
- From: Melchior FRANZ <melchior.franz@xxxxxxxxx>
- Subject: compose key works in xterm/gimp/firefox/etc, but not in *any* Qt/KDE app
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?
m.
[1] this didn't work in kmail either. I copied it over from an xterm. :-)
PS: this is with Linux/x86, libc 2.6.1, gcc 4.2.1, qt-copy and KDE
HEAD from the 3.* branch and SVN/HEAD
>> Visit http://mail.kde.org/mailman/listinfo/kde-devel#unsub to unsubscribe <<