keyboard state scrambled after unlock

Bug #1815730 reported by Andrew Kay
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
numlockx (Ubuntu)
New
Undecided
Unassigned

Bug Description

after locking the screen with ctl-alt-l the keyboard state changes to something strange.

I usually leave the keypad in the non-num-lock mode, so that eg "2" maps to up-arrow (otherwise my keyboard has no dedicated arrow keys, so this is important.)

During lock (eg at the password screen) the num-lock seems to be engaged automatically, and I think 2 maps to 2 again (which isn't a problem.)

However, after unlock "2" maps to something odd, neither "2" nor "up". I have to press num-lock TWICE to get back to my preferred no-num-lock state. This is wrong.

The problem is similar with all the keypad keys, "2" is just an example.

The arrow mode is something built-in to my Quick-fire cooler master cm-storm keyboard, it's not something I hacked myself.
This behaviour appeared after I performed LTS upgrade from Xubuntu 16.04 to Xubuntu 18.04

I'm guessing this is the right package to report, as xscreensaver is not installed, and flock tries first xscreensaver-command and then "light-locker-command --lock"

Description: Ubuntu 18.04.1 LTS
Release: 18.04
light-locker:
  Installed: 1.8.0-1ubuntu1
  Candidate: 1.8.0-1ubuntu1
  Version table:
 *** 1.8.0-1ubuntu1 500
        500 http://gb.archive.ubuntu.com/ubuntu bionic/universe amd64 Packages
        100 /var/lib/dpkg/status

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: light-locker 1.8.0-1ubuntu1
ProcVersionSignature: Ubuntu 4.15.0-45.48-generic 4.15.18
Uname: Linux 4.15.0-45-generic x86_64
ApportVersion: 2.20.9-0ubuntu7.5
Architecture: amd64
CurrentDesktop: XFCE
Date: Wed Feb 13 09:03:48 2019
InstallationDate: Installed on 2016-09-28 (867 days ago)
InstallationMedia: Xubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719)
SourcePackage: light-locker
UpgradeStatus: Upgraded to bionic on 2019-01-14 (30 days ago)

Revision history for this message
Andrew Kay (music1) wrote :
Revision history for this message
Theo Linkspfeifer (lastonestanding) wrote :

Light-locker uses lightdm-gtk-greeter to display the unlock screen. The greeter runs "numlockx" on initialization.

Does temporary removing the following file resolve the issue?

/usr/share/lightdm/lightdm.conf.d/50-xubuntu-numlock.conf

Revision history for this message
Andrew Kay (music1) wrote :

Yes, exactly it. Remove the file, reboot, problem goes away. Replace the file, reboot, problem comes back.

Thanks (and that's my workaround for now.)

affects: light-locker (Ubuntu) → numlockx (Ubuntu)
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.