numlock does not stay enabled Hardy alpha4

[Coz]

Hey guys,
 hardy Alpha4 clean install
I have noticed that the numlock key never is enabled when starting up and after I enable it it turns off again after a minute or so.
 I cant seem to keep it enabled!

just thought you should know

coz

[B. Clausius (barcc)]

barcc:~$ gconftool -g /desktop/gnome/peripherals/keyboard/remember_numlock_state
true

Numlock is disabled after login, but stays enabled during a session.
(hardy upgrade from gutsy)

[captive (salvo-schifani)]

same here, and /desktop/gnome/peripherals/keyboard/remember_numlock_state is already set to true.

[Pavol Klačanský (pavolzetor-deactivatedaccount)]

but i have similar problem, in loginscreen, if i numlock on i cannot write numeric else numlock off and i can write numeric

[antistress (antistress)]

same problem /desktop/gnome/peripherals/keyboard/remember_numlock_state is already set to true and NumLock is always disabled

(i've made a clean install of Hardy alpha 6 after deleting all configuration files in my $home/ )

[roman.rene (roman-rene)]

i've just installed Hardy beta on my laptop and my desktop , and the bug is still here on my both pc

Thanks

[ManuPeng (mvieuxmaire)]

It's still an issue in Hardy's development branch version from March, the 20th with all updates.

[supercompman (supercompman)]

I'm also experiencing the same problem with the Hardy beta. A minor, but very annoying bug.

[Robert Hrovat (robi-hipnos)]

Same here! Please fix this to be as it was before.

[amano (jyaku)]

I recently upgraded from Gutsy as well. Maybe the most annoying glitch in hardy at the moment. I often use my keypad and now it is always disabled when booting up. For the record, I use a german QWERTZ keyboard (Generic 105-key (Intl) PC (Germany Sun dead keys). Changing to another layout doesn't help. Is someone looking at this?

[Takahani (simon-esneault)]

Same here, ubuntu 8.04 64 bits, /desktop/gnome/peripherals/keyboard/remember_numlock_state also enabled, but no effect

[Nick B. (futurepilot)]

I have the same problem. It always remembered the state in Gutsy but not anymore in Hardy. /desktop/gnome/peripherals/keyboard/remember_numlock_state is checked in gconf-editor

[bluenova (bluenova)]

Same problem here, upon login numlock light is on, but numlock is really off. It's then necessary to press numlock 3 times to get it to the correct state of numlock light on and numlock really on. Unfortunately the setting is not remembered upon logout.

This really needs to be fixed before the final release, having to tell people they have to press numlock 3 times each time they log in will just be embarrassing.

[bluenova (bluenova)]

The fix:

Quote Dave Murphy:
----
After upgrading to Hardy I noticed that my numeric keypad was no longer working. Not a huge inconvenience, but when you’ve got one you like to be able to use it don’t you?

This morning - after trying to use it again - I decided to have another go at fixing it. A quick Google provided me with the solution:

   1. Go into the Keyboard Preferences (System >Preferences > Keyboard)
   2. Switch to the Mouse Keys tab
   3. Uncheck the box for Allow to control the pointer using the keyboard

Grammar excepted, a logical procedure but why (oh why) is it enabled by default?
----

[Takahani (simon-esneault)]

It's already unchecked here... I'll try enable/disable and reboot

[Nick B. (futurepilot)]

That was already unchecked for me too. I tried enabling it and disabling it, logging in logging out, and a number of other combinations, but nothing had an effect. Num lock is still always off.

[bluenova (bluenova)]

hmm, I guess it's back to the drawing board then. Seems that fix is only working for some people. I hope this gets sorted before the final release.

[antistress (antistress)]

this bug si not assigned ?!

[Fox (foxmaulder-1974)]

I've found an easy solution to this annoyance. Open up synaptic and search for numlockx and install it. Turn on the numlock key (not sure that step is necessary) and reboot. It worked for me.

[antistress (antistress)]

numlockx should not be required anymore since GNOME 2.14
That's a regression

[Fox (foxmaulder-1974)]

I understand and realize that, but this bug is about a month and a half old and if nobody wants to fix it, we need to get resourceful if it bothers us that much. I'm sure the devs have bigger things to worry about than this atm so I just shared what worked for me is all.

[antistress (antistress)]

what about new users ?
Will you say :
"hello, ubuntu is for human being
by the way, start synaptic and install numlockx to fix the known-bug-but-never-fixed of that LTS version"

[bluenova (bluenova)]

If this was a normal release I wouldn't be so worried, but for an LTS this
must be sorted.

On Sat, Apr 5, 2008 at 4:58 AM, antistress <email address hidden>
wrote:

> what about new users ?
> Will you say :
> "hello, ubuntu is for human being
> by the way, start synaptic and install numlockx to fix the
> known-bug-but-never-fixed of that LTS version"
>
> --
> numlock does not stay enabled Hardy alpha4
> https://bugs.launchpad.net/bugs/190579
> You received this bug notification because you are a direct subscriber
> of the bug.
>
> Status in Ubuntu: Confirmed
>
> Bug description:
> Hey guys,
> hardy Alpha4 clean install
> I have noticed that the numlock key never is enabled when starting up and
> after I enable it it turns off again after a minute or so.
> I cant seem to keep it enabled!
>
> just thought you should know
>
>
> coz
>

[Robert Hrovat (robi-hipnos)]

It seems this was fixed with yesterdays updates. On two computers numlock is turned on after booting. Can someone else check and confirm?
I have no idea which package brought the fix.

[Nick B. (futurepilot)]

Confirming. Num lock now comes back on when logging in. I installed all updates logged out and back in, turned Num lock on logged out and when I logged back in, Num lock came back on as it should.

[antistress (antistress)]

i also confirm that this bug is now fixed
thanks

[Gabriel Acevedo H. (gacevedo)]

I've just installed Hardy final release, and it won't turn on the numlock on session startup.

[Gabriel Acevedo H. (gacevedo)]

Sorry! never mind, I rebooted and it works now.

[davidr (davaweb)]

Nope - still here with me. Clean install.

I agree with antistress: "what about new users ?
Will you say :
"hello, ubuntu is for human being
by the way, start synaptic and install numlockx to fix the known-bug-but-never-fixed of that LTS version"

It's the same with the LTBug in Assitive Technologies ...

[Jmadero (jmadero)]

Update: I downloaded the new iso (was running the beta and had done the updates which fixed the problem). I wanted to format and install from fresh the new iso, the problem is back. Can someone else confirm this?

[davidr (davaweb)]

See post above yours.
It's still here.

[supercompman (supercompman)]

Well, I've done several clean installs using the release ISO and the problem is gone for the 4 systems I've installed on. I'm not saying that it doesn't still exist, but it's not something I'm seeing any more.

[davidr (davaweb)]

I'm using a Microsoft wireless Multimedia Keyboard 1.0A, unknown generic keyboards on others (all wireless).

All 3 still have it - 3 different motherboards.

Can't explain why - I don't know which logs to print that night help, I'm afraid.

Methinks some do, some don't - but in Feisty I never had a problem so I suspect it is not hardware combinations.

[fyo (fyo)]

I suffered the "numeric keypads only controls mouse cursor" bug after upgrading from Gutsy to Hardy yesterday (using the update manager). The solution proposed above of unchecking the option in the Mouse Keys tab of Keyboard Prefs worked.

However, this bug is still present. I would recommend simply having this option switched off by default...