Super+F and Super+A used as custom shortcuts stop working when using laucher shortcut
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Unity |
Confirmed
|
Low
|
Unassigned | ||
unity (Ubuntu) |
Confirmed
|
Low
|
Unassigned |
Bug Description
Before upgrading from 10.10 to 11.10 I used a lot of shortcuts of the type Super+letter like Super+T for terminal and Super+F for Chrome. I also used Gnome Do with the shortcut Super+space for some other applications that I didn't have a shortcut for. Now, in 11.10, I modified the shortcut for the launcher from just Super to Super+space since it allows me to use Super for my old shortcuts and the dash menu replaces Gnome Do.
It works almost perfectly except that there is a weird behaviour with Super+F and Super+A (I'll only mention Super+F from now on for simplicity). When I login, Super+F works perfectly by opening a Chrome window each time. The problems start when I use the Super+space shortcut to call the launcher/dash menu, since Super+F will almost always stop working until I logout (sometimes it only happens at the second time I do Super+space)! Even weirder, it doesn't happen if I open the launcher or the dash menu with the mouse instead of the Super+space shortcut, i.e. Super+F keeps working in this case no matter how many times I open the dash menu.
My opinion is that this has something to do with the fact that Super+F and Super+A were shortcuts for the dash menu for searching files and folders and for applications, but they still work as Super+space+F(A) so its not like they are overriding my custom shortcuts...
Any idea why this is happening and how to correct this?
tags: | removed: maverick2oneiric |
tags: |
added: shortcut removed: shortcuts |
Please see related bug #880517 "CTRL+f shortcut does not work in any application after Oneiric upgrade" (a new Ctrl-f shortcut is mysteriously defined instead which causes an X-Terminal to open).
It would be very helpful to have further comments on that bug.
It is interesting that both this bug and #880517 seem to exist after a "double" dist-upgrade from 10.10 Maverick to 11.10 Oneiric (defined as no real usage of 11.04 Natty, except for the do-release-upgrade to 11.10), and in the case of #880517 it does not exist for a fresh installation of Oneiric or for a "single" dist-upgrade from 11.04 to 11.10.