Re: Control key problem

[Halestino Pimentel <halestino@ipb.pt>]

Em Segunda 26 Dezembro 2005 15:28, o André Wöbbeking escreveu:
> On Monday 26 December 2005 12:50, Halestino Pimentel wrote:
> > Hi all,
> >
> > I have a HP Pavilion DV4285EA laptop and I'm with a problem: when KDE
> > starts, my left control key acts strange. For example:
> > - the left CONTROL key don't react to a CONTROL+C;
> > - in Konsole, to open a new command line, if I issue, in order,
> > (left)CONTROL+ALT+N nothing happens, but if I issue, in order,
> > ALT+(left)CONTROL+N, a new command line is open;
> > With the right CONTROL key, there isn't any problem.
> > This problem only occurs in KDE, since in tty1-6 the all CONTROL keys
> > work 100%.
> > The keyboard model configured in Control Center is Pc with 105 keys
> > (Intl) generic and the keyboard map is pt. I tried other models and
> > the probem persists.
>
> Did you configure any XKB options in control center? You can also run
> xev to see which key code is generated by your CONTROL key.
>
>
> Cheers,
> André

Hi André,

Thanks for your answer. XKB options in control center are not configured.
Running xev I've got the following output:

- For my right control key (which works fine):

KeyPress event, serial 31, synthetic NO, window 0x4200001,
    root 0x46, subw 0x0, time 20056922, (70,-13), root:(530,238),
    state 0x0, keycode 109 (keysym 0xffe4, Control_R), same_screen YES,
    XLookupString gives 0 bytes:
    XmbLookupString gives 0 bytes:
    XFilterEvent returns: False

KeyRelease event, serial 31, synthetic NO, window 0x4200001,
    root 0x46, subw 0x0, time 20056976, (70,-13), root:(530,238),
    state 0x4, keycode 109 (keysym 0xffe4, Control_R), same_screen YES,
    XLookupString gives 0 bytes:

- For my left control key (the problematic key):

FocusOut event, serial 31, synthetic NO, window 0x4200001,
    mode NotifyGrab, detail NotifyAncestor

FocusIn event, serial 31, synthetic NO, window 0x4200001,
    mode NotifyUngrab, detail NotifyAncestor

KeymapNotify event, serial 31, synthetic NO, window 0x0,
    keys:  2   0   0   0   0   0   0   0   0   0   0   0   0   0   0   0
           0   0   0   0   0   0   0   0   0   0   0   0   0   0   0   0

Kind of strange, hã?
Seems like the behaviour of a mouse...
Can you interpret this result?