Kali Black Screen After Login or "Failed to Start Session": Get the Desktop Back
A black screen after login in Kali Linux almost always means the desktop session crashed, not that your graphics card died — the fastest fix is to reach a text terminal with Ctrl+Alt+F3 and restart the display manager service. Here's the part almost nobody tells you: if that login screen appeared at all before it went black, your GPU driver already did its job — the fault is almost always in the session that starts after you type your password, which is why reinstalling NVIDIA drivers is usually the wrong first move.
The one question that tells you where to look
Jake runs a small phone shop, and he keeps a Kali VM around to check customer devices before he touches them for real work. One Tuesday morning, before a client demo, he ran his usual sudo apt update && sudo apt full-upgrade -y, rebooted like always, typed his password at the login screen — and got a black rectangle with a blinking cursor. The demo started fifteen minutes late.
Before touching any fix, answer one question: did you see a graphical login screen at all, or did the screen go black before that? A login screen — the box asking for your username and password — means the kernel booted, the GPU driver loaded, and the display manager (the piece of software that draws that login screen) is working. That means the problem lives in the session that starts after you type your password, not in graphics drivers. If you never saw a login screen and went straight from the boot logo to black, the problem is earlier in the chain — closer to the kernel and the GPU.
🙋♂️ Jake's Reality Check
"I saw the login box, typed my password, and then black. So my graphics card is broken, right?"
No. If the login box drew correctly, your GPU and driver already proved they work. Something crashed after that — the desktop session itself.
Getting to a terminal is the first move either way, because it lets you read the actual error instead of guessing at a black screen.
How to reach a text terminal (TTY)
- Press Ctrl+Alt+F3 (F2 through F6 also work on most installs). On VirtualBox, use the Host key — usually right Ctrl — instead of the left Ctrl, or the black screen swallows the keystroke.
- If a text login prompt appears, log in with your normal username and password (or kali / kali if this is an untouched live/pre-built image).
- Run systemctl status display-manager to see which service is running and whether it failed.
- If nothing responds — no text, no prompt, not even a cursor blink — the fault sits before the login manager, in the kernel or GPU driver, and you'll want the nomodeset step later in this post.
If you're on a physical laptop with a hybrid keyboard or no function-key row (some ultrabooks, some tablets in keyboard-dock mode), you may need to hold the Fn key alongside Ctrl+Alt+F3, or plug in a USB keyboard temporarily — the TTY switch is a kernel-level keyboard shortcut, and a manufacturer's custom Fn-lock behavior can eat it.
Cause 1: the display manager failed to start
Kali's default display manager — the service that draws the login screen and hands off to your desktop — is LightDM, running under Xfce (Kali's default desktop). If you've switched to GNOME at some point, that's GDM3 instead. After a package upgrade, this service can crash on start and just... stop, leaving a black screen with no error visible anywhere except the system log. In your TTY, check it directly:
systemctl status lightdm.service
A status of "failed" with a line like "Start request repeated too quickly" means the service is stuck in a restart loop and giving up. The /var/log/lightdm/lightdm.log file (or the Xorg log alongside it at /var/log/lightdm/x-0.org) usually names the real cause — a missing package, a broken configuration file, or a GPU driver that Xorg can't talk to. Try the straightforward restart first:
sudo systemctl restart lightdm
If that throws you straight back into a crash loop, reinstalling the package is the next cheapest move, since a half-upgraded package is a common trigger:
sudo apt install --reinstall lightdm
⚠️ What this actually breaks
Reinstalling the display manager doesn't touch your files, home directory, or installed tools — it only replaces the login-screen software. It's safe to try before anything more drastic.
Quick reference by desktop environment
| Desktop | Display manager | Restart command | Log file to check |
|---|---|---|---|
| Xfce (Kali default) | LightDM | sudo systemctl restart lightdm | /var/log/lightdm/lightdm.log |
| GNOME | GDM3 | sudo systemctl restart gdm3 | journalctl -u gdm3 |
| KDE Plasma | SDDM | sudo systemctl restart sddm | journalctl -u sddm |
Cause 2: NVIDIA drivers and DKMS breaking after a kernel update
Kali ships frequent kernel updates, and if you have an NVIDIA card with proprietary drivers installed, this is the single most common bare-metal cause of a black screen right after an upgrade. NVIDIA's driver isn't built into the kernel — it's rebuilt for each new kernel by DKMS (Dynamic Kernel Module Support), a system that automatically recompiles third-party kernel modules when the kernel changes. If the matching kernel headers for the new kernel aren't installed yet, DKMS has nothing to compile against, the module fails silently, and the graphical session can't start. On boot you might see nothing but a blinking cursor or a dash instead of the desktop.
The fix is to make sure headers and DKMS are in sync, from your TTY session:
sudo apt install -y linux-headers-$(uname -r)
sudo dkms autoinstall
sudo reboot
There's a second, narrower NVIDIA trap specific to GNOME: driver versions below 550.163.01 have known problems loading GNOME's session on Wayland, and this can also show up as a black screen or login failure with the log message "Unit gnome-session-wayland@wayland.target not found." Check whether Wayland is enabled:
sudo grep -r "Wayland" /etc/gdm3/
If your driver is older than that build and you're on GNOME, either update the NVIDIA driver package or force an Xorg session — GDM's login screen has a gear icon at the bottom right where you can pick "GNOME on Xorg" as a fallback before typing your password, once you can reach the login screen at all.
✅ Why this is the one to check first if you have NVIDIA
If your laptop or desktop has a dedicated NVIDIA GPU and the black screen appeared right after apt full-upgrade pulled a new kernel, headers-and-DKMS is the highest-odds cause, and the fix is two commands with no risk to your data.
Cause 3: the Xfce compositor, especially inside a VM
Xfce's window manager, xfwm4, includes a compositor — the piece responsible for effects like shadows and transparency. On weaker or virtualized graphics, this compositor can misbehave badly enough to blank the whole screen even though the desktop underneath is technically running. If you can get to a TTY and the desktop session shows as active in systemctl status lightdm despite the black screen, this is a strong candidate.
From the desktop menu (reachable by right-clicking the desktop once you're logged in, even blind, or by switching back with Ctrl+Alt+F1 or F7 after logging in from TTY): go to Settings → Window Manager Tweaks → Compositor tab, and uncheck "Enable display compositing." If you want visual effects back later, the alternative compositor "compton" can be added under Application Autostart instead of xfwm4's built-in one.
Cause 4: virtual machine graphics settings
Running Kali inside VirtualBox or VMware is extremely common, and the virtual GPU is a frequent source of exactly this symptom. Kali's own VirtualBox setup documentation specifically calls out disabling "Accelerated 3D graphics" as a step people skip and then run into trouble over. If your black screen only happens inside a VM:
- Shut the VM down fully (not save-state), open its display settings, and turn off 3D acceleration.
- Make sure Guest Additions (VirtualBox) or VMware Tools are installed and up to date — a mismatched or missing version is a common trigger on its own.
- In VirtualBox specifically, if 3D acceleration was the cause, disable it, update the Guest Additions, then re-enable it only if you actually need it.
Cause 5: a full disk (the one everyone forgets to check)
This is the cause with the least glamour and the most misdiagnoses. Both the display manager and your desktop session write temporary files and lock files as they start — to /tmp, your home directory, and /var. If any of those partitions is full, the session can fail to start with no obvious graphics-related error at all — just black. From your TTY:
df -h /
If / (or a separate /home partition) is at or near 100%, clear space before doing anything else — old kernel packages after several upgrades are a common culprit:
sudo apt autoremove
Popular advice online tends to jump straight to reinstalling graphics drivers or the whole desktop environment. That's often the wrong first move — checking disk space costs ten seconds and rules out an entire category of cause before you touch anything more invasive.
This is a different symptom: the login loop
"Login loop" is a distinct symptom from a plain black screen: you type your password, the screen flickers as if it's about to load, and you're dropped straight back at the login prompt — sometimes with the desktop briefly flashing first. This almost always points at a permissions problem in your home directory rather than graphics or the display manager itself. A very common trigger is having run a graphical program with sudo at some point, which leaves ownership files in your home folder set to root instead of you.
From a TTY, check and fix ownership of the two files most often responsible:
ls -la ~/.Xauthority ~/.ICEauthority
sudo chown $USER:$USER ~/.Xauthority ~/.ICEauthority
If that doesn't resolve it, a corrupted desktop configuration cache can also cause the loop. Renaming (not deleting, in case you want to inspect it later) the relevant config folders forces a fresh one to be generated on next login:
mv ~/.cache ~/.cache.bak
mv ~/.config/xfce4 ~/.config/xfce4.bak
This resets your Xfce panel layout and appearance settings back to default — a minor annoyance, not data loss. Your documents, Desktop folder, and installed tools are untouched.
If nothing even reaches a text terminal
If Ctrl+Alt+F3 gets you nothing at all — not even a blinking cursor — the problem sits earlier, in the kernel's attempt to set up a display mode before anything graphical has even tried to start. The standard boot parameter for this is nomodeset, which tells the kernel to skip its own display setup and let the display manager handle it instead:
At the GRUB menu, highlight your Kali entry, press e to edit, find the line starting with linux, add nomodeset to the end of it, then press Ctrl+X to boot with it just for this session. If that gets you to a desktop, it confirms a kernel/graphics-driver mismatch rather than a display-manager problem, and you should revisit the NVIDIA/DKMS section above rather than leaving nomodeset permanent — it disables hardware acceleration and isn't meant as a long-term fix.
Nomodeset alone, added once and left there, is often given as the whole fix on forum posts. It isn't — it gets you back in so you can fix the actual driver problem, not a substitute for doing so.
When none of the above holds: recovery mode and reinstalling the desktop
If restarting the display manager, fixing DKMS, and checking disk space all leave you back at black, GRUB's recovery mode gives you a safer environment to work from than a TTY over a half-broken session:
- Reboot, and at the GRUB menu select Advanced options for Kali GNU/Linux.
- Choose a recovery mode entry, then root to get a root shell without needing to log in through the broken session.
- Refresh package state in case the upgrade itself was interrupted: apt update && apt --fix-broken install.
- Fully reinstall the desktop and display manager as a last resort: apt install --reinstall kali-desktop-xfce lightdm.
- Reboot normally and check whether the login screen and desktop both return.
⚠️ What we cannot fix for you
If you can't remember the login password from before the upgrade, none of these steps help — TTY and recovery mode both still require your account credentials to reach a usable shell as that user. That's a separate password-recovery problem, not a black-screen one.
Reinstalling the entire operating system is the step people reach for out of frustration, and it's almost never necessary. None of the fixes above touch /home, your installed security tools, or your saved projects — they replace the login screen and desktop software, not your data.
Ethan's take
"People treat a black screen like the OS is dying," Ethan said. "It's the opposite — the kernel booted, the disk mounted, the network probably came up. One small piece of software, the login manager, choked. Reinstalling Kali over that is like replacing a car because the radio won't turn on."
Symptom-to-cause reference
| What you see | Likely cause | Try first |
|---|---|---|
| Login screen appears, then black after password | Display manager or desktop session crash | Restart lightdm/gdm3 from TTY |
| Black before login screen ever appears | Kernel/GPU driver mode-setting issue | Boot with nomodeset |
| Blinking cursor, no login screen, NVIDIA card | DKMS module not rebuilt for new kernel | Install matching kernel headers, dkms autoinstall |
| Password accepted, bounced back to login screen | Home directory permissions / corrupted config | Fix .Xauthority ownership, rename .config/xfce4 |
| Only happens in VirtualBox/VMware | Virtual GPU / 3D acceleration | Disable 3D acceleration, update Guest Additions |
| Xfce loads then screen goes black mid-session | xfwm4 compositor | Disable display compositing |
Did upgrading toward Kali 2026.3 cause this?
As of late August 2026, Kali 2026.3 hasn't officially shipped yet — but because Kali is a rolling distribution, running full-upgrade pulls packages from the same repository the next numbered release will be snapshotted from. If your black screen started right after a large upgrade, you may well have pulled in the same kernel and desktop package movement that's heading toward that release, including a KDE Plasma bump for Plasma users. There's a full breakdown of exactly what's confirmed for that release, what's still just a milestone-board target, and how to spot fake "2026.3 released" articles in our Kali 2026.3 tracking page — worth a look if you want to know whether you're on the bleeding edge of what's coming.
Either way, the fixes on this page apply the same regardless of which numbered release you're nominally on, since they target the display manager and driver layer, not release-specific packaging.
Reducing the odds of this happening on your next update
- Don't interrupt an upgrade midway. A kernel or display-manager package half-installed because of a closed lid or a killed terminal is a common self-inflicted cause of exactly this symptom.
- Reboot promptly after a kernel update rather than leaving the old kernel running for days — the longer the gap, the more DKMS modules can drift out of sync.
- Keep an eye on free disk space before running large upgrades, particularly on VM images with small allocated disks.
- If you're on NVIDIA, check driver/DKMS status right after any kernel bump rather than waiting for the next reboot to find out something broke.
One more thing worth knowing
Jake's demo-morning black screen turned out to be the DKMS case — his VM has an emulated NVIDIA adapter passthrough setup he'd forgotten about, and the new kernel had shipped without matching headers pre-installed. Two commands and a reboot, and he was back in before the client noticed anything beyond a slightly awkward opening five minutes. The lesson he took from it wasn't "don't update" — it was "check TTY before panicking," and that's really the whole point of this page.
- Kali 2026.3 Release Date: what's confirmed and what's still noise
Worth reading if this black screen showed up right after a big rolling-repo update.
Frequently asked questions
Is Kali Linux showing a black screen after login the same as a login loop?
No. A black screen means the screen goes dark and stays there. A login loop means you're sent back to the login prompt again instead. They usually have different causes — display manager/driver crashes for the black screen, home-directory permissions or config corruption for the loop — and the fixes in this post are separated accordingly.
Why does Kali Linux boot to a black screen after an update?
The most common triggers after a full-upgrade are an NVIDIA driver not rebuilt for a new kernel via DKMS, a display-manager package that failed to restart cleanly, or a full disk that stopped the session from writing its temporary files. Checking a TTY tells you which one you're dealing with.
How do I get out of a black screen in Kali Linux?
Press Ctrl+Alt+F3 (or F2 through F6) to reach a text terminal, log in there, and run systemctl status display-manager to see what's actually failing before trying any fix blind.
Does nomodeset fix Kali Linux black screen problems?
It can get you back to a desktop if the cause is a kernel/GPU mode-setting conflict, but it's a temporary workaround, not a permanent fix, and it disables hardware acceleration while active. Use it to get in and fix the underlying driver issue, not as a permanent boot option.
Why does my Kali Linux VM show a black screen after login?
Virtual GPUs in VirtualBox and VMware frequently cause this. Disable 3D acceleration in the VM's display settings while shut down, and make sure Guest Additions or VMware Tools are current — a version mismatch there is one of the most common VM-specific causes.
Can a full disk really cause a black screen in Kali Linux?
Yes. Both the display manager and your desktop session write temporary and lock files during startup, and if the filesystem they write to is full, that startup can fail with no graphics-related error message at all. Run df -h / from a TTY to rule this out early.
Should I reinstall Kali Linux to fix a black screen?
Almost never. Every fix in this post targets the display manager, desktop session, or driver layer, none of which requires touching your installed system or files. A full reinstall is a last resort reserved for cases where recovery mode and package reinstalls have both already failed.
How do I check which display manager Kali Linux is using?
Run systemctl status display-manager from a terminal, or check the contents of /etc/X11/default-display-manager. Kali's Xfce default is LightDM; if you've installed GNOME, it's likely GDM3 instead.
Why does Kali Linux keep sending me back to the login screen?
This login-loop pattern is most often caused by .Xauthority or .ICEauthority files in your home directory being owned by root instead of your user, usually from running a graphical app with sudo at some point. Fixing ownership with chown, or renaming a corrupted ~/.config/xfce4 folder, resolves most cases.
Is the NVIDIA driver always the cause of a Kali Linux black screen?
No. It's a very common cause on bare-metal systems with NVIDIA cards specifically after a kernel update, but the display manager crashing, a full disk, VM graphics settings, and home-directory permission issues are equally real causes with nothing to do with NVIDIA.
Does switching from GDM to LightDM fix black screen issues?
Sometimes, if the specific failure is tied to GDM's Wayland session handling with an older NVIDIA driver. But it's a workaround, not a diagnosis — it's worth understanding which service was actually failing first, since the same underlying driver problem can eventually affect either display manager.
Can updating toward Kali 2026.3 cause a black screen?
It's possible in the sense that any large rolling-repository upgrade — including packages that will eventually be part of the 2026.3 snapshot — can pull in a new kernel or desktop version that triggers one of the causes on this page. The fixes here aren't specific to any one numbered release.
Why does my Xfce desktop go black only when 3D acceleration is on?
The xfwm4 window manager's built-in compositor can fail on weak or virtualized 3D acceleration and blank the entire screen. Disabling display compositing under Settings > Window Manager Tweaks, or disabling 3D acceleration at the VM level, resolves this.
What is the Ctrl+Alt+F2 trick and does it always work?
It switches your display to a different virtual text terminal (TTY), letting you log in and diagnose without a graphical session. It works whenever the kernel itself is still running; if it does nothing at all, the fault is earlier in the boot chain, and a nomodeset boot parameter is the next thing to try.
Will I lose my files if I reinstall the desktop environment?
No. Reinstalling packages like kali-desktop-xfce or lightdm replaces software, not your home directory. Your documents, saved projects, and installed security tools are untouched by any fix described here.
How do I stop this from happening again after future updates?
Reboot promptly after kernel updates rather than letting the system sit on a half-updated state, watch free disk space before large upgrades, and if you run NVIDIA, check DKMS status right after any kernel bump instead of discovering a problem at the next cold boot.
Revision note. Written in late August 2026, covering current Kali rolling releases through 2026.2 and the display-manager and driver behavior that carries forward regardless of the exact release number. This will need revisiting once Kali 2026.3 ships officially or if a future release changes the default display manager. If you're reading this at 1am with a client demo in the morning: take a breath, the TTY trick almost always works, and your files are still there.