key works in sawfish but does not in icewm

From: Michael J a r o s (e0225848_at_student.tuwien.ac.at)
Date: 09/30/04 

Date: Thu, 30 Sep 2004 17:07:10 GMT

Hi!

I'm having problems with my "Alt Gr" key, which is used to get the third
character on some keys on German keyboards. I have a Debian (woody)
installation with Gnome installed. I use gdm to log in to either the
default sawfish window manager or to ICEWm. The 'Alt Gr' key works in
sawfish (which is slow), but does not work in ICEWm, which I would like to
use in future sessions. In ICEWm, the 'Alt Gr' key gives the primary
character in some combinations like the '<' key and no character at all in
some other combinations like the 'q' key. This behaviur changes after some
time of playing around with the keys (just playing around on the keyboard,
no configuration changes), so that there was no character returned in any
'Alt Gr'-combination.

Here's some info on my system as well as some xev output:

linux 2.6.7 i686
IceWM 1.2.16
sawfish 1.3
XFree86 Version 4.3.0.1
GDM 2.6.0.3

/etc/X11/XF86Config-4:
| Section "InputDevice"
| Identifier "Generic Keyboard"
| Driver "keyboard"
| Option "CoreKeyboard"
| Option "XkbRules" "xfree86"
| Option "XkbModel" "pc104"
| Option "XkbLayout" "de"
| EndSection

xmodmap output in sawfish AND icewm:
|xmodmap: up to 3 keys per modifier, (keycodes in parentheses):
|
|shift Shift_L (0x32), Shift_R (0x3e)
|lock Caps_Lock (0x42)
|control Control_L (0x25), Control_R (0x6d)
|mod1 Alt_L (0x40), BadKey (0x7d), BadKey (0x9c)
|mod2 Num_Lock (0x4d)
|mod3
|mod4 BadKey (0x7f), BadKey (0x80)
|mod5 Mode_switch (0x5d), ISO_Level3_Shift (0x7c)

xmodmap -pk | grep 94 output in sawfish AND icewm:
      94 0x003c (less) 0x003e (greater) 0x0000
(NoSymbol) 0x0000 (NoSymbol) 0x007c (bar) 0x00a6 (brokenbar)

I tried pressing 'Alt Gr' + '<' which should give the '|' (pipe) character
on my keyboard.

xev output in icewm:
|KeyPress event, serial 28, synthetic NO, window 0x1200001,
| root 0xb0, subw 0x0, time 10240080, (534,333), root:(537,350),
| state 0x0, keycode 113 (keysym 0xfe03, ISO_Level3_Shift), same_screen
YES,
| XLookupString gives 0 bytes: ""
|
|KeyPress event, serial 28, synthetic NO, window 0x1200001,
| root 0xb0, subw 0x0, time 10241043, (534,333), root:(537,350),
| state 0x80, keycode 94 (keysym 0x3c, less), same_screen YES,
| XLookupString gives 1 bytes: "<"
|
|KeyRelease event, serial 28, synthetic NO, window 0x1200001,
| root 0xb0, subw 0x0, time 10241185, (534,333), root:(537,350),
| state 0x80, keycode 94 (keysym 0x3c, less), same_screen YES,
| XLookupString gives 1 bytes: "<"
|
|KeyRelease event, serial 28, synthetic NO, window 0x1200001,
| root 0xb0, subw 0x0, time 10241232, (534,333), root:(537,350),
| state 0x80, keycode 113 (keysym 0xfe03, ISO_Level3_Shift),
same_screen YES,
| XLookupString gives 0 bytes: ""

xev output in sawfish:
|KeyPress event, serial 28, synthetic NO, window 0x2400001,
| root 0xb0, subw 0x0, time 9901926, (539,312), root:(568,374),
| state 0x0, keycode 113 (keysym 0xfe03, ISO_Level3_Shift), same_screen
YES,
| XLookupString gives 0 bytes: ""
|
|KeyPress event, serial 28, synthetic NO, window 0x2400001,
| root 0xb0, subw 0x0, time 9902236, (539,312), root:(568,374),
| state 0x80, keycode 94 (keysym 0x7c, bar), same_screen YES,
| XLookupString gives 1 bytes: "|"
|
|KeyRelease event, serial 28, synthetic NO, window 0x2400001,
| root 0xb0, subw 0x0, time 9902389, (539,312), root:(568,374),
| state 0x80, keycode 94 (keysym 0x7c, bar), same_screen YES,
| XLookupString gives 1 bytes: "|"
|
|KeyRelease event, serial 28, synthetic NO, window 0x2400001,
| root 0xb0, subw 0x0, time 9902523, (539,312), root:(568,374),
| state 0x80, keycode 113 (keysym 0xfe03, ISO_Level3_Shift),
same_screen YES,
| XLookupString gives 0 bytes: ""

It looks like some script modifies xmodmap parameters or something like
that. I do not have enough experience however to isolate the problem. I
hope someone can give me a hint or two.

Regards,
Michael Jaros

Relevant Pages

  • keymapping -> numlock doesnt work anymore
    ... KeyPress event, serial 32, synthetic NO, window 0x3200001, ... XLookupString gives 1 bytes: "j" ... XFilterEvent returns: False ... KeyRelease event, serial 32, synthetic NO, window 0x3200001, ...
    (freebsd-questions)
  • Re: Right ALT key drives me crazy under X
    ... I got this problem too and I solved it configuring my keyboard as pc105. ... KeyPress event, serial 31, synthetic NO, window 0x3600001, ... XLookupString gives 0 bytes: ... KeyRelease event, serial 31, synthetic NO, window 0x3600001, ...
    (Debian-User)
  • Re: lost my menu key
    ... KeyPress event, serial 32, synthetic NO, window 0x1200001, ... XLookupString gives 0 bytes: ... XFilterEvent returns: False ... KeyRelease event, serial 32, synthetic NO, window 0x1200001, ...
    (Debian-User)
  • Right ALT key drives me crazy under X
    ... KeyPress event, serial 31, synthetic NO, window 0x3600001, ... XLookupString gives 0 bytes: ... KeyRelease event, serial 31, synthetic NO, window 0x3600001, ...
    (Debian-User)
  • Re: Couldnt load XKB keymap... Cant switch to terminal mode
    ... and found that Ctrl-Alt-Fx does not work ... What is your xorg keyboard config? ... XLookupString gives 0 bytes: ... KeyRelease event, serial 30, synthetic NO, window 0x1400001, ...
    (Debian-User)