Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 35682 - numlockx in GDM
Summary: numlockx in GDM
Status: RESOLVED WONTFIX
Alias: None
Product: Gentoo Linux
Classification: Unclassified
Component: [OLD] GNOME (show other bugs)
Hardware: All Linux
: High enhancement (vote)
Assignee: Gentoo Linux Gnome Desktop Team
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2003-12-12 14:03 UTC by Robert Thorneycroft
Modified: 2005-04-28 05:47 UTC (History)
1 user (show)

See Also:
Package list:
Runtime testing required: ---


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Robert Thorneycroft 2003-12-12 14:03:20 UTC
I have been having problems getting numlockx to work in GDM.  I saw a note on 
bugzilla #29397 which has been marked as fixed, however I believe that the problem
is not really fixed properly for the following reasons:

1. I cannot find the example mentioned in the FAQ.
2. I think the feature should just work after installation on numlockx!

Reproducible: Always
Steps to Reproduce:
1. Install GDM
2. Install numlockx
3. Try to use the keypad.

Actual Results:  
Nothing happens.

Expected Results:  
I would have hoped that the feature would just work after installation without 
having to go trying to find FAQs to get it to work and without having to manually 
reconfigure xinitrc files etc. which are then likely as not to get accidentally 
overwritten during a later package installation.


In order to avoid this problem I propose the following patch to
/etc/X11/gdm/Init/Default

+ # Start numlockx if available
+ if [ -x /usr/X11R6/bin/numlockx ]; then
+         /usr/X11R6/bin/numlockx on
+ fi

This should take all of the pain out of getting numlockx working properly after
installation on a system running GDM.
Comment 1 John N. Laliberte (RETIRED) gentoo-dev 2005-03-25 20:49:05 UTC
This bug is over 2 years old, is this still a problem for you?
Comment 2 John N. Laliberte (RETIRED) gentoo-dev 2005-04-28 05:47:15 UTC
closing as wontfix, due to inactivity by the reporter, and age of the bug. reopen if its still an issue.