num-lock mangle keyboard layout

Bug #216374 reported by Nicolas Jungers
4
Affects Status Importance Assigned to Milestone
xorg (Ubuntu)
Invalid
Undecided
Unassigned

Bug Description

When installing kubuntu 8.04 on a iMac Alu 24" with a US alu keyboard.

The keyboard selection is functional even if there is no choice for the Mac alu mapping. But once the num-lock key is hitted the keyboard become basically non-functional. It happens with alpha-5 and daily-2008-04-10.

Tags: 8.04 hardy
Revision history for this message
Michaël (mpalomas) wrote :

I confirm and reproduce this issue ...
I own a PC but with the new Apple keyboard (french alternative layout), and once num lock is hit, the keyboard layout is completely broken, the numeric keypad seems to be "moved" in the center of the keybord, so basically you can type numbers and / +- * ... by typing in the center of the keyboard, but nothing more.
This happens with Ubuntu 8.04 (Xubuntu too).
The system is unusable ...

Revision history for this message
Nicolas Jungers (unbug) wrote : Re: [Bug 216374] Re: num-lock mangle keyboard layout

Michaël wrote:
> I confirm and reproduce this issue ...
> I own a PC but with the new Apple keyboard (french alternative layout), and once num lock is hit, the keyboard layout is completely broken, the numeric keypad seems to be "moved" in the center of the keybord, so basically you can type numbers and / +- * ... by typing in the center of the keyboard, but nothing more.
> This happens with Ubuntu 8.04 (Xubuntu too).
> The system is unusable ...

petite info : cette déclaration de bug est un doublon et il y a
plusieurs solutions proposées. Il faut faire une recherche sur "apple
alu keyboard".

Bàv,
Nicolas

Revision history for this message
theOlster (oliver-thelortons) wrote :

I too am having problems with the wired GB keyboard for my iMac on Ubuntu 7.04

Revision history for this message
Ian Weisser (ian-weisser) wrote :

Thank you for taking the time to report this bug and helping to make Ubuntu better. However, you are not using the most recent version of this package for your Ubuntu release. Please upgrade to the most recent version and let us know if you are still having this issue. Thanks in advance.

Revision history for this message
Bryce Harrington (bryce) wrote :

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.

Changed in xorg:
status: Confirmed → Invalid
Revision history for this message
Nicolas Jungers (unbug) wrote :

Bryce Harrington wrote:
> 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.
>
> ** Changed in: xorg (Ubuntu)
> Status: Confirmed => Invalid
>

The problem is still present in Hardy but solved in Intrepid.

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

Other bug subscribers

Remote bug watches

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