unable to lock screen with ctrl - alt - L if numlock is on

[Henk Jan Agteresch]

Locking screen with Ctrl - Alt - L does not work when Numlock is on. Tested on Hardy.

Reproduce

Verify Numlock is on
Hit Ctrl - Alt - L.
Nothing happens

Switch Numlock off
Hit Ctrl - Alt - L
Screen locks.

[Namhyung Kim (namhyung)]

Thank you for taking the time to report this bug and helping to make Ubuntu better. Please answer these questions:

* What kind of keyboard you are using?
* Can you check the keycode of 'L' key in both case of Numlock?
 (you can see the keycode of specific key using 'xev' utility)

This will help us to find and resolve the problem.

[Henk Jan Agteresch (hjagteresch)]

I'm using a Microsoft Natural Ergonomic Keyboard 4000. A coworker of mine has the same issue on a general Keytronic keyboard.

Starting with Numlock = on

KeyPress event, serial 27, synthetic NO, window 0x3800001,
    root 0xc2, subw 0x0, time 289153626, (721,14), root:(725,63),
    state 0x10, keycode 46 (keysym 0x6c, l), same_screen YES,
    XLookupString gives 1 bytes: (6c) "l"
    XmbLookupString gives 1 bytes: (6c) "l"
    XFilterEvent returns: False

KeyRelease event, serial 30, synthetic NO, window 0x3800001,
    root 0xc2, subw 0x0, time 289153746, (721,14), root:(725,63),
    state 0x10, keycode 46 (keysym 0x6c, l), same_screen YES,
    XLookupString gives 1 bytes: (6c) "l"
    XFilterEvent returns: False

Switch Numlock off

KeyPress event, serial 30, synthetic NO, window 0x3800001,
    root 0xc2, subw 0x0, time 289156002, (721,14), root:(725,63),
    state 0x10, keycode 77 (keysym 0xff7f, Num_Lock), same_screen YES,
    XLookupString gives 0 bytes:
    XmbLookupString gives 0 bytes:
    XFilterEvent returns: False

PropertyNotify event, serial 30, synthetic NO, window 0x3800001,
    atom 0x11a (XKLAVIER_STATE), time 289156012, state PropertyNewValue

KeyRelease event, serial 30, synthetic NO, window 0x3800001,
    root 0xc2, subw 0x0, time 289156106, (721,14), root:(725,63),
    state 0x10, keycode 77 (keysym 0xff7f, Num_Lock), same_screen YES,
    XLookupString gives 0 bytes:
    XFilterEvent returns: False

Try l with Numlock = off

KeyPress event, serial 30, synthetic NO, window 0x3800001,
    root 0xc2, subw 0x0, time 289157953, (721,14), root:(725,63),
    state 0x0, keycode 46 (keysym 0x6c, l), same_screen YES,
    XLookupString gives 1 bytes: (6c) "l"
    XmbLookupString gives 1 bytes: (6c) "l"
    XFilterEvent returns: False

KeyRelease event, serial 30, synthetic NO, window 0x3800001,
    root 0xc2, subw 0x0, time 289158065, (721,14), root:(725,63),
    state 0x0, keycode 46 (keysym 0x6c, l), same_screen YES,
    XLookupString gives 1 bytes: (6c) "l"
    XFilterEvent returns: False

[Namhyung Kim (namhyung)]

Commited.

[Henk Jan Agteresch (hjagteresch)]

Problem seems to be fixed in current hardy. Locking screen with CTRL-ALT-L works both with Numlock on and off

[Filofel (filofel)]

Hi,

I see just ran the same problem after upgrading from GG to HH (Actual 8.04 release):
Ctrl-Alt-L stopped working.
It is config'd as a keyboard shortcut for Lock Screen but doesn't work.
I tried defining it again, but it didn't work better any after that.
I'm using an an original MS Natural Keyboard, AZERTY (French/France) keymap.

xev:

KeyPress event, serial 27, synthetic NO, window 0x7600001,
    root 0x61, subw 0x0, time 8735982, (-454,-162), root:(1851,322),
    state 0x0, keycode 64 (keysym 0xffe9, Alt_L), same_screen YES,
    XLookupString gives 0 bytes:
    XmbLookupString gives 0 bytes:
    XFilterEvent returns: False

KeyPress event, serial 30, synthetic NO, window 0x7600001,
    root 0x61, subw 0x0, time 8736106, (-454,-162), root:(1851,322),
    state 0x8, keycode 37 (keysym 0xffe3, Control_L), same_screen YES,
    XLookupString gives 0 bytes:
    XmbLookupString gives 0 bytes:
    XFilterEvent returns: False

FocusOut event, serial 30, synthetic NO, window 0x7600001,
    mode NotifyGrab, detail NotifyAncestor

FocusIn event, serial 30, synthetic NO, window 0x7600001,
    mode NotifyUngrab, detail NotifyAncestor

KeymapNotify event, serial 30, synthetic NO, window 0x0,
    keys: 4294967213 0 0 0 32 64 0 0 1 0 0 0 0 0 0 0
           0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0

KeyRelease event, serial 30, synthetic NO, window 0x7600001,
    root 0x61, subw 0x0, time 8736916, (-454,-162), root:(1851,322),
    state 0xc, keycode 46 (keysym 0x6c, l), same_screen YES,
    XLookupString gives 1 bytes: (0c) "
                                       "
    XFilterEvent returns: False

KeyRelease event, serial 30, synthetic NO, window 0x7600001,
    root 0x61, subw 0x0, time 8737109, (-454,-162), root:(1851,322),
    state 0xc, keycode 64 (keysym 0xffe9, Alt_L), same_screen YES,
    XLookupString gives 0 bytes:
    XFilterEvent returns: False

KeyRelease event, serial 30, synthetic NO, window 0x7600001,
    root 0x61, subw 0x0, time 8737159, (-454,-162), root:(1851,322),
    state 0x4, keycode 37 (keysym 0xffe3, Control_L), same_screen YES,
    XLookupString gives 0 bytes:
    XFilterEvent returns: False

FocusOut event, serial 30, synthetic NO, window 0x7600001,
    mode NotifyNormal, detail NotifyNonlinear

[Stefan Verstege (sversteg)]

I got the same problem here.. Somewhere in the process to 8.04 lts it stopped working..

KeymapNotify event, serial 31, synthetic NO, window 0x0,
    keys: 4294967206 0 0 0 32 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

FocusOut event, serial 31, synthetic NO, window 0x4000001,
    mode NotifyUngrab, detail NotifyPointer

FocusIn event, serial 31, synthetic NO, window 0x4000001,
    mode NotifyGrab, detail NotifyPointer

KeymapNotify event, serial 31, synthetic NO, window 0x0,
    keys: 1 0 0 0 32 64 0 0 1 0 0 0 0 0 0 0
           0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0

[ces (goodmorning-no)]

After a bout of updates, I started experiencing this problem in Hardy. Before Ctrl+ALt_L worked fine; now it doesn't work whether numlock is on or not.

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

KeyPress event, serial 31, synthetic NO, window 0x2400001,
    root 0x1a6, subw 0x0, time 4232555, (165,-12), root:(168,36),
    state 0x4, keycode 64 (keysym 0xffe9, Alt_L), same_screen YES,
    XLookupString gives 0 bytes:
    XmbLookupString gives 0 bytes:
    XFilterEvent returns: False

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

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

KeymapNotify event, serial 31, synthetic NO, window 0x0,
    keys: 0 0 0 0 32 64 0 0 1 0 0 0 0 0 0 0
           0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0

KeyRelease event, serial 31, synthetic NO, window 0x2400001,
    root 0x1a6, subw 0x0, time 4232819, (165,-12), root:(168,36),
    state 0xc, keycode 46 (keysym 0x6c, l), same_screen YES,
    XLookupString gives 1 bytes: (0c) "
                                       "
    XFilterEvent returns: False

KeyRelease event, serial 31, synthetic NO, window 0x2400001,
    root 0x1a6, subw 0x0, time 4232843, (165,-12), root:(168,36),
    state 0xc, keycode 37 (keysym 0xffe3, Control_L), same_screen YES,
    XLookupString gives 0 bytes:
    XFilterEvent returns: False

KeyRelease event, serial 31, synthetic NO, window 0x2400001,
    root 0x1a6, subw 0x0, time 4232843, (165,-12), root:(168,36),
    state 0x8, keycode 64 (keysym 0xffe9, Alt_L), same_screen YES,
    XLookupString gives 0 bytes:
    XFilterEvent returns: False

[ces (goodmorning-no)]

Oops, apparently the reason my screen wouldn't lock was because the option "Show position of pointer when Control Key is pressed" in the Mouse Preferences was ticked. Unticking this option solved the problem.

On a related note, should a new bug be opened for this (that keyboard shortcuts don't work properly when this option is ticked)?

[anarki13 (anarki13)]

Problem still exists in Intrepid. solved by unticking "Show Position of Pointer when Control Key is pressed" in mouse preferences.

Help? Anyone?

[Ralph Corderoy (ralph-inputplus)]

Does https://bugzilla.gnome.org/show_bug.cgi?id=125618 explain the behaviour?

[smokydig (smokydig)]

I had the same problem and apparently the FF browser updated a shortcut on one of their commands to ctrl+L so if the browser is focused the focused window takes the command over Ubuntu i went into keyboard shortcuts and reassigned the alt+ ctrl+L and it works no matter if the browser is in focus or not YAY