NumLock gets enabled unexpectedly on my laptop

[Patrick]

Since I am using Ubuntu Feisty I have problems with Num Lock. When using an external keyboard there is no problem at all, but when using the laptop keyboard Num Luck starts at unexpected moments (I am using an IBM Thinkpad T42).

The laptop starts with the NumLock enabled (which I do not like anyway). Then I have to switch the numlock off. When doing this the NumLock led indicator does _not_ switch of (it still indicated that NumLock is enabled), but NumLock is off. There is no way I can switch off the NumLock-enabled led/indicator. When pressing special keys like CapsLock then NumLock gets enabled and I have to disable it again.

This is quite annoying and very inconvenient especially when typing passwords (as the indicator does not work).

ProblemType: Bug
Architecture: i386
Date: Thu Mar 15 11:54:58 2007
DistroRelease: Ubuntu 7.04
Uname: Linux patrick-laptop 2.6.20-10-generic #2 SMP Mon Mar 12 00:02:49 UTC 2007 i686 GNU/Linux

[Michael Kanis (mkanis)]

I do have the exactly same bug on an IBM Thinkpad T23. Would be really nice to see this gone in the final Feisty.

[GercoKees (gercokees)]

I have a very similar problem.
I use Edgy and Num-lock is activated at unexpected moments. I do use an Acer-aspire laptop... In a few days i will upgrade to feisty. I will report when the problem persists.

[Tor Bendiksen (tor-tblab)]

Also happens with me on my Thinkpad T30. When connected to an external keyboard it enables numlock just after I log in to X/gnome. This is expected, and wanted. When logging in to X/Gnome without an external keyboard the numlock led light comes on, and num-lock is active. Pressing num-lock to turn it off works, but the led is still on. If I switch to a virtual terminal (and of 1-6), and back the num-lock led will go off. I would be willing to try to debug this problem, but I have absolutely no clue where to start.

[Patrick (hanckmann-gmail)]

For me the problem as such still exsists. Only now, the Num-Lock led is not on by default anymore, nor does it switch to Num-Lock at unwanted moment.
The problem now is that the Num-Lock LED does not light up anymore at all.

[Michael Roy (mikemlp)]

See this thread in Ubuntuforums: [URL="http://ubuntuforums.org/showthread.php?p=2716481#post2716481[/URL]

     To quote Jingo:
          "Same problem. T42.

          Solved it by disabling gnome's "remember_numlock_state".
          Open up gconf-editor and search for "numlock", and you will see."

I have not tried this solution myself yet, so try at your own risk.

[Michael Roy (mikemlp)]

Also, my symptoms were slightly different - My numlock light gets stuck on and the altered keys ('letter' keys which become transformed into 'numeric keys' when numlock is on) will not create any output at all when pressed, not even the expected numeric output. The only way to turn off numlock is to use an external keyboard. If the computer starts up with numlock off, and it is turned on by pressing fn+scroll lock, there is no way to turn it off unless an external keyboard is plugged in. My issue may, then, be a separate issue with somewhat similar symptoms.

[Michael Kanis (mkanis)]

I also set the gconf key, mentioned in the link. This changes the behaviour a bit, however it does not really fix the bug.
Now (after disabling remember_numlock) the Numlock does not get enabled on startup and also not when pressing capslock. The Numlock LED stays off, no matter the state of Numlock.
When Numlock is on, the keys affected by this do not generate any characters at all. They do not even generate events in `xev`.

I also think, this bug is not related to xserver, as the behaviour is nearly the same on terminals (Ctrl+Alt+F1-6).

Could provide further information if needed, but I don't know where to start. :-)

[Bryce Harrington (bryce)]

We might be dealing with two or more unrelated bugs.

Michael, one way to rule out whether it is the xserver or not would be to boot linux in console mode, without going into X at all, and see if the behavior still occurs.

This sort of sounds similar to this upstream bug: https://bugs.freedesktop.org/show_bug.cgi?id=3037. However the symptoms are a bit different.

Patrick, or others having this issue, can you please attach your /etc/X11/xorg.conf and /var/log/Xorg.0.log files?

[Patrick (hanckmann-gmail)]

As requested in a mail of june 14

"Patrick, or others having this issue, can you please attach your /etc/X11/xorg.conf and /var/log/Xorg.0.log files?"

[Patrick (hanckmann-gmail)]

As requested in a mail of june 14

"Patrick, or others having this issue, can you please attach your /etc/X11/xorg.conf and /var/log/Xorg.0.log files?"

[tf (dr-tomas)]

Have the same problem; when I turn on Caps Lock, both Caps Lock and Num Lock are set; however, when the Caps Lock is truned off, the Num Lock remains in place and cannot be turned off exept for swithcing out of VT7 to VT1 and back -- BTW, if you google the Ubuntu Forums, you will see this problem has been around for 2 years now.

This bug should be upgraded from medium, as it renders the laptop keyboard near unusable.

[Michael Roy (mikemlp)]

xorg.conf as requested.

[Michael Roy (mikemlp)]

Xorg.0.log as requested.

[jpdborgna (jpdborgna)]

I have the same problem with a G41. Has it been solved?
Regards.

[Patrick (hanckmann-gmail)]

Hi there, today I did a clean install of Ubuntu Feisty from a newly downloaded cd. At this moment the Num-Lock problem seems fixed here. I will let you know if the problem returns!
Thanks for fixing it :-).

[Patrick (hanckmann-gmail)]

Oke, the problem returned. Now the led stays off and Num-Lock does not work at all (when working on the laptop keyboard). I did not test an external keyboard.
Anyway, it seems that the problem is still there. This week I will try the Gutsy live cd to see how it works there.

[Naveen N Rao (naveen-n-rao)]

This issue suddenly started showing up since yesterday. I have been on feisty for a while now and haven't seen this. I remember doing a dist-upgrade recently which upgraded a bunch of kde packages mostly. Plus, I installed nxserver packages from www.nomachine.com. Don't know if any of that is relevant here.
For me, on bootup, up till the login screen, everything is fine. The moment I login, numlock key is activated. Shift+Numlock doesn't turn off the LED - but, numlock would be switched off as verified in a terminal.
Bumped to this thread: http://ubuntuforums.org/archive/index.php/t-108431.html - installed numlockx. 'numlockx off' properly switches off the numlock led and disables numlock. 'numlockx on' switches on the led, but the behaviour is not the same. Now, I do not get anything when I type keys that have numbers on them.
On T42p.

- Naveen

[J Sinclair (jsinclair)]

I was having the same problem on my Thinkpad R51. I found a solution that worked for me here: http://kogs-www.informatik.uni-hamburg.de/~meine/thinkpad under the section "Making the Numlock work again".

Basically just run this command (I put it in my .bash_profile so it is applied every time I boot):

xmodmap -e "keycode 77 = Num_Lock"

Hope it works for you guys.

[J Sinclair (jsinclair)]

Sorry, I spoke too soon. This fixed another related problem I was having using a USB numeric keypad with my Thinkpad, but the problem with Caps lock setting the Num lock still exists.

[Shtepan Funky (steve-kriz)]

Hi, I have similiar problems on ThinkPad T41.

xmodmap -e "keycode 77 = Num_Lock"

- this make function LED sign under screen and disable strange behave of Num Keys, BUT Num Keys still doesn't type numbers. (when NumLk is on keys are not warking at all, when it is off I can type normal letters, smybols, etc.)

Thank you for any advice.

[Pekka Enberg (penberg)]

I too have this problem. I have a IBM Thinkpad T42p laptop and have seen this issue with other distributions as well.

When I log on to Gnome, NumLock enabled for some reason on laptops keyboard. The actual login screen works as expected. Now, if I press the NumLock button after login, it's disabled and the keyboard works as expected. However, if I now press CapsLock, the alphanumeric buttons stop working and are effectively dead.

Switching to a virtual console and back to X always resets the keyboard so that it works as expected. The keyboard also works as expected when booting into console-only single user mode.

[Pekka Enberg (penberg)]

I upgraded from Feisty Fawn to Gutsy Gibbon and now switching to a virtual console and back to X no longer resets the keyboard. So now I need to press NumLock after login to get the laptop keyboard working. Also, CapsLock is now totally dead for the alphanumeric buttons in X. Everything still works properly in the console though.

[Timo Aaltonen (tjaalton)]

Please try with hardy alpha2. It has had many input related changes.

[Tor Bendiksen (tor-tblab)]

Well, it seems that no-one has tried hardy yet (or at least not reported back here with results).

Myself, I am not willing to go to Hardy anytime soon as this is my main machine that I use every day.
I need a stable environment and I don't believe Hardy is there yet.
While this problem is really, really annoying it is workable.

What I don't get is this:
Does this really affect all Thinkpads? If not, what is different?
Does everyone just do like me and manually change numlock/capslock status every time you log in / come out of sleep mode?
Is anyone looking into this at all? I can help out, but I need to know where to start.

I write this because I noticed that this bug will be automatically closed in 31 days, and as far as I am concerned it is far from fixed. As a matter of fact there seems to have been little activity except from users confirming the problem.

Anyone have anything to add? Please?

[Pekka Enberg (penberg)]

Well, this bug should obviously not be closed as it's not fixed and is trivially reproducible. Upgrading to Hardy is not an option for me either, especially considering that no one has actually confirmed that the bug is fixed, just that "there are input related changes in alpha2." And it's not even clear whether this is a xorg or a Gnome bug. Do people with Kubuntu experience this?

[Rolf Leggewie (r0lf)]

Confirming.

I have seen this (and IIRC reported it, too). Might be that we are looking at more than one issue here with the multitude of reports. The water is still kind of muddy.

[Enrique (zetacygnus)]

I confirm what Naveen says about the numlockx behavior in my T42 with ubuntu feisty. I found a not-so-elegant solution. If you go to System -> Preferences -> Keyboard -> Layouts -> Keyboard model, I have a Generic 105-key (Intl) PC. Change that to IBM ThinkPad 560Z/600/600E/A22E, Intl. Now this gets very tricky. Press Shift+NumLk then type "numlockx toggle" (type this before Shift+NumLk in the terminal, otherwise the keys with number won't work) and now your numlock keys work. Shift+NumLk again and you recover the normal keyboar state but the led is still on. I tried this several time and it not always work in the same way. Sometimes you don't need the Shift+NumLk before the 'numlockx toggle' command... It is still anoying.

Enrique

[Matthijs (mvhenten)]

Hi anyone looked into this yet? it's annoying and should not happen. I have this problem since I upgraded a slackware 10.1 installation to ubuntu 7.2 ( what's up with those names? I can hardly remember feisty fawstey or whatever. Whenever the laptop comes out of sleep mode ( the REAL sleep, apm driven, not acpi! ) the numlock is on, the same after a reboot. running single user mode I don't have this problem, so it must be gnome/x related.

[emmeda (emmeda)]

Hi,

I have the same problem and updated to Hardy, but it did not help.
Using the gconf-editor and searching for numlock I found "numlock_remember_state" and "numlock_on".
"numlock_remember_state" let Ubuntu remember the "numlock_on" state from xsession to xsession. But "numlock_on" just change the baviour of an activated numpad:

numlock_on = true:
active -> you can type digits
inactive -> you can type letters

numlock_on = false:
active -> you can use numpad as arrows (u = left, o = right, 8 = up, etc.)
inactive -> you can type letters

The problem that I have is, that I cannot change the state of the LED with my keyboard (shift + numlock) and that the numpad is per default active (either I can typ digits or I can use arrows).

Greetz,
EmmeDa

[Payal (payal-kucheria)]

Me too..

I am running a IBM T41 with up to date Hardy.

This suddenly started after a recent upgrade.

[Payal (payal-kucheria)]

Interesting...it seems it is only the Numlock LED state that is messed up.

Pressing shift–numlock allows me to type again, but the numlock LED stays on.

[Patrick (hanckmann-gmail)]

This problem is/seems to be solved in the 8.04 beta.
Still I suggest to wait with an update due to some other issues (sound and video driver)
P.

[caspar_wrede (caspar-wrede)]

Problem NOT solved in Hardy. I have an x31 Thinkpad.

Numlock LED is always on, but pressing shift-numlock allows me to type (see payal's post)

[jay Urbanski (m-launchpad-0222-strops-org)]

I confirm I see the same behavior on my Thinkpad T42p. It is reproducible, whenever I login to a nomachine session from my desktop (which has the numlock on) the numlock light will become stuck on in Ubunto and the LED will not go off even if I toggle numlock off (although the keys toggle on and off). Very annoying.

[emmeda (emmeda)]

I fixed this problem for me!
I connected an external keyboard to my Thinkpad and pressed the numlock-key. Afterwards the numlock led turned off. After that, i plugged off the external keyboard again and the led and the numlock keys worked again as usual.

The bug that i have discovered at my Thinkpad probably is, that the keyvalue send from an external keyboard maybe a different one from the keyvalue which is produced by the Thinkpad itself (Fn + Num). But as you need this special keyvalue of an external keyboard's numlock-key to turn off the led of your Thinkpad, it is not possible to do this without an external keyboard. I am not sure about this, but it worked for me.

Tensed to see some answers,
EmmeDa

[Rolf Leggewie (r0lf)]

emmeda, xev is a program where you can find out what key events are being sent by what key stroke, take a look at bug 182421

[emmeda (emmeda)]

Thx Rofl, that looks much more like the bug I had.

[Arthur (moz-liebesgedichte)]

Interestingly I didn't have this problem at all on my X41 before. Since I've installed NX server everytime I remote log in (separate gnome session, same user) the NumLock LED goes on and stays on and the numeric keys are enabled as the Home/PgUp/End/PgDn/Del/Cursors as you can find them on a full-fledged keyboard. Shift-ScrlLk(NumLk) sets the keyboard right again, the LED stays on.

[Dima Ryazanov (dima-gmail)]

This just happened to me, too.

Looks like I can turn on/off the LED using an external keyboard, but not my laptop's keyboard (thinkpad t43p).

Why is the numlock value saved in the first place?? There should either be a GUI for it, or this setting should not exist.

[NoOp (glgxg)]

@Arthur: I can verify that this happens with NX server:

- Fresh install of 8.04.1 on an IBM Thinkpad T30, no issues with NumLk.
- Installed NX:
  nxclient_3.2.0-14_i386.deb
  nxnode_3.2.0-13_i386.deb
  nxserver_3.2.0-16_i386.deb
and NX'ed into the T30 to verify all was working. Immediately the NumLk LED came on and the numeric keys were enabled. The only way that I could get the alpha keys back was to do as you suggested Shift-ScrlLk(NumLk), and the LED stays on. Oddly enough, I log back in via NX to the T30 and then log back out and NumLk is no longer enabled, nor is the NumLk LED on.

Log back in to the T30 and press NumLk on the remote, NumLk key on the T30 goes on and off properly (I have the two machines side by side so it's easy to monitory). I leave the NumLk key enabled via the remote NX and logout. The T30 is left in a NumLk state; this time numbers on the keypad are working (type 'k' and the result is '2'). Pressing Shift-ScrlLk(NumLk) returns the keyboard to alpha, but LED is still on.

Test again: this time I turn off the "Remember NumLock State" in the T30. NumLk control from the remote now has no effect on the T30 target. Turn it back on (in the T30) and NumLk control from the remote now works.
Logout with NumLk turned off on the remote (and the T30) and now I'm back to no LED and no '2' when I press 'k' on the T30. Pressing Shift-ScrlLk(NumLk) returns the keyboard to alpha, but this time _no_ NumLk LED is on.

So perhaps it is a combination of Ubuntu and the application. In any event, the above _is_ reproducible if any developers want to test. (And yes Leann, I know that the Intrepid kernel is available... but this is an LTS release so testing via Intrepid isn't practical).

[Arthur (moz-liebesgedichte)]

Kicking nxserver and nxsensor out of /etc/rc2.d/ and rebooting resolved the issue for me. Only stopping nxserver didn't help. I didn't try to restart just the X session.

[huepfend_schof (kaweechelchen)]

The problem is still not solved in Ubuntu Intrepid!!
I use an IBM Thinkpad R50p.
The problem is very annoying, and I am wondering why this bug isn't fixed after almost 2 years.

[NoOp (glgxg)]

Tested again using Intrepid (fully updated from 2008-11-26), and experience the exact same symptoms as described in my post of 2008-09-19.

[sivencl (lechatcl)]

problem in Intrepid in my Thinkpad R32 AND my Acer Aspireone is perhaps different : I have a Numlock key.
At the begining, when I push the numocl key,the led become lighted, a is A, h is H,but " is", not 3.
This was not good for the range with numbers.
So I change in System> preferences > clavier (yes french) > other options > Ver key is ver key for all the touchs.
But, afetr all is good, a is A, " is 3, BUT but the no led. The led remains not lighted. I can't know if I am in Numkey or not.
If I do System>preference > keypad > Num lock key as an alternative etc; so the led remains not lighted. AND ia one clock doesn't run....Double click too.
SO I had tu return with not Numlock key case typed.

It's the same in my R32, in my acer aspire one and I have to test on my packard.

What news on this problem ?

regards.

[NoOp (glgxg)]

Same problem today on Jaunty (2.6.28-12-generic) as I reported in
https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/92482/comments/40
I had upgraded all of my NX software yesterday & tested by logging into the A21m and the issue is back. The NX acts as a remote keyboard.

On interesting result is that if I am in terminal and I Shift-NumLk I get no numbers at all, but I see the cursor move down and one space to the right each time that I press the 'h' key (number 3). If I keep pressing the key I can get the cursor to move all the way off the screen. If I press the 'k' key (number 2), the cursor moves directly down (vertical) one space. So toggling the Shift-NumLk is somehow setting to keyboard mouse control.

[NoOp (glgxg)]

OK. A bit long here, but I _think_ I've finally sorted out the workaround.
Finally, I reread
<https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/92482/comments/18>
and went digging on google and found:
<http://www.thinkwiki.org/wiki/How_to_get_special_keys_to_work#NumLock>

>> >> NumLock
>> >>
>> >> On the ThinkPad 600, T20, T21, T22, T30, X20, X21, X31, X40, T42p,
> > T43, R51, R52 and possibly other models, X does not recognize the
> > keycode for NumLk = Shift+ScrLk. To fix this, add the following to
> > ~/.Xmodmap in your home directory or /etc/X11/Xmodmap and run xmodmap,
> > ex: xmodmap ~/.Xmodmap:
>> >>
>> >> keycode 77 = Num_Lock
>> >>
>> >> The following might work better for you:
>> >>
>> >> keycode 77 = Num_Lock Num_Lock
>> >>
>> >> because you will only get keycode 77 together with Shift (at least
>> >> on
> > the T43)
>> >>
>> >> This configuration also enables the respective LED.
>> >>
>> >> Please note, pressing the Shift+ScrLk key combination, without first
> > following the above configuration, will start an accessibility feature,
> > which will allow the numeric keypad to maneuver the mouse pointer.
> > Starting this accessibility feature and subsequently running xmodmap, as
> > described above, results in the accessibility feature and the numeric
> > lock LED functioning simultaneously. As such, the above configuration
> > should be completed before the accessibility feature is started in order
> > to produce numbers.

That seems to describe exactly what I was seeing with the cursor movement.

So, I figure what the heck & create two files:

~/.Xmodmap
and
/etc/X11/Xmodmap

and in both I add:

keycode 77 = Num_Lock Num_Lock

And then:

$ xmodmap /etc/X11/Xmodmap

Logout/in and what do you know... not only does Shift-NumLk work, but
the LED also works! Thinking that it's just a fluke, I powerdown the
A21m, wait for a few moments, and power back up. NumLk is working
properly! Reboot a few times, still works. Login/out from a remote NX and it still works! :-)

So I guess the next questions would be; 1) why is Shift-NumLk triggering an accessibility feature (converting to keyboard cursor movement) to begin with, and 2) what reads the Xmodmap files on gdm start?

[P4man (duvel123)]

I have a similar problem, and knowing how to trigger and cure it may (or may not) help some of you.

 ET Wolfenstein (game) doesn't properly work with my azerty keyboard, so before launching it I execute
xmodmap with a different layout file. After exiting, I want to restore the keyboard layout with:

xmodmap /usr/share/xmodmap/xmodmap.be

And then I have the problem some of you have: numlock will no longer work, nor will the arrow keys. In fact, no matter what keymap I select, I get that problem.

Oddly, what solved it for me is :
system > preferences > keyboard > layouts > layout options

*Anything* I change there instantly solves it, even if I change "adding eurosign" settings or something. The numock light goes on again, and works again, as do arrow keys.

Its quite possible Im doing something wrong, but I thought it might help track this problem.

[Bryce Harrington (bryce)]

[This is an automatic notification.]

Hi Patrick,

This bug was reported against an earlier version of Ubuntu, can you
test if it still occurs on Lucid?

Please note we also provide technical support for older versions of
Ubuntu, but not in the bug tracker. Instead, to raise the issue through
normal support channels, please see:

    http://www.ubuntu.com/support

If you are the original reporter and can still reproduce the issue on
Lucid, please run the following command to refresh the report:

  apport-collect 92482

If you are not the original reporter, please file a new bug report, so
we can work with you as the original reporter instead (you can reference
bug 92482 in your report if you think it may be related):

  ubuntu-bug xorg

If by chance you can no longer reproduce the issue on Lucid or if you
feel it is no longer relevant, please mark the bug report 'Fix Released'
or 'Invalid' as appropriate, at the following URL:

  https://bugs.launchpad.net/ubuntu/+bug/92482

[Patrick (hanckmann-gmail)]

Sadly, I have no IBM laptop anymore to test this on. However, on my other laptop (Acer) this problem does not occur. I propose to tag this bug 'Fix Released' or (maybe better) 'Invalid'.

[Rolf Leggewie (r0lf)]

I can still test this. And I remember that this was still broken at least at the beginning of this year. I was running karmic, then. I'll try to test this one of these days in Lucid. Please ping me once more before closing in case I forget.

[cnshw (cnshw)]

I've come across this problem today on my IBM T43.The Numlock led indicator gets on when I login,and it does't gets off whenever I press Shift+Numlck or other keys,but the numpad's state can be switched.
I'm using Ubuntu 9.10.

[Rolf Leggewie (r0lf)]

cnshw, can you test one of the lucid live CD?

[X-Byte (xbyte)]

Happens to me as well. Using a Thinkpad T40. Caps Lock is no problem.
NumLock shows the specified behaviour.
After login, NumLock gets activated, LED turns on.
Shift+ScrollLock (NumLock) does does disable NumLock keys, but LED stays turned on.

There was no problem in Ubuntu 9.04 and 9.10 for me. Problem occured after upgrading existing Installation to 10.04.

The Problem even shows just booting the LiveCD of Ubuntu 10.04.
Will try it on a Thinpad T43 later and see if the problems occurs as well.

[Rolf Leggewie (r0lf)]

x-byte, can you please run "apport-collect 92482"?

[cnshw (cnshw)]

Hi Rolf,I have updated to lucid 10.04 LTS on my T43 via the internet,I didn't test it with a bootable LiveCD.
Unfortunately, I found the problem still goes on.
It's just the same as X-byte said,the Capslock key works fine,but the Shift+Numlock goes no problem only before I login.
After I logined,the Numlck LED turns on,Shift+numlck works only functionally but not the LED.

[cnshw (cnshw)]

Oh,by the way Rolf,I've installed Lucid on an USB-HDD and boot from it when I use Ubuntu.
The inner hard disk has a WindowsXP on it.
I have no idea whether this will affect the problem.

[Rolf Leggewie (r0lf)]

cnshw, thank you for adding more information. It shouldn't matter what medium you boot from. But we still need somebody to run "apport-collect 92482" to get the information needed to progress.

[jaf0 (jaf0)]

running lucid with latest updates ..

This bug affects me too...

IBM/Lenovo t40

running apport-collect 92482

[jaf0 (jaf0)]

oops. dialog cleared unintentionally? so running apport-collect again,

[jaf0 (jaf0)]

<FIX>

(doesn't cure the num-lock light, but at least doesn't re-enable numlock on wakeup....

Use "IBM Thinkpad R60/T60/R61/T61" in System -> Preferences -> Keyboard Preferences.

(although I haven't checked the effect when I dock or attach a full-size keyboard yet.)

[jaf0 (jaf0)]

ok so i lied. i still have the problem when docked ....

[JackDeth (jackdeth)]

I am having this identical problem after upgrading to 10.04 except I have a T41. Numlock light stays on all the time. Numlock turns itself on randomly without knowledge. Only way to tell is you suddenly aren't typing right when hitting any of the keys on the right side of the keyboard that constitute the blue numeric keypad keys. This never happened with any previous version I tried.

[Chris Bainbridge (chris-bainbridge)]

Bug still present in Lucid. Using Thinkpad T42p... It took ages to figure out why j k l were printing numbers....

I'll report back after updating to Maverick.

[PianoMonkey (ethanherbertson)]

I'm running Mint 10 on a ZaReason Strata Pro 13, and I've had similar difficulties: Num Lock turning on and off at random, the NumLk key not always reliably affecting Num Lock state (or LED), etc.

I was going to post all this when I noticed that the NumLk key on my keyboard is EXTREMELY sensitive to touch--as in, I need only brush a finger across it for it to activate/deactivate Num Lock. I'm not sure how this could relate to the problem others are reporting, but I have to assume it accounts for the problems I'm experiencing.

I'm assuming it's a hardware problem, but I'm going to investigate the software side to see if the sensitivity might (somehow) be adjustable.

[Sebastian Nohn (sebastian-nohn)]

Same Problem on t43p on Maverick

[Bryce Harrington (bryce)]

I notice there's not been comments on this since Maverick. Anyone still seeing this problem in Oneiric?

[bugbot (bugbot)]

We're closing this bug since it is has been some time with no response from the original reporter. However, if the issue still exists please feel free to reopen with the requested information. Also, if you could, please test against the latest development version of Ubuntu, since this confirms the bug is one we may be able to pass upstream for help.

[Kent Lin (kent-jclin)]

Test with Oneiric, the issue still can be seen in Oneiric.

[James M. Leddy (jm-leddy)]

Hi Kent,

Which hardware do you have that are experiencing this problem?

[bugbot (bugbot)]

We're closing this bug since there has not been a response from the original reporter. However, the issue still exists please feel free to reopen with the requested information. If you're not the original reporter, we'd prefer you file a new bug report.

Some tips:

  * Report X.org bugs via the command: `ubuntu-bug xorg`

  * Test against the latest development Ubuntu. http://cdimage.ubuntu.com/daily-live/
    Bugs marked as affecting the development version tend to get priority attention.

  * The `xdiagnose` utility has functionality for enabling debugging and
    analyzing a few common X problems.

  * Tag your bugs with the Ubuntu versions you have reproduced the issue in.

  * See https://wiki.ubuntu.com/X/Reporting for tips on writing good bug reports.