Ubuntu
xkeyboard-config package

Special keys on Acer Aspire 5920G (Norwegian) not recognized

Bug #382257 reported by Anders
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
udev
New
Undecided
Unassigned
xkeyboard-config (Ubuntu)
Invalid
Undecided
Unassigned

Bug Description

Binary package hint: gnome-control-center

The Acer Aspire 5920 has a number of unusual keys, including a $ and a € key in the bottom right corner. Pressing these keys simply yield no input in any Ubuntu application.

Additionally, the keyboard's special play/pause, stop and forward/backward are incorrectly mapped in Totem:
Play/pause triggers fast forward
Stop triggers fast backwards/rewind
The forward/backward buttons yield no reaction.

Most other "special" keys like Wifi, Bluetooth and even the volume control work perfectly.

ProblemType: Bug
Architecture: i386
DistroRelease: Ubuntu 9.04
ExecutablePath: /usr/bin/gnome-keyboard-properties
NonfreeKernelModules: nvidia
Package: gnome-control-center 1:2.26.0-0ubuntu3
ProcEnviron:
 LANG=nb_NO.UTF-8
 SHELL=/bin/bash
SourcePackage: gnome-control-center
Uname: Linux 2.6.28-11-generic i686

Revision history for this message
Anders (andersja+launchpad-net) wrote :
Revision history for this message
Anders (andersja+launchpad-net) wrote :

Setting the keyboard layout to "Manufacturer Acer" and model to "Acer Bærbar" (tr: Acer portable / Acer laptop) does not correctly map the special keys

Sebastien Bacher (seb128)
affects: gnome-control-center (Ubuntu) → xkeyboard-config (Ubuntu)
Bryce Harrington (bryce)
tags: added: jaunty
Revision history for this message
Simos Xenitellis  (simosx) wrote :

This is a udev bug; you need to add the proper keymap for the laptop in /lib/udev/keymaps/*

I just checked that in Ubuntu 10.04 there is an entry for acer, with references to 'euro' and 'dollar',
which probably means that the problem is already solved.

Reporter, could you please verify that the issue is solved in 10.04?

Changed in xkeyboard-config (Ubuntu):
status: New → Invalid
Revision history for this message
Anders (andersja+launchpad-net) wrote :

Thanks for the update. I no longer have access to the laptop I detected this on, so I am unable to re-test. Seeing how noone else have reported any follow-ups on this bug since I reported it, it can probably be closed.

Thank you for your help.

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

Other bug subscribers

Remote bug watches

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