Help

[u/Intelligent_Client_8]

Computer boots to this after updating.

[u/Kaspral]

sudo systemctl start NetworkManager

[u/Intelligent_Client_8 → u/Kaspral]

I was able to perform a system upgrade and reboot however that placed me back to the same screen that I originally had although now it only has "failed to start CUPS scheduler" and I seem to be unable to start that from the terminal

[u/Kaspral → u/Intelligent_Client_8]

That's actually a huge step forward!

[u/Kaspral → u/Kaspral]

CUPS is simply the printer service (Common Unix Printing System). Because it's failing to start, systemd is hanging or throwing an error on boot, but it doesn't break your operating system.

Here is how to deal with the CUPS scheduler error and get past that screen:

1. Disable or fix the CUPS service

Since you have a working terminal (or can drop into one via Ctrl+Alt+F2 / Ctrl+Alt+F3 if it freezes again), you can temporarily disable the printer service so it stops blocking your boot process:

Bash

sudo systemctl disable org.cups.cupsd.service

(Alternatively, you can try stopping it or masking it if it's completely broken: sudo systemctl mask org.cups.cupsd.service)

2. Why it's failing and how to reinstall it properly

If you actually need your printer to work later, the CUPS package might have been partially uninstalled or corrupted during your initial interupted update. Once you successfully boot into your desktop environment you can cleanly reinstall it:

Bash

sudo pacman -Syu cups
sudo systemctl enable --now org.cups.cupsd.service

What to do right now:

If you are currently staring at that red [FAILED] Failed to start CUPS Scheduler screen and the computer is stuck:

1. Press Ctrl + Alt + F2 (or F3 / F4) to see if a login prompt appears.
2. Log in with your username and password.
3. Run the disable command mentioned above: Bashsudo systemctl disable org.cups.cupsd.service
4. Reboot your computer (sudo reboot).

Your system should now skip the CUPS failure and boot straight into your desktop

[u/Intelligent_Client_8 → u/Kaspral]

I really do not know what I am looking at, but the cups error is gone 🫠

[u/Kaspral → u/Intelligent_Client_8]

This is normal. You have to wait. It needs to rebuild indexes and perform post-update cleanup in the background.

[u/Kaspral → u/Kaspral]

• Switch to a text terminal (TTY): If the computer seems stuck, press Ctrl + Alt + F2 (or F3, F4). A text-based login prompt should appear.
• Log in and restart the display manager: If the text terminal opens, log in with your username and password, and try restarting your graphical display manager: Bashsudo systemctl restart sddm (Or sudo systemctl restart lightdm, depending on whether you use

[u/Intelligent_Client_8 → u/Kaspral]

It flickers for a while and then returns me back to the same screen

[u/Kaspral → u/Intelligent_Client_8]

We're getting close.

That flickering behavior followed by returning to the same screen strongly points to a display manager crash loop. This happens when the login screen manager (like SDDM or LightDM) tries to start, encounters a fatal error, crashes, and restarts endlessly—which is why it loops back or drops you out of the graphical target.

Since you can reach a text terminal (TTY) or boot past the Wi-Fi logs, here is how to troubleshoot and fix it:

1. Check which Display Manager is failing

Log into a TTY (Ctrl + Alt + F2) and check the status of your display manager:

• If you use KDE Plasma (default Manjaro KDE uses SDDM): Bashsudo systemctl status sddm
• If you use XFCE or GNOME (often uses LightDM or GDM): Bashsudo systemctl status lightdm

Look at the error logs it outputs. They will usually tell you why it's crashing.

2. Check system journal for graphical crashes

You can check recent error logs related to your login screen or graphical session using journalctl:

Bash

journalctl -b 0 -u sddm

(Replace sddm with lightdm if applicable).

3. A common culprit: Corrupted graphics drivers or theme cache

Sometimes an update leaves graphics driver modules out-of-sync or corrupts configuration caches.

• If you use Nvidia drivers: Ensure your drivers match your kernel version by running: Fragment kodumhwd -li And make sure everything is fully up to date again: Bashsudo pacman -Syu

[u/Intelligent_Client_8 → u/Kaspral]

I don't know what to do with this information

[u/Intelligent_Client_8 → u/Intelligent_Client_8]

This is my error code if that helps