[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#544646: console-setup: ~/.XCompose file ignored



Hello, I bumped into an X error, so I got to restart X after copying it from my other machine... Luckily?
Anyway, here's the output.

KeyPress event, serial 31, synthetic NO, window 0x1800001,
    root 0x107, subw 0x0, time 1380796236, (1918,733), root:(1919,734),
    state 0x0, keycode 105 (keysym 0xff20, Multi_key), same_screen YES,
    XLookupString gives 0 bytes: 
    XmbLookupString gives 0 bytes: 
    XFilterEvent returns: True

KeyRelease event, serial 31, synthetic NO, window 0x1800001,
    root 0x107, subw 0x0, time 1380796397, (1918,733), root:(1919,734),
    state 0x0, keycode 105 (keysym 0xff20, Multi_key), same_screen YES,
    XLookupString gives 0 bytes: 
    XFilterEvent returns: False

KeyPress event, serial 31, synthetic NO, window 0x1800001,
    root 0x107, subw 0x0, time 1380797248, (1918,733), root:(1919,734),
    state 0x0, keycode 21 (keysym 0x3d, equal), same_screen YES,
    XLookupString gives 1 bytes: (3d) "="
    XmbLookupString gives 1 bytes: (3d) "="
    XFilterEvent returns: True

KeyRelease event, serial 31, synthetic NO, window 0x1800001,
    root 0x107, subw 0x0, time 1380797376, (1918,733), root:(1919,734),
    state 0x0, keycode 21 (keysym 0x3d, equal), same_screen YES,
    XLookupString gives 1 bytes: (3d) "="
    XFilterEvent returns: False

KeyPress event, serial 31, synthetic NO, window 0x1800001,
    root 0x107, subw 0x0, time 1380797966, (1918,733), root:(1919,734),
    state 0x0, keycode 61 (keysym 0x2f, slash), same_screen YES,
    XLookupString gives 1 bytes: (2f) "/"
    XmbLookupString gives 1 bytes: (2f) "/"
    XFilterEvent returns: True

KeyPress event, serial 31, synthetic NO, window 0x1800001,
    root 0x107, subw 0x0, time 1380797966, (1918,733), root:(1919,734),
    state 0x0, keycode 0 (keysym 0x0, NoSymbol), same_screen YES,
    XLookupString gives 0 bytes: 
    XmbLookupString gives 3 bytes: (e2 89 a0) "≠"
    XFilterEvent returns: False

KeyRelease event, serial 31, synthetic NO, window 0x1800001,
    root 0x107, subw 0x0, time 1380798131, (1918,733), root:(1919,734),
    state 0x0, keycode 61 (keysym 0x2f, slash), same_screen YES,
    XLookupString gives 1 bytes: (2f) "/"
    XFilterEvent returns: False

Looks like it's trying to work, but urxvt, emacs(and all other gtk apps), okular(and all other Qt apps)fail to recognise the character. Only the standard ones work.
On one machine I even tried editing the master compose file, and restarting X. Fail.
dpkg-reconfigure console setup (blah blah) fail.
reboot, fail.

This box is clean, just letting you know what's been (unwisely, perhaps) tried in the past.
I've tried using uim and such, I believe as laid out here:
http://old.nabble.com/Compose-key-ignored-td9119688.html
but I can't be sure, as it's been a while.
I'm quite adjusted to scim for Japanese input, so a change to uim would be awkward at best, and what I've read tells me that it would probably drive me back to where I am even if it worked.
I don't think this is a gtk issue, nor that every toolkit is ignoring it. If it's scim/xim blocking things, that's... awkward.

my .xinitrc, just in case:

#!/bin/bash
#
# ~/.xinitrc
export LC_CTYPE=ja_JP.utf8 

 
xsetroot -cursor_name left_ptr -solid black &


export MOZILLA_NO_JEMALLOC=0

#X CPU usage workaround -_-...
export MOZ_DISABLE_PANGO=1

export XMODIFIERS="@im=SCIM"
export GTK_IM_MODULE=xim
export QT_IM_MODULE=xim
scim -d  

xmodmap ~/.xmodmap-siduxbox &
sleep 1
xmodmap ~/.xmodmap-siduxbox &
 
export EDITOR=emacsclient
stumpwm

Thanks for the help.
At Thu, 12 Nov 2009 10:08:25 +0100,
Julien Cristau wrote:
> 
> On Tue, Sep  1, 2009 at 23:27:42 -0500, TheGZeus wrote:
> 
> > none of these key combos work for me, and everything before the Russian entries work on an Arch installation.
> > I have restarted X, as well as rebooted my computer.
> > They still have no effect.
> > I saw a bug related to GTK+,.XCompose and xim, but this is a problem in all apps, regardless of toolkit.
> > not sure where to go from here.
> > 
> can you run xev, press one of those combinations, and send the output to
> this bug?  gtk uses its own input method by default so any changes to
> .XCompose wouldn't show up there, but xev uses plain Xlib.
> 
> Cheers,
> Julien




Reply to: