On 02/20/2012 02:42 PM, Dean Henrichsmeyer wrote:
> @ Doug (mc3man) I don't follow. I don't use ccsm, tilda, or others.. I
> only use the keyboard shortcuts in system settings. I have one precise
> machine in which Ctrl-arrow switches workspaces just fine and one that
> does not. It stopped working when this bug was introduced.
>
> Are you saying that bug 931601 is the culprit?
>
Dean - not at all. Your previous made it seem possible you were using
ccsm to set the mentioned binding.
I was commenting that one can't set a binding for key combo in ccsm if
the use the Ctrl key while doing so.
It will be inputed as <Primary> which will be ignored and the remainder
of the set combo will be the actual binding. (Same thing happens in Tilda
On 02/20/2012 02:42 PM, Dean Henrichsmeyer wrote:
> @ Doug (mc3man) I don't follow. I don't use ccsm, tilda, or others.. I
> only use the keyboard shortcuts in system settings. I have one precise
> machine in which Ctrl-arrow switches workspaces just fine and one that
> does not. It stopped working when this bug was introduced.
>
> Are you saying that bug 931601 is the culprit?
>
Dean - not at all. Your previous made it seem possible you were using
ccsm to set the mentioned binding.
I was commenting that one can't set a binding for key combo in ccsm if
the use the Ctrl key while doing so.
It will be inputed as <Primary> which will be ignored and the remainder
of the set combo will be the actual binding. (Same thing happens in Tilda