How to Fix a Frozen GNOME Desktop Session

If only one application is frozen, close that window if it still responds. If the whole GNOME desktop session has stopped responding, try the Xorg shell restart first. It works only in an Xorg session. On Wayland, or when GNOME is completely unresponsive, switch to a text console (TTY) and restart the graphical display manager. That last step logs you out of the graphical session, so unsaved work can be lost.

Before you restart: If the desktop briefly responds, save open documents. Restarting the display manager closes graphical applications and may end other users’ graphical sessions on a shared computer.

Check whether one app or the whole desktop is stuck

Look for signs that GNOME still accepts keyboard input: can you switch windows, open the Activities overview, or bring up the command runner? If one app alone is unresponsive, close that app if possible and leave the desktop session running. Use the recovery steps below when the panel, pointer, keyboard shortcuts, or multiple windows are stuck together.

Step 1: Restart GNOME Shell in an Xorg session

GNOME’s keyboard shortcut guide lists Alt+F2 as the command runner. If that dialog still opens, enter the single letter r and press Enter. This asks GNOME Shell to restart without restarting the computer.

This shortcut is not available for restarting Shell under Wayland; Red Hat’s GNOME and Wayland documentation lists that as a Wayland limitation. If the command dialog does not appear, or the session is Wayland, skip to the TTY method. Do not repeatedly enter r or try gnome-shell --replace as a universal fix.

Use a TTY for a Wayland or desktop-wide freeze

Step 2: Switch to a text console

Press Ctrl+Alt+F3. On some laptops, hold Fn as well. A black login prompt should appear. If it does not, try another function key such as F4 or F5; the available console numbers vary by distribution. The GNOME Boxes keyboard guide notes that Ctrl+Alt+F3 opens a virtual console and Ctrl+Alt+F1 returns to the desktop on many Linux distributions.

Type your Linux username and press Enter, then type your password and press Enter. The password field stays blank as you type; that is normal. If no TTY responds, see the last-resort section below.

Step 3: Restart the display manager

Once logged in, run this command on a system that uses systemd and has the standard display-manager unit:

sudo systemctl restart display-manager

Enter your account password if asked. The systemctl manual defines restart as stopping and then starting the named unit. For a display manager, this ends the current graphical session and starts the login service again. It does not reboot Linux, but it closes the applications in that session.

If systemd reports that display-manager.service does not exist, do not guess at a service name or run separate stop and start commands. Check your distribution’s documentation for the unit name used by its installed display manager. On a non-systemd distribution, use that distribution’s supported service controls instead.

Step 4: Return to the graphical login screen

After the command finishes, press Ctrl+Alt+F1 or Ctrl+Alt+F2. If you still see a text console, try the other key or cycle through the first few function keys until the graphical login screen appears. Sign in normally. The console mapping differs between distributions and versions, so there is no single return key that works everywhere.

If the TTY does not respond

If keyboard input works nowhere, the machine may be frozen below the desktop layer. If remote access such as SSH was already enabled and you know how to use it, you can run the same display-manager command from a trusted connection. Otherwise, a forced power-off may be the only remaining option. Hold the power button only as a last resort: it can discard unsaved work and interrupt disk writes. After restarting, let the system complete its normal startup and use your distribution’s recovery guidance if it reports filesystem or boot errors.

Reduce the chance of another GNOME freeze

If the problem started after installing or updating a Shell extension, disable that extension after you can log in. Red Hat’s extension management guide documents the gnome-extensions command. You can list extension IDs, then disable a suspected one:

gnome-extensions list
gnome-extensions disable EXTENSION-UUID

Replace EXTENSION-UUID with the exact ID shown by the first command. Disable one extension at a time so you can identify a cause. Also install operating-system and graphics-driver updates through your distribution’s normal update tools. If freezes continue, note what was happening just before each one and check your distribution’s support documentation or logs; repeated session restarts can restore the screen, but they do not fix an underlying driver, hardware, or extension problem.