"Initiate Window Move" can only be set to button 1
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Compiz |
Won't Fix
|
Medium
|
MC Return | ||
compiz (Ubuntu) |
Won't Fix
|
Low
|
Unassigned | ||
Bug Description
Binary package hint: compiz
This is dependent on some option being set, as I've accidentally triggered this before and managed later to clear it; I'm trying to do the same now, but whatever it is I *certainly* didn't select any option that read anything like "Initiate Window Move" "Button1" :-)
It *may* be relevant that the "Window Menu" binding in ccsm keeps reverting to "Button3" no matter what I put in it, including if I change it directly in GConf.
This did appear just after I tried to use GL Desktop. Clearly a mistake; but it persists after that, including beyond a log-out and log-in cycle, and is still the case even if I choose Normal or Extra in Visual Effects, not only Custom.
If Compiz is off, everything's fine.
Changed in compiz: | |
importance: | Undecided → Low |
summary: |
- Compiz, Button 1 mouse clicks in windows intiates window drag + "Initiate Window Move" can only be set to button 1 |
Changed in compiz (Ubuntu): | |
status: | Confirmed → Triaged |
Changed in compiz: | |
milestone: | none → 0.9.10.0 |
Changed in compiz: | |
importance: | Undecided → Medium |
milestone: | 0.9.10.0 → 0.9.11.0 |
assignee: | nobody → MC Return (mc-return) |
Can be cleared by double-clicking on the mouse button setting in ccsm, clicking on the button to reset it to the default then (in my case) clearing the keyboard short-cut because I wanted to use it for something else. Typing <Alt>Button3 into the main ccsm screen field wouldn't work, nor into GConf; but the reset does it.
(Note, I hadn't changed that keyboard shortcut just prior to it going wrong - rather I'd done that days earlier.) I still think it's something that the gnome-compiz- manager did, as it happened after I tried to run that, and that also messed up some of my other settings.
Now I can return to the problem for which I was *about* to place a bug report before this happened (which was why I was messing with settings).