How to Fix a Black Screen After Login on Linux

You type your password, hit Enter, and the screen goes dark. No desktop, no panel, maybe a blinking cursor or a mouse pointer floating in a void. It looks like the whole install died.

It almost never did. Your files are on the disk, and the fault usually sits in the graphics path: a GPU driver, a stale config file, or a full disk. This guide on How to Fix a Black Screen After Login on Linux walks through the causes in order of likelihood, with commands for each major distro, so you can stop guessing.

Quick Triage: Match Your Symptom to a Fix

What you see	Most likely cause	Go to
Black screen plus movable cursor	Compositor or config crash	Quick wins
Black screen right after a kernel update	NVIDIA module not rebuilt	Driver fixes
Login loops back to the password box	Full disk or wrong file ownership	Terminal checks
Black after waking from sleep	Wayland/NVIDIA resume bug	What changed in 2026
Works with nomodeset only	GPU driver problem	Driver fixes
Only the laptop fails, desktop PC fine	Hybrid graphics	Hybrid laptops
Black after a distro upgrade	Wrong driver branch or half-finished upgrade	Rollbacks

What Changed in 2026

Two shifts made this problem more common this year.

GNOME 50 is Wayland-only. Ubuntu 26.04 LTS “Resolute Raccoon” (released April 23, 2026) ships GNOME 50 and Linux kernel 7.0, and it’s the first Ubuntu LTS where the default GNOME session is Wayland-only. The old “pick Xorg from the gear icon” escape route is gone on the standard desktop. Ubuntu’s known-issues list also notes suspend/resume display corruption on some NVIDIA desktops under Wayland.

Older NVIDIA cards moved to legacy branches. Fedora 44 community threads show a repeating pattern: someone upgrades, the newest NVIDIA driver no longer supports their older card, and they land on a black screen. Helpers keep pointing them to RPM Fusion’s 580xx legacy packages.

Debian is the calm one. Debian 13 “trixie” is at point release 13.6 (July 11, 2026), with full support until August 9, 2028 and LTS until June 30, 2030.

Step 1: Get a Terminal and Run Three Checks

Don’t reinstall anything yet.

1. Press Ctrl + Alt + F3 (try F2 to F6 if needed) and log in at the text prompt.
2. If that fails, reboot, open GRUB (hold Shift on BIOS, tap Esc on UEFI), choose Advanced options, and boot a recovery entry or an older kernel.

Then run:

df -h                      # is / or /home at 100%?
ls -l ~/.Xauthority        # should be owned by YOU, not root
journalctl -b -p err       # errors from this boot

Disk full? Free space with sudo apt clean, sudo dnf clean all, sudo pacman -Sc or sudo zypper clean, then remove old logs and downloads. A session can’t start with nowhere to write.

Wrong ownership? This often follows running a graphical app with sudo:

sudo chown -R $USER:$USER ~

Reboot. If the desktop returns, you’re done.

Read the journal, don’t guess

journalctl -b | grep -iE "nvidia|nouveau|amdgpu|i915|gdm|sddm|lightdm|mutter|kwin"

• NVRM or nvidia errors: driver or module problem
• Module not found: kernel and driver mismatch
• Failed to start Display Manager: the login manager itself is broken
• No space left on device: self-explanatory

Step 2: Quick Wins Before Touching Drivers

Move config aside, don’t delete it:

mv ~/.config/monitors.xml ~/.config/monitors.xml.bak
mv ~/.config/dconf ~/.config/dconf.bak     # GNOME
mv ~/.config/plasma-org.kde.plasma.desktop-appletsrc ~/.config/plasma.bak   # KDE

You’ll lose custom panel layouts but keep your files.

Create a throwaway user to learn whether the fault is system-wide or just your profile:

sudo adduser testuser      # Debian/Ubuntu; use "sudo useradd -m testuser && sudo passwd testuser" elsewhere

If testuser logs in fine, your own config is the problem.

Restart or reinstall the display manager:

sudo systemctl restart gdm        # gdm3 on Debian/Ubuntu
sudo systemctl restart sddm       # KDE
sudo systemctl restart lightdm    # Mint, Xfce, Cinnamon, MATE

If that fails, reinstall it: sudo apt install --reinstall gdm3, sudo dnf reinstall gdm, sudo pacman -S gdm or sudo zypper in -f gdm.

Step 3: Fix the Graphics Driver

First confirm the diagnosis. At GRUB press e, find the line starting with linux, add nomodeset at the end, and press Ctrl + X. If the desktop appears at low resolution, your GPU driver is the culprit. Use that session to fix it properly rather than living with it.

NVIDIA, by distro

Ubuntu 26.04 LTS and Ubuntu-based (Kubuntu, Pop!_OS, Zorin):

ubuntu-drivers devices
sudo ubuntu-drivers install
sudo reboot

If you ever installed a .run file from NVIDIA’s site, remove it first with sudo nvidia-uninstall. Mixing packaged and manual drivers is a classic trap.

Linux Mint: Open Driver Manager (reachable via nomodeset), pick the recommended proprietary driver, apply and reboot. Timeshift is also your quickest undo if an update caused it.

Debian 13 “trixie”: Enable non-free and non-free-firmware in your APT sources, then:

sudo apt install nvidia-detect
nvidia-detect
sudo apt install nvidia-driver
sudo reboot

Fedora 44: Current cards use the standard RPM Fusion package:

sudo dnf install akmod-nvidia xorg-x11-drv-nvidia-cuda

Older cards (community reports point to the GTX 10-series and earlier) need the legacy branch:

sudo dnf remove akmod-nvidia
sudo dnf install akmod-nvidia-580xx xorg-x11-drv-nvidia-580xx-cuda

Wait a few minutes before rebooting. The akmod system builds the kernel module in the background, and an early reboot is why many people think the driver “failed.” Confirm with modinfo -F version nvidia first.

Arch and Arch-based (EndeavourOS, Manjaro):

# Default "linux" kernel, Turing (RTX 20-series) and newer:
sudo pacman -S nvidia-open nvidia-utils
# Any other kernel (lts, zen, custom):
sudo pacman -S nvidia-open-dkms nvidia-utils linux-headers
sudo mkinitcpio -P

Pre-Turing cards need a legacy driver from the AUR. The Arch Wiki’s NVIDIA page lists which package matches which generation. If a fresh pacman -Syu caused the break, downgrade the package from /var/cache/pacman/pkg.

openSUSE Tumbleweed and Leap: Add NVIDIA’s official repository via YaST or zypper, install the matching driver and reboot.

Secure Boot can silently block the driver

If Secure Boot is on, an unsigned NVIDIA module won’t load, and you get a black screen with no obvious error. Check:

mokutil --sb-state

• Ubuntu and Mint prompt you to create a MOK password during driver install. Reboot, choose Enroll MOK, and enter it.
• Fedora needs the akmods key: sudo kmodgenca -a, then sudo mokutil --import /etc/pki/akmods/certs/public_key.der and reboot to enroll.
• Or disable Secure Boot in firmware as a quick test.

Turn on DRM modesetting for Wayland

Most packages enable it automatically. If yours didn’t, add nvidia-drm.modeset=1 to GRUB_CMDLINE_LINUX_DEFAULT in /etc/default/grub, then regenerate GRUB: sudo update-grub (Debian family), sudo grub2-mkconfig -o /boot/grub2/grub.cfg (Fedora, openSUSE) or sudo grub-mkconfig -o /boot/grub/grub.cfg (Arch).

AMD and Intel

These use open drivers in the kernel and Mesa, so black screens usually mean missing firmware or a partial upgrade.

• Debian/Ubuntu: sudo apt install --reinstall linux-firmware mesa-vulkan-drivers && sudo update-initramfs -u
• Fedora: sudo dnf reinstall linux-firmware mesa-dri-drivers && sudo dracut -f
• Arch: sudo pacman -S linux-firmware mesa && sudo mkinitcpio -P

If it began after a kernel update, boot the previous kernel from GRUB. If that works, wait for a fixed kernel.

Hybrid laptops (Intel or AMD plus NVIDIA)

Force one GPU to test. On Ubuntu-based systems, sudo prime-select intel (or nvidia) then reboot. Elsewhere, EnvyControl or supergfxctl do the same job.

Step 4: Wayland vs Xorg Fallbacks

Your escape route depends on your desktop.

• Ubuntu 26.04 GNOME and other GNOME 50 distros: There’s no Xorg session. Fall back to another kernel, another driver version, or a second desktop such as Xfce installed alongside.
• GNOME 49 and older: Set WaylandEnable=false under [daemon] in /etc/gdm3/custom.conf (or /etc/gdm/custom.conf on Fedora) to force Xorg. This option has no effect once your GNOME no longer ships an X11 session.
• KDE Plasma: If the Plasma X11 session package is installed, you can pick it from the SDDM session menu. From a console, the last-used session is stored in /var/lib/sddm/state.conf, so you can point it at the X11 session file there. If the package isn’t installed, Plasma may not offer an X11 session at all in your version.
• Xfce, Cinnamon, MATE: These still run on X11 by default, which is partly why they survive NVIDIA problems better.

Step 5: Roll Back When Fixing Takes Too Long

Distro	Best rollback	Driver tool	Usual login manager	Difficulty
Ubuntu 26.04 LTS	Older kernel from GRUB, apt downgrade	ubuntu-drivers	GDM	Easy
Linux Mint	Timeshift snapshot	Driver Manager	LightDM	Very easy
Fedora 44	dnf history undo, older kernel	RPM Fusion akmod	GDM or SDDM	Moderate
Debian 13.6	Older kernel, apt pinning	nvidia-detect	GDM	Moderate
Arch / EndeavourOS	Downgrade from pacman cache	nvidia-open or AUR legacy	Varies	Hard
openSUSE	Snapper Btrfs rollback	NVIDIA repo + zypper	SDDM or GDM	Easy

On openSUSE, sudo snapper rollback plus a reboot undoes a bad update in minutes. On Fedora, sudo dnf history list then sudo dnf history undo <ID> reverses one transaction.

Which Recovery Approach Should You Pick?

Fixing the GPU driver

• Pro: solves the root cause in most NVIDIA cases and survives updates
• Con: the wrong branch or Secure Boot blocking the module leaves you stuck

Booting an older kernel

• Pro: one minute, and no packages change
• Con: skips security patches and doesn’t help if the driver is at fault

Snapshot rollback

• Pro: reverses config and packages together
• Con: only works if you set snapshots up beforehand

Common Patterns From the Community

These show up again and again in forum reports and are worth recognising.

• “I upgraded Fedora and now it’s black.” Usually an older NVIDIA card that now needs the 580xx branch.
• “I installed the driver and rebooted at once.” The akmod build hadn’t finished, so the module never existed.
• “It works on Mint live USB but not my install.” A leftover manual driver or stale config in the installed system.

Last Resorts

1. Reinstall the desktop meta-package (sudo apt install --reinstall ubuntu-desktop, task-gnome-desktop on Debian, or sudo dnf group install workstation-product-environment on Fedora).
2. Finish a broken upgrade: sudo dpkg --configure -a && sudo apt -f install, or sudo dnf distro-sync.
3. Install a lightweight second desktop to get a working session.
4. Back up from a live USB before anything drastic. It costs ten minutes and removes the fear.
5. Reinstall, keeping your /home partition unformatted.

Prevention Checklist

• Use packaged drivers, not NVIDIA’s .run installer
• Wait for the module build after kernel updates on Fedora and Arch
• Keep one older kernel installed
• Set up Timeshift, Snapper or Btrfs Assistant before you need it
• Read release notes before major upgrades
• Keep 15 to 20 percent of the disk free

Frequently Asked Questions

Final Thoughts

A dark screen after login feels catastrophic, but it’s usually a small break between your kernel, GPU driver and desktop. Start at the console, read the journal, rule out disk and ownership problems, then fix the driver for your distro and card generation. Keep a snapshot or an older kernel handy and you’ll rarely stay stuck.

I hope this guide on How to Fix a Black Screen After Login on Linux gets you back to your desktop fast. If you’re still stuck, post your journalctl -b -p err output and GPU model on your distro’s forum. Helpers can often spot the problem in seconds.

Useful Official Resources

• Ubuntu 26.04 LTS roadmap and desktop notes (Ubuntu Discourse)
• Debian “trixie” release information (debian.org)
• NVIDIA driver guide (Arch Wiki)
• NVIDIA installation on Fedora (RPM Fusion)
• Fedora 44 black screen after update thread (Fedora Discussion)
• Kernel parameters reference (Arch Wiki)

---

Disclaimer: This article is for general information only. Commands that remove packages, edit boot settings or change ownership can affect your system, so back up important data first and adapt the steps to your hardware and distro version. Distro releases and driver support change often, so confirm details against official documentation. The author and publisher aren’t liable for data loss or system issues resulting from this guide.

---