Cannot move between workspaces using CTRL+ALT+<up/down arrows>

[Giovanni Mellini]

Ciao,
as the title says after upgrading from 13.04 to 13.10 I have some problem with workspaces.

In particular I cannot use anymore the shortcuts
- L_CTRL+ALT-<arrow down>
- L_CTRL+ALT-<arrow up>
to move up and down between workspaces.
The left and right shortcuts still work, so the problem is only with up/down arrows.

One more think to note that probably is related to the above.
The same happens while I try to move a windows to another workspace using keybord shortcut L_CTRL+L_SHIFT+ALT+<arrows>, only left and right arrows work, up/down no.
I tried to disable and enable workspaces from settings menu and tried to reset to default but is the same.

This is my unity version

giovanni@manta:~$ dpkg-query -l unity
Voluto=U (non noto)/I (installato)/R (rimosso)/P (rimosso totale)/H (in attesa)
| Stato=Non/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend
|/ Err?=(nessuno)/R (reinstallazione richiesta) (Stato,Err: maiuscolo=grave)
||/ Nome Versione Architettura Descrizione
+++-===================-==============-==============-===========================================
ii unity 7.1.0+13.10.20 i386 Interface designed for efficiency of space
giovanni@manta:~$

Tks
Giovanni

[Stephen M. Webb (bregma)]

I found my Desktop Wall setting in CCSM (Compiz Configuration Settings Manager) got changed somehow. I manually changed them back and the previous switching functionality was restored.

Can you please check the Bindings section of the Desktop Wall settings in the Compiz Configuration Settings Manager to make sure they are correct?

[Giovanni Mellini (merlos)]

Hi Stephen,
I found that my settings where changed during the upgrade process

This is how Section "Move within wall" appears
"Move up" binds to <Super>Prior
"Move down" dinds to <Super>Next

I resetted the bindings and now I can move between all the workspaces using L-CTRL+ALT+<arrows>
The same for section "Move with window within wall", I resetted the up/down bindings and now it works.

As I said this was due to an upgrade from 13.04 to 13.10 so I think that is better to assign the bug to the right owner to avoid this happening to other users during upgrade process.

Tks
Giovanni

[Doug McMahon (mc3man)]

marking as dupe to a 2.5 month old compiz bug on this
Note that this has nothing to do with upgrades per se, seen on fresh installs & all new user accounts