Numlock setting not preserved by grub

Bug #1027694 reported by tomsam on 2012-07-22
56
This bug affects 11 people
Affects Status Importance Assigned to Milestone
grub
Unknown
Unknown
grub2 (Ubuntu)
Undecided
Unassigned

Bug Description

Grub 1.99 on Ubuntu 12.04 (current version; fully updated this morning Jul 22, 2012)

On my PC, the default Numlock setting in the BIOS is ON (and since this is not a laptop, Numlock should be staying on all the day).

Before grub and Ubuntu were installed, Win7 had started correctly with Numlock on.
After that, neither Ubuntu 12.04 nor Win7 start with Numlock on.

Apparently, Numlock is on until grub is started (meaning the BIOS sets it to its default, and the Numlock led is lit).
Then Numlock is switched off at about the time the grub menu is displayed. If one of the
operation systems is selected, Numlock is not switched on again, but stays off.

See http://savannah.gnu.org/bugs/?34547
In that bug report they state that this is a problem of the patches Ubuntu applies to grub.

Note: I know about numlockx, but this doesn't solve the problem with Win7.
And: numlockx switches Numlock on too late (meaning: after the lightdm login screen)

How do I get a correct version of grub?

Thomas

Thank you for taking the time to report this bug and helping to make Ubuntu better. It seems that your bug report is not filed about a specific source package though, rather it is just filed against Ubuntu in general. It is important that bug reports be filed about source packages so that people interested in the package can find the bugs about it. You can find some hints about determining what package your bug might be about at https://wiki.ubuntu.com/Bugs/FindRightPackage. You might also ask for help in the #ubuntu-bugs irc channel on Freenode.

To change the source package that this bug is filed about visit https://bugs.launchpad.net/ubuntu/+bug/1027694/+editstatus and add the package name in the text box next to the word Package.

[This is an automated message. I apologize if it reached you inappropriately; please just reply to this message indicating so.]

tags: added: bot-comment
tomsam (tomsam) on 2012-07-22
affects: ubuntu → grub (Ubuntu)
Steve Langasek (vorlon) on 2012-07-22
affects: grub (Ubuntu) → grub2 (Ubuntu)
Launchpad Janitor (janitor) wrote :

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in grub2 (Ubuntu):
status: New → Confirmed
Lephix (lephix) wrote :

I encounter the same issue.

Björn Carlsson (b-r-carlsson) wrote :

I run Linux Mint 16 and Windows 7 and experience the same issue.
In Mint I found a workaround by using numlockx in mdm, the same could be done for Lightgdm, but for Windows I haven't found a solution yet.

http://forums.linuxmint.com/viewtopic.php?f=90&t=108658&start=20

About Windows 7, I can reproduce the bug. About Ubuntu 13.10, I use numlockx too.

To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.