How to Fix SDDM Hanging or Crashing After Logout on Manjaro Linux

We have all been there on Manjaro: you wrap up whatever you are doing, hit Logout to swap users or step away, and bam - pitch black screen. Sometimes there is a stray frozen cursor mocking you, sometimes pure void. Your machine hasn't actually crashed under the hood, but the Display Manager (SDDM) essentially tripped over its own shoelaces while trying to reload.

If you are running KDE Plasma on Manjaro, you are definitely not alone here. What is usually happening is a classic race condition: your system drags its feet closing out background processes from your old session, and SDDM tries spinning back up before the ground is actually clear. Resist the urge to hold down that power button; let's get you unstuck right now, and then knock out the root cause for good.

The Quick Fix: Unfreeze Without Rebooting

If you are staring at that frustrating blank display right this second, don't yank the plug or do a hard reset - you really don't want to risk corrupting your drive. You can easily bounce the display manager straight from a virtual TTY terminal instead.

1. Tap Ctrl + Alt + F2 (or try F3/F4). That drops you right out of the broken GUI into a clean text console.

2. Log in with your regular username and password.

3. Kick SDDM back to life by running: sudo systemctl restart sddm

4. Give it a second, and your normal login screen should pop right back up.

That will rescue your current session, but it is just a bandage. To keep it from freezing up every single time you sign out, we need to tidy up how SDDM handles session handoffs.

Solution 1: The "Xstop" Script Method (Most Effective)

The cleanest, most reliable workaround is to tell SDDM to aggressively clean house whenever you log out. If we force it to terminate any lingering user processes the second the session drops, those leftover "zombie" tasks won't hang up the manager anymore.

To do that, we just drop a quick directive into the system's Xstop script using Nano or whichever terminal editor you prefer.

1. Pop open your terminal.

2. Open the script with administrative privileges: sudo nano /usr/share/sddm/scripts/Xstop

3. Scroll all the way to the bottom and add this single line: killall --user $USER

4. Hit Ctrl + O to write the changes, press Enter, and exit with Ctrl + X.

Now, whenever the X server wraps up, it automatically clears out every lingering background thread tied to your account, giving SDDM a totally clean slate to restart smoothly.

Solution 2: Adjusting SDDM Configuration

If that script tweak didn't totally do the trick, the culprit might be the way SDDM attempts to recycle or reuse active sessions. Forcing it to treat every single logout like a fresh launch often clears the roadblock.

While you could fiddle with snippet directories, editing the primary configuration file directly is the most straightforward path here.

1. Open your main configuration file: sudo nano /etc/sddm.conf

2. Check for the [Users] block. If you don't see one in there, go ahead and create it.

3. Under that section, make sure this directive is present: ReuseSession=true

A quick heads-up: Hardware can be quirky, and for reasons that baffle everyone, some NVIDIA setups actually behave better when this is set to false. If setting it to true leaves you stuck, flip it to false and see if your card prefers that.

Solution 3: NVIDIA Driver Conflicts (Kernel Parameters)

Running dedicated NVIDIA hardware on proprietary drivers? The black screen is practically a rite of passage, usually stemming from a sloppy display handoff. To smooth that transition out, you will want to enable DRM kernel mode setting.

1. Pull up your GRUB loader configuration: sudo nano /etc/default/grub

2. Track down the line labeled GRUB_CMDLINE_LINUX_DEFAULT.

3. Slip nvidia-drm.modeset=1 inside the existing quotation marks so it looks something like: GRUB_CMDLINE_LINUX_DEFAULT="quiet splash nvidia-drm.modeset=1"

4. Save out of the file, then rebuild your boot config: sudo update-grub

5. Give your machine a full restart so the new kernel flags take effect.

Solution 4: Reinstalling SDDM Correctly

If you have spent hours heavily customizing Plasma themes, tinkering with dotfiles, or stacking login tweaks, something underlying might simply be misconfigured or corrupt. Nuking SDDM and pulling down a clean install gets everything back to baseline.

You will want to wipe its residual configs rather than doing a basic uninstall so nothing broken carries over.

1. Jump over to a text terminal with Ctrl + Alt + F2 and kill the active display service: sudo systemctl stop sddm

2. Strip out SDDM alongside unneeded dependencies: sudo pacman -Rns sddm

3. Grab a fresh package: sudo pacman -S sddm

4. Re-enable the service so it starts on boot, then fire it up: sudo systemctl enable sddm followed by sudo systemctl start sddm

How to Analyze the Logs

Still running into a wall? The best move is to let your system tell you what it is choking on. Journal logs get massive fast, but you can lean on the linux tail command to slice through the noise and only inspect the freshest errors.

Right after you get hit with a frozen logout, reboot or restart SDDM from TTY, then fire this off: journalctl -b -1 -p 3

What you are looking at here are strictly priority 3 errors (actual failures) pulled from your previous boot cycle (-1). Scan the output for mentions of sddm, kwin, or nvidia. Snagging that exact error message will make searching the Manjaro community forums infinitely more productive.

On top of that, if you suspect duplicate configs are fighting each other across /etc/ or /usr/, you can always deploy the find command to track down any rogue drop-in files quietly overriding your setup.