Ubuntu Shutdown Screen Explained, Step by Step

Ever clicked shut down, then stared at the same screen for what felt like forever? Your Ubuntu machine is working through a checklist: closing apps, saving state, and stopping services before the power goes off.

The shutdown screen is your window into that process.

Here’s a plain look at what that screen shows, how to power off from the desktop or the terminal, and what to try when it refuses to finish. Along the way we’ll touch on tuning the power menu and reading shutdown logs.

Why the Ubuntu Shutdown Screen Freezes

A shutdown that hangs looks almost finished, which makes it hard to know when to stop waiting.

How the freeze shows up

The symptom is a frozen shutdown splash, the Ubuntu screen that stays up while progress never finishes. On Ubuntu 24.04 LTS with GNOME on Wayland, the hang can stay frozen for hours.

A forced long press of the power button works in a pinch, but it skips the clean shutdown steps, so it’s a stopgap, not a fix. Treat it as a last resort.

Hardware, kernel, and GNOME details

Gather these before you test anything:

• Hardware model and specs: list the exact model, CPU, graphics, and drive type.
• Kernel and GNOME version: run uname -r and gnome-shell --version.
• Windowing system: run echo $XDG_SESSION_TYPE, which should print wayland.

Fixes tried and what happened next

Pressing Esc during the splash reveals the detail messages, so screenshot them while they’re visible.

Disabling the snapd service was the next thing tried. The problem persisted, so snapd wasn’t the fix.

The systemd journal keeps logs, and journalctl -b -1 reads the previous boot’s entries, including the shutdown messages from the hung session.

If one service stalls the shutdown, lower the stop-job timeout by setting DefaultTimeoutStopSec to a shorter value in /etc/systemd/system.conf. That makes systemd give up on the stuck service sooner.

Consider a student whose ten-year-old laptop still hangs. A screenshot plus the journalctl -b -1 output gives a helper something specific to work with, not just ‘it freezes.’

If you’d rather restyle the splash, Plymouth draws it. List themes with sudo plymouth-set-default-theme -l, then run sudo update-initramfs -u so your pick loads at boot.

How Logind Handles Power Button Events

Your power button hands its press to systemd-logind, the service that manages power events. Here’s what we’ll check.

Power key options in logind.conf

Settings live in /etc/systemd/logind.conf. The key one is HandlePowerKey, which takes three values:

• poweroff: shut down (the default)
• suspend: sleep instead
• ignore: do nothing

Think of a student on an old ThinkPad whose power button sits by the keyboard. Setting HandlePowerKey=ignore stops a stray press from shutting down mid-essay.

HandleLidSwitch (closing the lid) and HandleRebootKey (the reboot key) follow the same pattern. Put edits in a drop-in under /etc/systemd/logind.conf.d/, then run sudo systemctl restart systemd-logind.

Checking which inhibitor locks block shutdown

An inhibitor lock is a program’s way of saying wait. Low-level locks come straight from systemd-logind, while high-level locks come from your desktop session.

Run systemd-inhibit --list to see who holds a lock and why. Scripts can make the same D-Bus call with busctl call org.freedesktop.login1 /org/freedesktop/login1 org.freedesktop.login1.Manager ListInhibitors.

For permissions, pkaction | grep login1 lists the PolicyKit actions behind logind. Start there.

How GNOME can get in the way

GNOME takes its own locks at startup, so they can appear in the list you just checked. The gsd-media-keys component can also block logind from handling the power key.

By default, a press on Ubuntu’s GNOME desktop shows a shutdown confirmation dialog instead of powering off at once. That’s your accidental press protection: a moment to cancel. GNOME is asking before you power off, while logind is acting on the press.

Power menu extensions can add or change entries too, so if shutdown acts strangely, disable extensions one at a time.

How to Immediately Shut Down Ubuntu?

To power off Ubuntu, use the power menu in the top-right corner or a single terminal command. Here’s how the common commands compare:

• sudo shutdown now: powers off right away after your password.
• sudo poweroff: same job, fewer words.
• systemctl poweroff: asks systemd, the service manager, to do it.

Is sudo shutdown now safe? Safe enough, but it won’t ask you to confirm, so save your work first. On the lock screen, click the power icon in the corner; it usually offers the same menu.

Boot into multi-user.target without the GUI

Booting into multi-user.target, the old runlevel 3 with no graphical user interface (GUI), gives you a plain text console.

Add systemd.unit=multi-user.target to GRUB_CMDLINE_LINUX in /etc/default/grub (the settings for GRUB, the boot loader), then run sudo update-grub. It’s a reversible change, not a permanent one: undo the edit, rerun update-grub, and the desktop returns.

Denying power actions with a PolicyKit rule

PolicyKit (polkit) decides who may power off.

Older releases read PKLA files (an older rule format) in the localauthority directory, while newer ones want JavaScript rules, so it’s less about writing the rule and more about which format your version reads.

A wildcard can match every inhibit-handle action at once. Test with dbus-send, a command-line tool, to confirm a restricted user gets refused. A parent on a shared family desktop might block a kid’s account from powering off mid-download.

We haven’t tested the JavaScript variant, so treat it as a starting point.

Blocking inhibit calls through D-Bus

D-Bus is the message bus desktop parts use to talk. Apps call its Inhibit() member for a sleep or lock hold, so denying that member in a policy file blocks the request. Reload the D-Bus service to apply it.

Blocking the call is the easy part, but the side effects matter: some desktop features rely on those holds, so locking and sleep can misbehave. To limit it, scope the policy to the gdm user, the GNOME login screen account.

Changing the button action with gsettings

gsettings is the command-line tool for GNOME settings, including the power button. Its allowed values are limited, and poweroff isn’t one of them, so pick from the list. For the login screen, repeat it as the gdm user.

You’ll also need the dbus-x11 package, or gsettings may refuse to run. Install it first.

A shutdown that hangs is frustrating, but it’s usually a solvable problem. Start with the simple GUI or command options, check the logs when something stalls, and then work on making the power menu feel like yours.

Once you know where to look, a stubborn shutdown stops being a mystery and becomes a quick fix. You’ll have a clear path from the first click to a clean power-off every time.

Your desktop should feel like yours, and it should power off cleanly every time you ask it to.