The workspace problem
You just migrated from Windows or macOS. You hit the Super key, see the grid of windows, and expect to click a Desktop 2 button. There is no button. You try Ctrl+Alt+Arrow and nothing happens. Your terminal, browser, and file manager are all fighting for the same screen real estate. You need separation. GNOME gives it to you, but it works differently than what you are used to.
How GNOME actually handles virtual desktops
GNOME treats workspaces as a dynamic canvas, not a fixed set of slots. Traditional desktop environments allocate four or eight static desktops. GNOME creates a new workspace the moment you push a window into it, and destroys it when the last window leaves. This matches how developers actually work. You open a project, spawn a terminal, pull up documentation, and push them to a fresh space. When you close the project, the space vanishes. You never run out of desktops. You never waste time switching through empty ones.
The system tracks window placement through the Mutter window manager. Mutter handles compositing, animations, and workspace assignment. It listens to keyboard events, maps them to actions, and updates the session state. When you press a shortcut, Mutter moves the window or switches the view. It does not require a background daemon or a configuration file. The behavior is baked into the shell.
GNOME stores your workspace preferences in the GSettings database. The database lives in ~/.config/dconf/user and syncs with the running session. This is a Linux convention: user configuration stays in the home directory. System defaults live in /usr/share/glib-2.0/schemas/. Never edit the system schemas. They will be overwritten during package updates. Edit your local dconf database instead.
Reboot before you debug. Half the time the symptom is gone.
The native workflow
Start with the keyboard. GNOME reserves the Super key for workspace navigation. Use these combinations to move around without touching the mouse.
# Switch to the workspace above or below the current one
# Super + Page Up / Page Down
# WHY: Moves your view up or down the workspace stack. Keeps your hands on the home row.
# Jump directly to workspace number one through nine
# Super + Alt + 1 / Super + Alt + 2 / ... / Super + Alt + 9
# WHY: Bypasses sequential switching. Useful when you have a dedicated terminal workspace at number two.
# Move the focused window to the workspace above or below
# Super + Shift + Page Up / Page Down
# WHY: Transfers the window without changing your current view. Lets you organize while staying on the active space.
Trackpad gestures are the modern standard. Swipe up with three fingers to open the Activities overview. Swipe down with three fingers to show the current workspace. Swipe left or right with three fingers to move between workspaces. The gesture engine lives in libinput and maps directly to Mutter. If your trackpad supports it, gestures are faster than memorizing modifiers.
You can force static workspaces if you prefer a fixed grid. GNOME stores this preference in the GSettings database. Change the value to lock the number of desktops.
# Check the current workspace behavior
gsettings get org.gnome.mutter dynamic-workspaces
# WHY: Returns true by default. Confirms whether GNOME creates spaces on demand or uses a fixed count.
# Switch to a fixed number of workspaces
gsettings set org.gnome.mutter dynamic-workspaces false
# WHY: Disables automatic creation. Forces GNOME to keep the exact number you define.
# Set the fixed count to four desktops
gsettings set org.gnome.desktop.wm.preferences num-workspaces 4
# WHY: Defines the exact grid size. GNOME will never create a fifth space until you change this value.
Reboot is not required. The shell reads the new values immediately. Open the Activities overview to see the change take effect.
If you prefer a graphical interface over the terminal, install dconf-editor. It reads the same database and applies changes instantly. Run sudo dnf install dconf-editor to get it. Navigate to /org/gnome/mutter/dynamic-workspaces to toggle the behavior. The GUI and the CLI modify the exact same keys. Pick the tool that matches your workflow.
Run journalctl first. Read the actual error before guessing.
Verify your setup
Run a quick test to confirm the shortcuts and settings are active. Open three terminal windows. Push the first to workspace two using Super+Shift+Page Down. Push the second to workspace three. Switch to workspace two with Super+Alt+2. Verify the terminal appears. Switch back to workspace one. The original terminal should still be there. If the windows stay put and the view switches cleanly, the configuration is working.
Check the GSettings database directly if you suspect a GUI tool overwrote your changes.
# List all workspace-related keys in the current session
gsettings list-recursively | grep -E "workspace|num-workspaces"
# WHY: Dumps the active configuration. Lets you verify that dynamic-workspaces and num-workspaces match your intent.
Multi-monitor setups require extra attention. GNOME treats each monitor as an independent workspace stack by default. This means Super+Page Up moves you vertically on the current screen, not across screens. If you want a single unified workspace across all monitors, change the span setting.
# Enable a single workspace that spans all connected displays
gsettings set org.gnome.mutter edge-tiling true
# WHY: Keeps window snapping behavior consistent across the entire virtual desktop area.
# Disable per-monitor workspace isolation
gsettings set org.gnome.shell.overrides workspaces-only-on-primary false
# WHY: Forces GNOME to treat all monitors as one continuous canvas. Prevents accidental window loss when dragging across screens.
The change applies immediately. Drag a window from the left monitor to the right monitor to confirm it stays on the same workspace layer.
Snapshot the system before the upgrade. Future-you will thank you.
Common pitfalls and broken shortcuts
The most frequent issue is a conflicting keybinding. Third-party tools, gaming launchers, or clipboard managers often hijack Super+Shift+Arrow or Super+Page Up. GNOME will silently ignore the shortcut if another process claims it. Run the keybinding query to find the collision.
# Search for any active binding that uses Super and Page Up
gsettings list-recursively | grep -i "super.*page"
# WHY: Shows which schema owns the shortcut. Helps you identify rogue extensions or custom scripts.
Extensions are the second culprit. Window grid, patchwork, or tiling extensions modify Mutter's default behavior. Some extensions disable dynamic workspaces entirely. Others replace the Activities overview with a custom launcher that breaks gesture routing. If your shortcuts stop working after installing an extension, disable it and test again. GNOME extensions run as separate processes. They can crash without taking down the shell, but they often leave the session in a half-configured state.
You will occasionally see this error in the journal when an extension fails to load:
gnome-shell[1234]: Extension "workspace-grid@some-author" had error: TypeError: workspace is undefined
The error means the extension expects a fixed workspace array but GNOME is running in dynamic mode. Disable the extension or switch to static workspaces. Do not edit the extension JavaScript files manually. They will be overwritten on the next GNOME update.
Trackpad gestures sometimes fail on older hardware. The gesture engine requires a multitouch surface that reports at least three simultaneous contacts. If swiping does nothing, check the libinput configuration.
# Verify your trackpad is recognized as a multitouch device
libinput list-devices | grep -A 5 "Touchpad"
# WHY: Shows the device capabilities. Confirms whether the hardware supports three-finger gestures.
If the device shows Capability: clickfinger or Capability: gesture, the hardware is fine. The issue is likely a driver quirk or a conflicting input method. Reset the input configuration to defaults and test again.
SELinux denials rarely affect workspace navigation, but they can block dconf-editor or gsettings from writing to ~/.config/dconf/user. If you see permission errors when changing workspace settings, check the audit log.
# Check for recent SELinux denials related to dconf or gsettings
journalctl -t setroubleshoot | tail -n 20
# WHY: Shows one-line summaries of blocked operations. Lets you restore context without disabling SELinux.
Restore the correct context with restorecon -Rv ~/.config/dconf/ if the permissions are wrong. Never disable SELinux to fix a configuration tool. Fix the context instead.
Trust the package manager. Manual file edits drift, snapshots stay.
When to stick with defaults versus when to extend
Use the native dynamic workspace system when you want zero configuration and automatic cleanup. Use static workspaces when you run a fixed set of applications and need predictable numbering for scripts or window managers. Use trackpad gestures when you have a modern laptop and want muscle-memory navigation. Use keyboard shortcuts when you are on a desktop machine or using a low-latency wireless keyboard. Use GNOME extensions only when you need tiling behavior, persistent workspace names, or custom window snapping. Stick to the default shell if you only deviate from the layout occasionally.