Thanks for trying to verify. Below are xev KeyPress and KeyRelease sequences for cases where HUD did and did not appear.
Since I've been using ubuntu/compiz/unity for a while, it seemed possible that I have some old config kruft that was necessary for this bug. I started up a guest session and indeed the problem does not appear.
So, my current hypothesis is that there is a user selectable delay buried somewhere that I configured long ago in a galaxy far far away. Any ideas where to look for that? Or, barring that, what config file to toss as a test?
xev data:
=======
Here's an xev sequence that caused the hud to appear.
KeyPress event, serial 28, synthetic NO, window 0x5400001,
root 0x9f, subw 0x0, time 134674304, (69,151), root:(1141,203),
state 0x0, keycode 64 (keysym 0xffe9, Alt_L), same_screen YES,
XLookupString gives 0 bytes:
XmbLookupString gives 0 bytes:
XFilterEvent returns: False
KeyPress event, serial 28, synthetic NO, window 0x5400001,
root 0x9f, subw 0x0, time 134674384, (69,151), root:(1141,203),
state 0x8, keycode 40 (keysym 0x64, d), same_screen YES,
XLookupString gives 1 bytes: (64) "d"
XmbLookupString gives 1 bytes: (64) "d"
XFilterEvent returns: False
KeyRelease event, serial 28, synthetic NO, window 0x5400001,
root 0x9f, subw 0x0, time 134674424, (69,151), root:(1141,203),
state 0x8, keycode 64 (keysym 0xffe9, Alt_L), same_screen YES,
XLookupString gives 0 bytes:
XFilterEvent returns: False
KeyRelease event, serial 28, synthetic NO, window 0x5400001,
root 0x9f, subw 0x0, time 134674442, (69,151), root:(1141,203),
state 0x0, keycode 40 (keysym 0x64, d), same_screen YES,
XLookupString gives 1 bytes: (64) "d"
XFilterEvent returns: False
And, for comparison, a sequence that didn't cause hud:
KeyPress event, serial 28, synthetic NO, window 0x5400001,
root 0x9f, subw 0x5400002, time 134756538, (33,44), root:(1728,1283),
state 0x0, keycode 64 (keysym 0xffe9, Alt_L), same_screen YES,
XLookupString gives 0 bytes:
XmbLookupString gives 0 bytes:
XFilterEvent returns: False
KeyPress event, serial 28, synthetic NO, window 0x5400001,
root 0x9f, subw 0x5400002, time 134756956, (33,44), root:(1728,1283),
state 0x8, keycode 40 (keysym 0x64, d), same_screen YES,
XLookupString gives 1 bytes: (64) "d"
XmbLookupString gives 1 bytes: (64) "d"
XFilterEvent returns: False
KeyRelease event, serial 28, synthetic NO, window 0x5400001,
root 0x9f, subw 0x5400002, time 134757034, (33,44), root:(1728,1283),
state 0x8, keycode 40 (keysym 0x64, d), same_screen YES,
XLookupString gives 1 bytes: (64) "d"
XFilterEvent returns: False
KeyRelease event, serial 28, synthetic NO, window 0x5400001,
root 0x9f, subw 0x5400002, time 134757134, (33,44), root:(1728,1283),
state 0x8, keycode 64 (keysym 0xffe9, Alt_L), same_screen YES,
XLookupString gives 0 bytes:
XFilterEvent returns: False
Thanks for trying to verify. Below are xev KeyPress and KeyRelease sequences for cases where HUD did and did not appear.
Since I've been using ubuntu/compiz/unity for a while, it seemed possible that I have some old config kruft that was necessary for this bug. I started up a guest session and indeed the problem does not appear.
So, my current hypothesis is that there is a user selectable delay buried somewhere that I configured long ago in a galaxy far far away. Any ideas where to look for that? Or, barring that, what config file to toss as a test?
xev data:
=======
Here's an xev sequence that caused the hud to appear.
KeyPress event, serial 28, synthetic NO, window 0x5400001,
root 0x9f, subw 0x0, time 134674304, (69,151), root:(1141,203),
state 0x0, keycode 64 (keysym 0xffe9, Alt_L), same_screen YES,
XLookupString gives 0 bytes:
XmbLookupString gives 0 bytes:
XFilterEvent returns: False
KeyPress event, serial 28, synthetic NO, window 0x5400001,
root 0x9f, subw 0x0, time 134674384, (69,151), root:(1141,203),
state 0x8, keycode 40 (keysym 0x64, d), same_screen YES,
XLookupString gives 1 bytes: (64) "d"
XmbLookupString gives 1 bytes: (64) "d"
XFilterEvent returns: False
KeyRelease event, serial 28, synthetic NO, window 0x5400001,
root 0x9f, subw 0x0, time 134674424, (69,151), root:(1141,203),
state 0x8, keycode 64 (keysym 0xffe9, Alt_L), same_screen YES,
XLookupString gives 0 bytes:
XFilterEvent returns: False
KeyRelease event, serial 28, synthetic NO, window 0x5400001,
root 0x9f, subw 0x0, time 134674442, (69,151), root:(1141,203),
state 0x0, keycode 40 (keysym 0x64, d), same_screen YES,
XLookupString gives 1 bytes: (64) "d"
XFilterEvent returns: False
And, for comparison, a sequence that didn't cause hud:
KeyPress event, serial 28, synthetic NO, window 0x5400001,
root 0x9f, subw 0x5400002, time 134756538, (33,44), root:(1728,1283),
state 0x0, keycode 64 (keysym 0xffe9, Alt_L), same_screen YES,
XLookupString gives 0 bytes:
XmbLookupString gives 0 bytes:
XFilterEvent returns: False
KeyPress event, serial 28, synthetic NO, window 0x5400001,
root 0x9f, subw 0x5400002, time 134756956, (33,44), root:(1728,1283),
state 0x8, keycode 40 (keysym 0x64, d), same_screen YES,
XLookupString gives 1 bytes: (64) "d"
XmbLookupString gives 1 bytes: (64) "d"
XFilterEvent returns: False
KeyRelease event, serial 28, synthetic NO, window 0x5400001,
root 0x9f, subw 0x5400002, time 134757034, (33,44), root:(1728,1283),
state 0x8, keycode 40 (keysym 0x64, d), same_screen YES,
XLookupString gives 1 bytes: (64) "d"
XFilterEvent returns: False
KeyRelease event, serial 28, synthetic NO, window 0x5400001,
root 0x9f, subw 0x5400002, time 134757134, (33,44), root:(1728,1283),
state 0x8, keycode 64 (keysym 0xffe9, Alt_L), same_screen YES,
XLookupString gives 0 bytes:
XFilterEvent returns: False