Num lock works in reverse on Ubuntu 19.10 wayland

Bug #1846249 reported by Bickhaus
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
gnome-settings-daemon (Ubuntu)
Fix Released
Undecided
Unassigned

Bug Description

I updated to the Ubuntu 19.10 beta yesterday, and since updating, the num lock key on my keyboard (DASKeyboard Prime 13 from System76) is reversed. When it is on (indicator light is lit), the numbers do not work, but the arrows, page up/down, home, end keys, etc. work. When it is off, the numbers work and the arrows, etc. are disabled. Viewing the image of my keyboard layout (English US) in the Regions and Language section of GNOME settings shows Num Lock lit up when it is not lit on the keyboard and vice versa.

I use the Wayland session, and this issue was not present prior to upgrading (I originally installed 18.10 and then upgraded to 19.04.). It is not present if I use another keyboard (I booted with a LITE-ON SK-9020 which uses USB like the DASKeyboard.). It is not present while using the DASKeyboard, if I log into an X session, rather than Wayland. I also tried changing the keyboard language, deleting the English (US) language and then switching back (so I am now back on the English (US) layout). That did not work.

I ran the commands specified on the Ubuntu Wiki's debuggingKeyboardDetection page. The output of lsusb -v is attached as an attachment. I do not have gconftool-2 installed, so I did not run that. The output of xprop -root | grep XKB > ~/xk is:

_XKB_RULES_NAMES(STRING) = "evdev", "pc105", "us", "", ""

ProblemType: Bug
DistroRelease: Ubuntu 19.10
Package: x11-utils 7.7+4build1
ProcVersionSignature: Ubuntu 5.3.0-13.14-generic 5.3.0
Uname: Linux 5.3.0-13-generic x86_64
ApportVersion: 2.20.11-0ubuntu7
Architecture: amd64
BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Tue Oct 1 11:17:31 2019
DistUpgraded: 2019-09-30 20:21:51,653 DEBUG Running PostInstallScript: './xorg_fix_proprietary.py'
DistroCodename: eoan
DistroVariant: ubuntu
DkmsStatus: virtualbox, 6.0.12, 5.3.0-13-generic, x86_64: installed
GraphicsCard:
 Advanced Micro Devices, Inc. [AMD/ATI] Ellesmere [Radeon RX 470/480/570/570X/580/580X/590] [1002:67df] (rev ef) (prog-if 00 [VGA controller])
   Subsystem: Tul Corporation / PowerColor Ellesmere [Radeon RX 470/480/570/570X/580/580X/590] [148c:2379]
InstallationDate: Installed on 2019-03-19 (195 days ago)
InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3)
MachineType: System manufacturer System Product Name
ProcEnviron:
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=<set>
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-13-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7
SourcePackage: x11-utils
UpgradeStatus: Upgraded to eoan on 2019-10-01 (0 days ago)
dmi.bios.date: 09/12/2019
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 1820
dmi.board.asset.tag: Default string
dmi.board.name: PRIME B450-PLUS
dmi.board.vendor: ASUSTeK COMPUTER INC.
dmi.board.version: Rev X.0x
dmi.chassis.asset.tag: Default string
dmi.chassis.type: 3
dmi.chassis.vendor: Default string
dmi.chassis.version: Default string
dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1820:bd09/12/2019:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnPRIMEB450-PLUS:rvrRevX.0x:cvnDefaultstring:ct3:cvrDefaultstring:
dmi.product.family: To be filled by O.E.M.
dmi.product.name: System Product Name
dmi.product.sku: SKU
dmi.product.version: System Version
dmi.sys.vendor: System manufacturer
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.99-1ubuntu1
version.libgl1-mesa-dri: libgl1-mesa-dri 19.1.6-1ubuntu1
version.libgl1-mesa-glx: libgl1-mesa-glx N/A
version.xserver-xorg-core: xserver-xorg-core 2:1.20.5+git20190820-0ubuntu3
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.1-1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20190815-1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

Revision history for this message
Bickhaus (bickhaus) wrote :
Revision history for this message
Bickhaus (bickhaus) wrote :

I have also noticed that the num lock button seems to sync properly IF num lock is off at boot. If I turn num lock after boot, then the key and indicator light function the way i expect (light on == numbers; light off == arrows, etc). If num lock is on at boot, then the indicator light and key are reversed (light on == arrows, etc; light off == numbers).

Revision history for this message
Bickhaus (bickhaus) wrote :

When I am logged into Wayland (and therefore experiencing the issue, the output of gsettings list-recursively | grep -e numlock is this when the numlock led is off but the numbers work anyway:

org.gnome.desktop.peripherals.keyboard remember-numlock-state true
org.gnome.desktop.peripherals.keyboard numlock-state false

When the numlock led is on, but the numbers don't work:

org.gnome.desktop.peripherals.keyboard remember-numlock-state true
org.gnome.desktop.peripherals.keyboard numlock-state true

Revision history for this message
Bickhaus (bickhaus) wrote :

When I am logged into an X session (and therefore not experiencing the issue), the output of gsettings list-recursively | grep -e numlock is this when the numlock led is off and the numbers don't work:

org.gnome.desktop.peripherals.keyboard remember-numlock-state true
org.gnome.desktop.peripherals.keyboard numlock-state false

When numlock is on and the numbers work:

org.gnome.desktop.peripherals.keyboard remember-numlock-state true
org.gnome.desktop.peripherals.keyboard numlock-state true

Revision history for this message
Bickhaus (bickhaus) wrote :

Essentially, it seems like when logging in under Wayland, the system remembers the status of the numlock LED, BUT it always starts the system with the numlock functionality disabled. This is why the LED is out of sync if it's on when logging on, but not if it's off when logging in.

Bickhaus (bickhaus)
affects: x11-utils (Ubuntu) → gnome-settings-daemon (Ubuntu)
Bickhaus (bickhaus)
Changed in gnome-settings-daemon (Ubuntu):
status: New → Fix Released
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.