Article 6QSSP Linuxmint MATE: Can't use Super+Up/Down to switch workspaces, why?

Linuxmint MATE: Can't use Super+Up/Down to switch workspaces, why?

by
noughtnaut
from LinuxQuestions.org on (#6QSSP)
Hi.
I've recently installed Linux Mint 22 ("Wilma"), come from Ubuntu (version 22.04). Both installations are of the MATE flavour.

- On Ubuntu, I have "Super+Up/Down" mapped to "Switch to workspace on the left/right of the current workspace", and this worked beautifully. I also have "Shift+Super+Up/Down" mapped to switching workspace while taking the current window with it.
- On LinuxMint, I can use "Keyboard Shortcuts" (mate-keybinding-properties) to specify the same keyboard shortcuts, but they do nothing. For now, as a work-around I have instead bound "Ctrl+Alt+Up/Down" but this really messes with my muscle memory (I've been using the Super key for many, many years).

As far as I know, it should be the same versions of the desktop environment, the keybinding program, etc. So why is it not working?

Here is my relevant keybinding (via "dconf dump / | grep to-workspace", with manual edits):

# These are found under "/org/gnome/desktop/wm/keybindings/"
# I don't know what "Prior" and "Next" even are...
switch-to-workspace-left=['<Super>Prior']
switch-to-workspace-right=['<Super>Next']
move-to-workspace-left=['<Shift><Super>Prior']
move-to-workspace-right=['<Shift><Super>Next']
#These and their siblings do nothing
switch-to-workspace-1=['<Super>Home']
move-to-workspace-1=['<Shift><Super>Home']

# These are found under "/org/mate/marco/global-keybindings/"
# This is my unhappy work-around because eg. '<Super>Up' doesn't work
switch-to-workspace-left='<Primary><Alt>Up'
switch-to-workspace-right='<Primary><Alt>Down'
move-to-workspace-left='<Primary><Shift><Alt>Up'
move-to-workspace-right='<Primary><Shift><Alt>Down'
# These work just fine
switch-to-workspace-1='<Mod4>1'
switch-to-workspace-2='<Mod4>2'
move-to-workspace-1='<Shift><Mod4>exclam'
move-to-workspace-2='<Shift><Mod4>quotedbl'

I saw a suggestion in a much older thread on another forum about the Compiz compositor, but I couldn't follow it because things now look very different than described. I don't know if or how it's relevant, but I have looked for conflicting keyboard bindings in "CompizConfig Settings Manager" (ccsm) but found no obvious culprit. I did disable the "Commands" plugin because it didn't seem to have anything configured anyway, and I have seen no change in behaviour from doing so.https://www.linuxquestions.org/quest...r-marker-2.pnghttps://www.linuxquestions.org/quest...r-marker-2.pnghttps://www.linuxquestions.org/quest...r-marker-2.png
External Content
Source RSS or Atom Feed
Feed Location https://feeds.feedburner.com/linuxquestions/latest
Feed Title LinuxQuestions.org
Feed Link https://www.linuxquestions.org/questions/
Reply 0 comments