Unity

Thinkpad previous/next keys trigger HUD

Bug #1047449 reported by Alan Pope 🍺🐧🐱 🦄 on 2012-09-07

This bug report is a duplicate of: Bug #969039: HUD appears when tapping Alt+Left very quickly. Edit Remove

This bug affects 1 person

Affects		Status	Importance	Assigned to	Milestone
	Unity	New	Undecided	Unassigned

Bug Description

The two keys located above the left and right cursor keys on a thinkpad keyboard seem to be mapped to ALT+left and ALT+right. This is expected, and in apps such as Xchat can be used to move channels up and down the list. Unfortunately after pressing them the HUD appears. It's really annoying as one often stabs these by accident when heading for the cursor cluster nearby.

ProblemType: Bug
DistroRelease: Ubuntu 12.04
Package: unity 5.14.0+bzr2400ubuntu0+704 [origin: LP-PPA-unity-team-sru]
ProcVersionSignature: Ubuntu 3.2.0-29.46-generic 3.2.24
Uname: Linux 3.2.0-29-generic x86_64
ApportVersion: 2.0.1-0ubuntu12
Architecture: amd64
CompizPlugins: [core,composite,opengl,compiztoolbox,decor,vpswitch,snap,mousepoll,resize,place,move,wall,grid,regex,imgpng,session,gnomecompat,animation,fade,unitymtgrabhandles,workarounds,scale,expo,ezoom,unityshell]
CrashDB: unity
Date: Fri Sep 7 16:14:09 2012
EcryptfsInUse: Yes
InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release amd64 (20120425)
SourcePackage: unity
UpgradeStatus: No upgrade log present (probably fresh install)

Tags:

Revision history for this message

Alan Pope 🍺🐧🐱 🦄 (popey) wrote on 2012-09-07:

Dependencies.txt Edit (7.3 KiB, text/plain; charset="utf-8")
GconfCompiz.txt Edit (36.8 KiB, text/plain; charset="utf-8")
ProcEnviron.txt Edit (294 bytes, text/plain; charset="utf-8")

Revision history for this message

Daniel van Vugt (vanvugt) wrote on 2012-09-10:

Thank you for taking the time to report this bug and helping to make Ubuntu better. This particular bug has already been reported and is a duplicate of bug 969039, so it is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Feel free to continue to report any other bugs you may find.