After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 521197 - Numeric keypad no longer works after upgrade
Numeric keypad no longer works after upgrade
Product: gnome-settings-daemon
Classification: Core
Component: plugins
Other Linux
: Normal normal
: ---
Assigned To: gnome-settings-daemon-maint
Depends on:
Reported: 2008-03-08 15:26 UTC by Sebastien Bacher
Modified: 2008-04-01 15:35 UTC
See Also:
GNOME target: ---
GNOME version: 2.21/2.22

Description Sebastien Bacher 2008-03-08 15:26:28 UTC
The bug has been opened on

"I have standard ps2 keyboard and ps2-to-usb adapter. Numeric keys section stopped to work after updating to hardy. Num Lock on or off doesn't help. The numeric keys above letters work ok.

I just noticed that my numeric keys work as a mouse, I can move the cursor with keyboard..

I haven't selected assisteve technologies in gnome-at-properties. Why it was set to on by default??"
Comment 1 Jens Granseuer 2008-03-08 15:39:40 UTC
Mouse keys is off by default. It can be activated using the standard X shortcut Alt + LShift + NumLock which is possibly what happened here, and there's no way for us to diable that. Doesn't sound like a bug at all.
Comment 2 Sebastien Bacher 2008-03-08 16:10:29 UTC
there is a bug somewhere, I noticed the same issue on several installations after upgrading from gnome-control-center 2.20 to 2.21 this cycle, those were working before restarting the session and not after the upgrade
Comment 3 Jens Granseuer 2008-03-08 16:46:44 UTC
After upgrading g-c-c? If it's just that mousekeys is suddenly enabled after the upgrade, I don't see where g-c-c comes into it. g-c-c isn't even running in a normal session. g-s-d maybe, but g-c-c?
Comment 4 Sebastien Bacher 2008-03-08 20:23:49 UTC
you can reassigning to g-s-d, not sure which one has the issue
Comment 5 Sebastien Bacher 2008-03-08 20:24:57 UTC
the description might not have been clear but the bug was there after updating from 2.20 g-c-c to the new g-c-c and g-s-d splitted versions so it might be due one or the other
Comment 6 Sebastien Bacher 2008-03-08 20:25:35 UTC
reassigning to g-s-d
Comment 7 Jens Granseuer 2008-03-28 17:15:01 UTC
Sounds like it could be related to