Mouse Keys enabled/enables during session when setting shows disabled
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
gnome-control-center (Ubuntu) |
New
|
Undecided
|
Unassigned |
Bug Description
After starting a session, the numpad behaves as if Mouse Keys is enabled. Going to Settings > Universal Access > Mouse Keys shows that the feature is disabled. To disable Mouse Keys, the setting must be enabled first, then disabled. Alternatively, the following commands must be used in terminal:
gsettings set org.gnome.
gsettings set org.gnome.
These settings will only persist for the session. It has been observed that the function seemingly enables itself during a session, with no known trigger. At the same time, the num lock or shift + num lock hotkey does not function. Whether that is a separate bug is another story, but neither key combination results in the accidental or purposeful activation or deactivation of Mouse Keys.
Problem observed in Ubuntu 18.04. gsettings-
Current temporary workaround is to add the two commands above into a script to run on startup. This does not solve inadvertent activations later on, however.
EDIT: Mouse Keys observed to enable itself when I type "xset led on" into terminal to enable keyboard backlight.
ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: gnome-control-
ProcVersionSign
Uname: Linux 4.15.0-20-generic x86_64
NonfreeKernelMo
ApportVersion: 2.20.9-0ubuntu7
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Mon Apr 30 06:36:09 2018
ExecutablePath: /usr/bin/
InstallationDate: Installed on 2018-04-28 (1 days ago)
InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
SourcePackage: gnome-control-
UpgradeStatus: No upgrade log present (probably fresh install)
description: | updated |
Looks like this bug goes all the way back to 8.04, reading the later comments in the following bug report:
https:/ /bugs.launchpad .net/ubuntu/ +source/ gnome-control- center/ +bug/197589
Comment 34 onwards.