[Bug 916246] New: Number keypad disabled in KDE 4
http://bugzilla.opensuse.org/show_bug.cgi?id=916246 Bug ID: 916246 Summary: Number keypad disabled in KDE 4 Classification: openSUSE Product: openSUSE Distribution Version: 13.2 Hardware: x86-64 OS: openSUSE 13.2 Status: NEW Severity: Major Priority: P5 - None Component: KDE4 Workspace Assignee: kde-maintainers@suse.de Reporter: linux@barrowhillfarm.org.uk QA Contact: qa-bugs@suse.de Found By: --- Blocker: --- At the KDE login screen, I need to press the NumLock key to activate, even though it set to switch on automatically in the BIOS and in KDE System Settings. I can then enter my password using the number keypad. After the KDE Plasma Workspace has loaded, the number keypad is disabled and unresponsive, even after toggling the NumLock key. A Crtl + Alt + F2 terminal accepts input from the number keypad, but on switching back to the graphical interface, the number keypad revets to being inactive. This behaviour is independent of the application being used - it occurs in Konsole, Kate, Kwrite, LibreOffice, and Thunderbird, for example. I have installed XFCE on the same machine, and it does not appear to be affected by this bug. The terminal application accepts and displays input from the number keypad. I'm running an up-to-date, patched version of openSUSE 13.2, x86_64, with nVidia graphics (GeForce 9600) and a Logitech K750 wireless USB keyboard. The same hardware worked with openSUSE 13.1 + KDE4. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=916246
--- Comment #1 from Bob Williams
http://bugzilla.opensuse.org/show_bug.cgi?id=916246
Bob Williams
http://bugzilla.opensuse.org/show_bug.cgi?id=916246
--- Comment #2 from Bob Williams
http://bugzilla.opensuse.org/show_bug.cgi?id=916246
Bob Williams
http://bugzilla.opensuse.org/show_bug.cgi?id=916246
Bob Williams
http://bugzilla.opensuse.org/show_bug.cgi?id=916246
--- Comment #3 from Bob Williams
http://bugzilla.opensuse.org/show_bug.cgi?id=916246
Wolfgang Bauer
Since switching to plasma5/KDE Frameworks 5 this bug has disappeared. With the KF5 desktop, my number keypad functions correctly, suggesting that the bug appeared in a recent version of KDE 4.
Ok, then it's not Severity "Major" and Priority "High" any more I guess? Btw, you're not supposed to set the Priority field anyway. This is for the developers/maintainers to prioritize the bugs they are working on. And I don't think this is a KDE(4) bug at all. It works fine here on several systems. Some notes though: - regarding the login screen: KDM doesn't change the NumLock state at all, unless you explicitely added the "NumLock" option to /usr/share/kde4/config/kdm/kdmrc. And it doesn't respect the user's settings (of course). The settings from /etc/sysconfig/keyboard are evaluated by systemd-vconsole.setup and the NumLock state is set by the general display-manager.service startup script. There has been a bug where this only worked if you manually added /etc/sysconfig/keyboard to the initrd (bug#901916), but that should be fixed (if not, reopen the other bugreport please). But: when you set KBD_NUMLOCK="bios" (which is the default) and turn NumLock on in the BIOS, this only works if the BIOS is actually able to turn it on. On my system this stopped working when I replaced my PS/2 keyboard with an USB one, now NumLock is off on the boot menu although I enabled it in the BIOS. So try setting KBD_NUMLOCK="yes" instead (in /etc/sysconfig/keyboard), this should work in any case and turn it on unconditionally. Regarding KDE4: What have you configured in Systemsettings->Input Devices->Keyboard->NumLock on KDE startup? In the case of "Leave unchanged", the above applies. Try the different settings though, if it is set "Turn Off", KDE4 will turn it off on startup of course. Btw, this setting doesn't work at all in Plasma5 yet. At least it didn't when I last tried. You might also try to change to a different keyboard layout as a test. And try to run "numlockx on" or "numlockx toggle" manually. Does this work? If not, it's definitely no KDE problem. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=916246
--- Comment #5 from Wolfgang Bauer
What have you configured in Systemsettings->Input Devices->Keyboard->NumLock on KDE startup? In the case of "Leave unchanged", the above applies. Try the different settings though, if it is set "Turn Off", KDE4 will turn it off on startup of course.
Btw, this setting doesn't work at all in Plasma5 yet. At least it didn't when I last tried.
PS: this setting actually does work now in Plasma5. It has been fixed for 5.2.1: https://bugs.kde.org/show_bug.cgi?id=339643 Your original problem description sounds a bit like this KDE bugreport though: https://bugs.kde.org/show_bug.cgi?id=329727 So make sure that "use keyboard for mouse-navigation" is turned off. If it's turned on this basically disables the numeric keyboard and makes it move the mouse cursor instead. If that's the problem, it would also explain why it worked after switching to Plasma5. Plasma5 doesn't read this setting from KDE4, and it is of course disabled by default. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=916246
Bob Williams
participants (1)
-
bugzilla_noreply@novell.com