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

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



On 04-Nov-15 19:38, Zsolt Rizsanyi wrote:
> On Monday 15 November 2004 16.38, Gabor Nagy wrote:
> > Recently I have noticed that AltGr does not work anymore in the
> > Hungarian layout.
> 
> I have KDE 3.2 from testing and the Alt-Gr works without problem for me 
> with the hungarian keyboard (using the hu_querty layout).
> So I think your problem is not related to KDE. Can you test this on the 
> linux console? Does Alt-Gr work there?

It is clearly not layout related, as the French layout has the same
problem.

In the console it works.

> If you create a new user does Alt-Gr work for him.

My wife experiences the same problem.

> 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.

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?)

KeyPress event, serial 28, synthetic NO, window 0x2600001,
    root 0x40, subw 0x0, time 8059540, (170,2), root:(1012,24),
    state 0x0, keycode 64 (keysym 0xffe9, Alt_L), same_screen YES,
    XLookupString gives 0 bytes:  ""

KeyPress event, serial 28, synthetic NO, window 0x2600001,
    root 0x40, subw 0x0, time 8061107, (170,2), root:(1012,24),
    state 0x8, keycode 55 (keysym 0x76, v), same_screen YES,
    XLookupString gives 1 bytes:  "v"

KeyRelease event, serial 28, synthetic NO, window 0x2600001,
    root 0x40, subw 0x0, time 8061148, (170,2), root:(1012,24),
    state 0x8, keycode 55 (keysym 0x76, v), same_screen YES,
    XLookupString gives 1 bytes:  "v"

KeyRelease event, serial 28, synthetic NO, window 0x2600001,
    root 0x40, subw 0x0, time 8061750, (170,2), root:(1012,24),
    state 0x8, keycode 64 (keysym 0xffe9, Alt_L), same_screen YES,
    XLookupString gives 0 bytes:  ""

KeyPress event, serial 28, synthetic NO, window 0x2600001,
    root 0x40, subw 0x0, time 8062870, (170,2), root:(1012,24),
    state 0x0, keycode 113 (keysym 0xffea, Alt_R), same_screen YES,
    XLookupString gives 0 bytes:  ""

KeyPress event, serial 28, synthetic NO, window 0x2600001,
    root 0x40, subw 0x0, time 8063519, (170,2), root:(1012,24),
    state 0x8, keycode 55 (keysym 0x76, v), same_screen YES,
    XLookupString gives 1 bytes:  "v"

KeyRelease event, serial 28, synthetic NO, window 0x2600001,
    root 0x40, subw 0x0, time 8063575, (170,2), root:(1012,24),
    state 0x8, keycode 55 (keysym 0x76, v), same_screen YES,
    XLookupString gives 1 bytes:  "v"

KeyRelease event, serial 28, synthetic NO, window 0x2600001,
    root 0x40, subw 0x0, time 8063939, (170,2), root:(1012,24),
    state 0x8, keycode 113 (keysym 0xffea, Alt_R), same_screen YES,
    XLookupString gives 0 bytes:  ""

Regards,
Gabor



Reply to: