move window to workspace shortcut keys don't work

[kevmitch]

No matter what shortcut key combination I set in gnome-keybinding-properties, it seems that the "Move Window to Workspace #" shortcuts will not work. The keys combinations appear to be ignored by the window manager.

[Sebastien Bacher (seb128)]

thank you for your bug report, what ubuntu version do you use? do you use the desktop effects option?

[kevmitch (kevmitch)]

I am using Jaunty Jackalope. I have the default desktop effects option selected (i.e., I'm using compiz with minimal effects).

[Hugh Blemings (hughhalf)]

Can confirm this behaviour under fresh Jaunty Beta install as reported by kevmitch as well as on an older Intrepid install:

If "Visual Effects" is set to anything other than "None" have observed the following:

* Moving a window to a new Workspace directly by using a numeric shortcut (e.g. assigning Shift-Ctrl-F1, Shift-Ctrl-F2 etc.) key does not work. Moving the window to a different Workspace using Shift-Ctrl-Alt-Left, Shift-Ctrl-Alt-Right etc. _does_ work as expected.

* Even if more than two Workspaces as assigned using the Workspace Switcher, there is no option to assign shortkeys for Workspaces beyond 1 and 2 in the Keyboard Shortcuts Menu unless these options were already present (see below)

If "Visual Effects" is set to "None" the following is observed:

* All shortcut keys to move windows to different Workspaces function as expected.

* The option in Keyboard Shortcuts to set shortcuts for selecting and moving windows to Workspaces beyond 1 & 2 appears if more than 2 Workspaces are setup in the Workspace Switcher. If assigned, these shortcut keys persist, but will only work if Visual Effects is "None"

[Sebastien Bacher (seb128)]

the issue seems rather to be a wm one that a GNOME bug, you might want to check that the GNOME compatibility option is on in the compiz config

[Hugh Blemings (hughhalf)]

installed compizconfig-settings-manager and ran ccsm (thanks for the pointer Sebastien!) and confirm gnome compatability is checked.

Will dig into this further as time permits.

[Hugh Blemings (hughhalf)]

One possible workaround seems to be as follows:

* Install compiz-config-settings-manager (ccsm)

* Run ccsm

* Under the Window Manager options, enable "Put"

* Under the "Put" configuration options, locate "Put to Arbitrary Viewport"

* For each desired viewport (desktop) assign an appropriate key combination (Personally I used Ctrl-Shift-F1, Ctrl-Shift-F2 etc.)

Drawback with this approach is that when the window is moved, the selected viewport moves too - so you jump to the new location of the window which may or may not be desirable.

Will continue to dig into the "real" fix for this.

Thanks again to Sebastien

[Petr Dlouhý (petr-dlouhy)]

The bug seems to be still present in Karmic.

[Serguei Pachtchenko (pachtchenko)]

When using using Compiz's "Put" workaround described above by Hugh Blemings:
to avoid automatically jumping to the new viewport when moving a window, enable "Unfocus Window" in "Put"/"Misc. Options"

[jepler (jepler)]

Affects Lucid as well.

Why in the world is "an option shown in a core configuration dialog should actually work" a *wishlist item*? If you don't intend to make it work for all Visual Effects settings, take it out of Keyboard Shortcuts.

[jk (mail-j-k)]

This bug is still present in Maverick...

[jk (mail-j-k)]

Concerning the workaround proposed by Hugh Blemings: If you set it up this way with the compiz config manager and enable "Unfocus window" in the "Misc. Options" tab, the viewport doesn't move, so the behavior is what you would expect from the "Move window to workspace" events.

[malraux (scottanderson42)]

Does not work in Natty either.

I just upgraded from Gutsy, where it worked fine. How is something going from "works" to "doesn't work" considered wishlist?

The workaround "works" for sufficiently "will only put windows to workspace 2 no matter which one is actually being sent to" values of "works"...

[Ernesto Alfonso (erjoalgo-u)]

Workaround simply does not work for me. After enabling put and specifying the key bindings, those key bindings do nothing.

[Ernesto Alfonso (erjoalgo-u)]

Actually, the (incorrect, useless) behaviour is as malraux specified. All windows are moved to the same workspace, top-right.

[dansheen (dansheen)]

Actually, compiz w/ cssm is NOT an option: https://bugs.launchpad.net/ubuntu/+source/compiz-fusion-plugins-main/+bug/684019
Me too, I believe this should not be a Wishlist item.

[Jesse Johnson (holocronweaver)]

This has all the makings of a bug. A certain behaviour is implied to the user but fails to be provided. Either remove it from the shortcuts menu or make it work. It worked in 8.10, but has been uneven ever since. Rarely I can get the shortcuts to work, but they are not always responsive. This is especially true when moving Firefox windows where addons seem to compete with Ubuntu for key grabs.

[ErikMn (erik-m85)]

Is there some configuration file I could attach to help a maintainer/compiz-developer to verify this? Or is it verified but no one interested/able to fix it?

Since 6 people wrote along the lines of "this is a bug, not wishlist" during the 21 months since Travis set it to "wishlist" and I haven't seen any progress, I would like to change status to bug but it seems I don't have permission to do so (or just can't find how to do it). Since it is open source I suppose I should dig into the code rather than rant, though...

I got hit by this when I upgraded to a clean install of 11.04, which is now running with the classic Gnome look with Compiz. I tried setting the shortcuts using the core settings->keyboard shortcuts and via CCSM, and using one of them at a time to avoid interference. I managed to get the "can move window to viewport 2" behaviour described in https://bugs.launchpad.net/ubuntu/+source/compiz-fusion-plugins-main/+bug/684019 but moving to other workspaces (Ctrl+Alt+Numpad1 or 3) does not work for me.

[Robert Roth (evfool)]

Thank you for taking the time to report this bug and helping to make Ubuntu better. This particular bug has already been reported and is a duplicate of bug #898087, so it is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Feel free to continue to report any other bugs you may find.

PS: I am marking this (the older) bug as a duplicate of the other (newer) bug as the other one has multiple projects affected and is assigned to a developer and should be taken care of for the next version, Precise.