Comment 3 for bug 977683

On Tue, Apr 10, 2012 at 08:16:26AM -0000, Albert Astals Cid wrote:
> How is your external display connected? Via a regular port or via some
> propietary hardware system?

Er, it's a regular port.

> If you feel adventurous please install unity-2d from this ppa
> https://launchpad.net/~aacid/+archive/ppaprecise/ and do the following

> * Open a terminal
> * Write "killall unity-2d-shell"
> * Write "killall unity-2d-shell" again
> * Write "unity-2d-shell"
> * Try to reproduce the problem with alt+tab triggering the hud
> * Attach here the output of the "unity-2d-shell" command, which shall contain the logging of which keys you pressed/released and why the hud was triggered

Took a while to reproduce the problem, but here it is. As it happens, my
external monitor was not connected when this occurred.

unity-2d-shell: [DEBUG] KeyDebug "19:11:17.483" You released Alt it was a hold
unity-2d-shell: [DEBUG] KeyDebug "19:11:18.915" You pressed Alt
unity-2d-shell: [DEBUG] KeyDebug "19:11:19.075" You released Alt it's a tap
unity-2d-shell: [DEBUG] KeyDebug "19:11:19.947" You pressed Alt
unity-2d-shell: [DEBUG] KeyDebug "19:11:20.197" You pressed Alt for 250 ms, it's a hold
unity-2d-shell: [DEBUG] KeyDebug "19:11:20.411" You released Alt it was a hold
unity-2d-shell: [DEBUG] KeyDebug "19:11:30.619" You pressed Alt
unity-2d-shell: [DEBUG] KeyDebug "19:11:30.843" You released Alt it's a tap
unity-2d-shell: [DEBUG] KeyDebug "19:11:32.372" You pressed Alt
unity-2d-shell: [DEBUG] KeyDebug "19:11:32.595" You released Alt it's a tap
unity-2d-shell: [DEBUG] KeyDebug "19:11:32.915" You pressed Alt
unity-2d-shell: [DEBUG] KeyDebug "19:11:33.107" You released Alt it's a tap
unity-2d-shell: [DEBUG] KeyDebug "19:11:34.188" You pressed Alt
unity-2d-shell: [DEBUG] KeyDebug "19:11:34.438" You pressed Alt for 250 ms, it's a hold
unity-2d-shell: [DEBUG] KeyDebug "19:11:37.595" You released Alt it was a hold
unity-2d-shell: [DEBUG] KeyDebug "19:11:38.875" You pressed Alt
unity-2d-shell: [DEBUG] KeyDebug "19:11:39.126" You pressed Alt for 250 ms, it's a hold
unity-2d-shell: [DEBUG] KeyDebug "19:11:39.155" You released Alt it was a hold
unity-2d-shell: [DEBUG] KeyDebug "19:11:39.540" You pressed Alt
unity-2d-shell: [DEBUG] KeyDebug "19:11:39.790" You pressed Alt for 250 ms, it's a hold
unity-2d-shell: [DEBUG] KeyDebug "19:11:39.811" You released Alt it was a hold
unity-2d-shell: [DEBUG] KeyDebug "19:11:40.004" You pressed Alt
unity-2d-shell: [DEBUG] KeyDebug "19:11:40.254" You pressed Alt for 250 ms, it's a hold
unity-2d-shell: [DEBUG] KeyDebug "19:11:40.411" You released Alt it was a hold
unity-2d-shell: [DEBUG] KeyDebug "19:11:40.803" You pressed Alt
unity-2d-shell: [DEBUG] KeyDebug "19:11:41.035" You released Alt it's a tap

So perhaps this has nothing to do with the external monitor at all, and is
just because I type faster when I'm on my external *keyboard* and can
Alt+Tab between windows quicker?

I assumed unity had some way of noticing whether other keys were pressed
while Alt was held down, and if so to ignore it. I gather from the
debugging output that this is not the case?

--
Steve Langasek Give me a lever long enough and a Free OS
Debian Developer to set it on, and I can move the world.
Ubuntu Developer http://www.debian.org/
<email address hidden> <email address hidden>