"Initiate Window Move" can only be set to button 1

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).

I've had this problem too. ccsm insists on setting the binding to either Button3 or <Alt>Button3. If the value is anything but "<Alt>Button3", however, the Move Window is initiated when you click with Button1. BUT, if you hold down the Alt key in this state, the click will go through to the window (as an Alt-click).

Setting the value using gconf-editor does the same thing.

Thanks for taking the time to report this bug and helping to make Ubuntu better. You reported this bug a while ago and there hasn't been any activity in it recently. We were wondering is this still an issue for you? Thanks in advance.

We are closing this bug report because it lacks the information we need to investigate the problem, as described in the previous comments. Please reopen it if you can give us the missing information, and don't hesitate to submit bug reports in the future. To reopen the bug report you can click on the current status, under the Status column, and change the Status back to "New". Thanks again!.

I have changed the status of this bug back to new because it mirrors the problem that I am having. I am trying to set "Initiate Window Move" to "Button 8" for the "move" plugin, but every time I change it it doesn't go into effect and is reverted to either "<Alt>Button1" or "Button1" ("Button1" being overridden like this has its challenges!).

I am using the compizconfig-settings-manager to test this. I have also tried setting it using gconf-editor, but to no avail.

To recreate the bug just open ccsm, goto the "Move Window" options at the bottom, click the "Initiate Window Move" config button, unclick "Alt", and select a different available mouse button.

Interestingly, if I open compizconfig-settings-manager as root, the Button choice is saved correctly. But it isn't put into effect on my desktop (I assume that it is editing a gconf registry unique to the root user, so that makes sense).

Anyways, I think that this is an issue both because I want to customize this setting, but can't, and because it can override an unsuspecting user's Button1, with consequences that can be hard to undo.

Setting the "Window Menu" to "Button3" (as done by the conflict resolver sometimes) completely breaks the bindings. Button1 will result in "window move", Alt+Button1 in regular clicks. This is really ugly. Not sure if it's ccsm or compiz' fault.

I am also encountering this problem. It appears that ccsm (compizconfig-settings-manager) is forcing the window menu setting to what it thinks is the metacity default. Changing the metacity mouse_modifier setting with gconf-editor will work until ccsm is started again, at which point metacity/compiz acts as if the mouse modifier is "none". Using the keyboard to set the compiz Window Menu setting back to its default will restore default metacity(-like?) functionality.

I ran into this problem when I was trying to set up <Alt>Button2 as window menu and <Alt>Button3 as window resize. Metacity doesn't appear to provide an option for this, even in gconf-editor. A gconf-editor search for the text "Button3" only returned compiz keys. So I think this problem is potentially twofold: I think there's a deficiency in metacity because it doesn't allow one to completely disable or reassign the window click buttons (it only allows changing the modifier), and second, there's a deficiency in compiz or ccsm that causes the window modifier setting to go nuts.

The setting in ccsm is shown in blue instead of the normal text color, which I'm guessing means that the setting is unavailable or problematic. Another person had a problem with blue settings, referenced on the Ubuntu forums: http://ubuntuforums.org/showthread.php?t=559273

I can confirm this. I used to (back with Beryl) set my window move to Button 9. Now, in Compiz, I cannot set the mouse button for "Initiate Window Move" to anything but Button 1. If I try to set it to Button 9, it still grabs Button 1, and consequently I can't use my mouse normally.

There is a "resolution" at http://forum.compiz-fusion.org/showthread.php?p=60424

---Quote "maniac":
Disable the "Desktop environment integration" under Preferences in ccsm.
Metacity does not allow mouse button adjustments for Move-Resize-Window Menu, so with DE integration enabled, you can't change it in ccsm either.
---

I would say this is still a UI problem because the relation between DE integration and these options is not obvious.

But I believe there should be:
a) an "Override desktop manager integration/shortcut keys"
or
b) a user warning if they would like to do disable desktop environment integration

I now have a problem with 'Move Window' and 'Resize Window' plugins.
I changed the keyboard settings (as my middle mouse button is dying) to 'Super+Alt button 1' for move, and 'ctrl+alt button 1' for resize.

Actually now I cannot move or resize, and cannot use the keyboard shortcut Alt F7 either.

Other keyboard shortcuts are working fine.

Something else, which I'm not sure to say is a feature or bug, is that (having problems clicking my middle mouse button) I want to set 'move' and 'resize' windows. The two settings are linked, and cannot be set separately!

I want to set 'move' to 'ctrl+alt' button1, then 'resize' to 'ctrl+shift' button 1.

This is impossible - it appears that whatever keyboard shortcut I apply to 'resize' is instantly updated to 'move' also!

What exactly does the Desktop Integration do? I'm afraid that disabling it for one shortcut would do more damage then good.

may I suggest this be a duplicate for the "more then one shortcut" bug which number now escapes me. the one where you can write the mouse shortcut as "<Alt>Button1 | Button9"

This way, the desktop integration remains, and users can specify additional shortcuts in a consistent way for extra ones.

What is the status of this bug? Is no one working on it? I am new to Ubuntu, and one of the first things I tried to do is to assign window move to mouse button 9. But it doesn't work any better for me than for anybody else. If the plugin can't be made to work properly, wouldn't it be better to remove it altogether?

I am trying to set Initiate Window Move to Button5 or 6 (haven't been able to see which is more comfortable) .. and whaddya know- keeps changing back to Alt+Button1. This is the final obstacle in my "perfect" desktop configuration. Does anyone have a fresh link to a solution? The link posted a while back is dead.

This was working (bound to Button10) before I upgraded to Xubuntu 10.10, now no matter what I do it reverts to <Alt>Button1. As well if I set it to <Alt>Button3 it asks if I want to disable Window Menu that is already bound to <Alt>Button3, but when confirming this nothing has changed; still Alt+Button3 shows the menu and if I close and reopen the settings page, Initiate Window Move is back to <Alt>Button1.

Disabling desktop integration, importing from config file and restarting Compiz does finally allow me to use Button10 as I had been before.

This is still present in Ubuntu 12.10. I'm trying to disable "Initiate Window Move", but when I go back to the main menu and then back to "Move Window" it's enabled again. A "workaround" I found is to change the modifier from Alt to Shift-Control-Alt-Super (which I will never press or that no program will ask me to use).

Hmm, I could not reproduce this bug anymore.

In CCSM->Move-General->Initiate Window Move I can set any button-combi and it works perfectly...

@all affected running Raring:
Please try this PPA:
ppa:smspillaz/compiz-dev

and please report back, if you still can reproduce this issue...

Thank you for taking the time to report this bug. The compiz program that we currently use in Ubuntu is a C++ re-write of the original compiz and was announced the 4th July 2010. Therefore, the bugs that were reported before that date, will be marked as "Won't Fix" as they probably exist in the original program which is not stored in launchpad. (The last LTS that used the old compiz is the 10.04 which is not supported anymore).