Bug#281398: kde-core: AltGr no longer works

[Rizsanyi Zsolt <rizsanyi@users.sourceforge.net>]

On Tuesday 16 November 2004 15.46, Nagy Gabor wrote:
> On 04-Nov-15 19:38, Zsolt Rizsanyi wrote:
> > If you create a new user does Alt-Gr work for him.
>
> My wife experiences the same problem.

But your wife also has an old configuration, which could have became 
corrupt in the same way is it happened with yours.
Creating a new user is not that big hassle, and you could eliminate some 
possibilities. And you can even try out things more freely.
One thing I would try out is changing the Keyboard Model in the kxkb 
configuration.

> > You should also test booting into Gnome (with the new user) if
> > everything else fails :)
>
> So I don't know exactly if it is X related, or KDE, but my guess is KDE.
> I don't have gnome installed, and I don't know how to identify the
> source of the problem.

You could easily test if it is a KDE problem or not, just start X without 
KDE. Eg. you could start a simple xterm by using
xinit -- :1

You just need to make sure that the Hungarian layout is set in your 
XF86Config

> But since xev returns different codes for left and right alt, I think it
> is the keyboard layout thing's responsibility to know that when after
> ALT_R a v comes, it should produce the @ glyph.
>
> Please have a look at this xev output, and tell me if it is good or not
> (shouldn't state be different for the two alt keys?)

I'm not sure about any of this, but here is what I get from xev when I 
enter the @ sign in Hungarian layout:

KeyPress event, serial 28, synthetic NO, window 0x3c00001,
    root 0x3f, subw 0x0, time 23598848, (-123,709), root:(825,739),
    state 0x0, keycode 113 (keysym 0xff7e, Mode_switch), same_screen YES,
    XLookupString gives 0 bytes:  ""

KeyPress event, serial 28, synthetic NO, window 0x3c00001,
    root 0x3f, subw 0x0, time 23599390, (-123,709), root:(825,739),
    state 0x2000, keycode 55 (keysym 0x40, at), same_screen YES,
    XLookupString gives 1 bytes:  "@"

KeyRelease event, serial 28, synthetic NO, window 0x3c00001,
    root 0x3f, subw 0x0, time 23599491, (-123,709), root:(825,739),
    state 0x2000, keycode 55 (keysym 0x40, at), same_screen YES,
    XLookupString gives 1 bytes:  "@"

KeyRelease event, serial 28, synthetic NO, window 0x3c00001,
    root 0x3f, subw 0x0, time 23599750, (-123,709), root:(825,739),
    state 0x2000, keycode 113 (keysym 0xff7e, Mode_switch), same_screen 
YES,
    XLookupString gives 0 bytes:  ""



In English layout I get this for the same keystrokes:
KeyPress event, serial 29, synthetic NO, window 0x3c00001,
    root 0x3f, subw 0x0, time 23667167, (-252,0), root:(696,30),
    state 0x0, keycode 113 (keysym 0xffea, Alt_R), same_screen YES,
    XLookupString gives 0 bytes:  ""

KeyPress event, serial 29, synthetic NO, window 0x3c00001,
    root 0x3f, subw 0x0, time 23668029, (-252,0), root:(696,30),
    state 0x8, keycode 55 (keysym 0x76, v), same_screen YES,
    XLookupString gives 1 bytes:  "v"

KeyRelease event, serial 29, synthetic NO, window 0x3c00001,
    root 0x3f, subw 0x0, time 23668144, (-252,0), root:(696,30),
    state 0x8, keycode 55 (keysym 0x76, v), same_screen YES,
    XLookupString gives 1 bytes:  "v"

KeyRelease event, serial 29, synthetic NO, window 0x3c00001,
    root 0x3f, subw 0x0, time 23668379, (-252,0), root:(696,30),
    state 0x8, keycode 113 (keysym 0xffea, Alt_R), same_screen YES,
    XLookupString gives 0 bytes:  ""