Summary: | Make enabling NumLock at startup possible in systemsettings | ||
---|---|---|---|
Product: | [Applications] systemsettings | Reporter: | Raphael Kubo da Costa <rakuco> |
Component: | general | Assignee: | Unassigned bugs mailing-list <unassigned-bugs> |
Status: | CLOSED DUPLICATE | ||
Severity: | wishlist | CC: | finex |
Priority: | NOR | ||
Version: | 4.1 | ||
Target Milestone: | --- | ||
Platform: | unspecified | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: | ||
Sentry Crash Report: | |||
Attachments: |
screenshot
screenshot My Keyboard & Mouse window |
Description
Raphael Kubo da Costa
2008-09-22 15:11:46 UTC
It is already available: System settings -> keyboard & mouse -> keyboard -> NumLock on KDE startup I haven't been able to find Keyboard in Keyboard&Mouse in 4.2 or svn trunk for some time anymore. Probably it is an issue on your specific installation because the option is still present on 4.2 and trunk. Created attachment 31119 [details]
screenshot
Created attachment 31120 [details]
screenshot
@Raphael: please, would you like to post a screenshot of your "keyboard & mouse" settings window? You can even try to start the kcm module typing: kcmshell4 keyboard If it doesn't start, it means that you don't have it installed. Created attachment 31126 [details]
My Keyboard & Mouse window
@FiNeX: I've attached my settings window. It looks the same both for trunk and 4.2 (Arch Linux). Typing kcmshell4 keyboard in trunk, I get kcmshell(4195)/kcmshell (kdelibs) locateModule: "keyboard" should not be loaded. In this case, what needs to be done to active/compile the module? It depends from your packager or, if you have compiled kde from trunk, maybe you've not installed all the components. You can ask for a more detailed help on the new kde forum or on IRC channel. I'm using trunk and the problem persists. Initial investigation in the code suggests keyboard.desktop in $KDEDIR/share/kde4/services is loaded as a menu id and not as a desktop file. If I rename it to something like 'foo.desktop' and run kbuildsycoca4 it works fine. Should this bug be reopened or should I file a new bug report? Actually, this bug is in fact bug 169710. Marking as DUPLICATE (don't know if DUPLICATE bugs should be marked as CLOSED or RESOLVED). *** This bug has been marked as a duplicate of bug 169710 *** |