Bug 189822

Summary: keyboard settings module is missing
Product: [Applications] systemsettings Reporter: Paul Pogonyshev <pogonyshev>
Component: generalAssignee: Unassigned bugs mailing-list <unassigned-bugs>
Status: RESOLVED DUPLICATE    
Severity: normal CC: andresbajotierra, echidnaman, wrightc
Priority: NOR    
Version: unspecified   
Target Milestone: ---   
Platform: Debian testing   
OS: Linux   
Latest Commit: Version Fixed In:

Description Paul Pogonyshev 2009-04-16 19:14:52 UTC
Version:            (using KDE 4.2.2)
OS:                Linux
Installed from:    Debian testing/unstable Packages

After upgrading from 4.2.0 (as I recall) to 4.2.2, keyboard configuration module is gone and the keyboard repeat rate and repeat delay are reset from my custom preferences to some standard value.  'Keyboard & Mouse' category now contains these items:

* Mouse
* Joystick
* Standard Keyboard Shortcuts
* Global Keyboard Shortcuts

None allows me to adjust keyboard repeat rate and delay.

Maybe something went wrong during the update.  Debian also fired up its own helper to migrate settings from ~/.kde4 to ~/.kde.

For me this is a huge annoyance (up to a point of switching to GNOME, hopefully not for long), because I use keyboard a lot.
Comment 1 Christopher B. Wright 2009-04-17 07:08:28 UTC
I have noticed this as well. I don't use the keyboard settings often but I would like to be able to automatically activate num lock at the start of my KDE session.
Comment 2 Dario Andres 2009-04-17 17:12:02 UTC
This seems to be a packaging issue.
Could you try reinstalling your KDE packages? Are they up to date?
You can try with the shell command "kcmshell4 keyboard", this should bring the Keyboard settings (without the whole SystemSettings). If it doesn't work, then the Keyboard configuration module is not present (it was not compiled or not properly packaged/installed)
Thanks
Comment 3 Christopher B. Wright 2009-04-17 17:39:04 UTC
"kcmshell4 keyboard" did nothing. However, I didn't consider that this might be a Kubuntu packaging issue. That makes sense.

... now I need to figure out where to report that. :)
Comment 4 Dario Andres 2009-04-17 17:46:01 UTC
:)
Comment 5 Jonathan Thomas 2009-06-01 21:01:23 UTC

*** This bug has been marked as a duplicate of bug 169710 ***