Story / scenario opener
You just finished a major dnf upgrade on your Fedora workstation. The system reboots, the GRUB menu vanishes, and the screen stays black. The display manager never loads. You need a terminal to check the logs, but you are stuck in a boot loop. Or maybe you are setting up a headless server and want to skip the desktop environment entirely to save RAM and reduce attack surface. Both situations boil down to one systemd configuration: the default target.
What's actually happening
Systemd replaces the old SysV init runlevels with a dependency-based system called targets. A target is just a collection of units that start together. multi-user.target boots the system to a command line. It starts networking, SSH, and core services. graphical.target inherits everything from multi-user and adds the display manager, desktop environment, and Xorg or Wayland compositors.
Think of targets like layers. The base layer handles hardware and networking. The next layer adds user sessions. The top layer adds a graphical interface. When you boot, systemd follows a symlink at /etc/systemd/system/default.target to decide which layer to stop at. That symlink points to a unit file in /usr/lib/systemd/system/. You never edit the unit files in /usr/lib/. Package managers overwrite them on every update. You only change where the symlink points. That keeps your configuration safe across dnf upgrade --refresh cycles.
The symlink mechanism matters because systemd reads it early in the boot sequence. If the symlink points to a valid target, systemd pulls in all required dependencies and starts them in parallel. If the symlink is broken or points to a missing unit, systemd cannot proceed and drops you into emergency mode. The system is not broken. It is waiting for a valid destination.
Reboot before you debug. Half the time the symptom is gone.
How to change the default target
The systemctl set-default command updates that symlink automatically. It handles the path resolution and permissions for you. Run the command with sudo to apply the change. The command does not reboot the machine. It only changes what happens the next time the system starts.
Here is how to switch to a command-line only boot. This is the standard configuration for servers and containers.
sudo systemctl set-default multi-user.target # Updates the default.target symlink to point to multi-user
# WHY: This prevents the display manager from starting on boot
# WHY: Saves roughly 300MB of RAM on a default Fedora Workstation install
# WHY: Reduces the attack surface by not loading X11 or Wayland servers
Here is how to switch back to the desktop environment. Use this when you need a graphical interface for daily work or development.
sudo systemctl set-default graphical.target # Restores the desktop environment as the boot destination
# WHY: Ensures GDM or SDDM starts automatically after core services
# WHY: Required for any application that depends on a display server
# WHY: Pulls in desktop session services and power management daemons
If you need to switch targets immediately without rebooting, use systemctl isolate. This stops units not required by the new target and starts the ones that are. It is useful when the desktop freezes and you need a clean terminal to run diagnostics.
Here is how to drop to a terminal instantly from a running desktop.
sudo systemctl isolate multi-user.target # Switches the running system state immediately
# WHY: Kills the display manager and desktop session on the fly
# WHY: Useful for emergency debugging when the GUI is frozen
# WHY: Does not modify the default.target symlink for future boots
Run journalctl first. Read the actual error before guessing.
Verify the change
Always confirm the symlink points to the correct unit before you reboot. A broken symlink or a typo in the target name will drop you into a recovery shell. Verification takes two seconds and saves twenty minutes of troubleshooting.
Here is how to check which target systemd will load on the next boot.
systemctl get-default # Reads the current default.target symlink
# WHY: Confirms the configuration survived the command without errors
# WHY: Returns the exact unit name systemd will use during initialization
# WHY: Fails fast if the symlink points to a non-existent unit
You can also inspect the symlink directly to see the full path. This helps when debugging package manager conflicts or manual edits that went wrong.
Here is how to verify the symlink structure matches systemd expectations.
ls -l /etc/systemd/system/default.target # Shows where the symlink actually points
# WHY: Verifies the file is a symlink and not a regular file
# WHY: Confirms the destination matches the output of get-default
# WHY: Reveals if a previous admin manually replaced the symlink with a copy
If the output shows a regular file instead of a symlink, delete it and run set-default again. Systemd expects a symbolic link. Regular files in that directory cause initialization warnings and can block target switching.
Trust the package manager. Manual file edits drift, snapshots stay.
Common pitfalls and what the error looks like
The most common mistake is typing the target name wrong. Systemd will accept the command but create a symlink to a non-existent unit. The next boot will fail to find the target and drop you into emergency mode.
If you see the following prompt, you misspelled the target name or dropped the .target suffix.
Welcome to emergency mode! After logging in, type "journalctl -xb" to view
system logs, "systemctl reboot" to reboot, "systemctl default" or ^D to
try again to boot into default mode.
Check the exact spelling. Systemd units always end in .target. Do not drop the suffix. Run systemctl get-default to see what you actually set.
Another frequent issue involves display manager conflicts. Fedora Workstation ships with GDM. If you installed SDDM or LightDM and changed the default to graphical.target, systemd might start both. The boot will hang or show a black screen. Disable the unwanted display manager before switching targets.
Here is how to check which display manager is active and stop the conflicting one.
systemctl status gdm.service # Checks if the GNOME display manager is running
# WHY: Shows recent log lines and the current active state
# WHY: Always check status before disabling or masking a service
# WHY: Reveals dependency failures that block the graphical stack
sudo systemctl disable --now gdm.service # Stops and prevents GDM from starting
# WHY: Frees the graphical.target slot for your preferred display manager
# WHY: Prevents two display managers from fighting over the same TTY
SELinux denials can also block target transitions if you manually edited unit files. Fedora enforces strict contexts on /etc/systemd/system/. If you copied files from a backup without preserving attributes, the boot will stall. Run restorecon -Rv /etc/systemd/system/ to fix contexts. Read journalctl -t setroubleshoot for a one-line summary before disabling SELinux. The journalctl -xe command adds explanatory text and jumps to the end. Most sysadmins type journalctl -xeu <unit> muscle-memory style. Use it to isolate the exact service that failed during the target switch.
Snapshot the system before the upgrade. Future-you will thank you.
When to use this vs alternatives
Use systemctl set-default multi-user.target when you are provisioning a server, a CI runner, or a headless media box. Use systemctl set-default graphical.target when you need a desktop environment for development, browsing, or GUI applications. Use systemctl isolate when you need to switch the running system state immediately without rebooting. Use rescue.target when the system fails to boot and you need a single-user root shell to fix broken packages or filesystem errors. Stay on the default Workstation configuration if you only need a terminal occasionally and prefer the convenience of a desktop.