Overview
Graphical desktops consume resources and can block recovery when GPU drivers fail. Multi-user.target boots to a text login on virtual consoles.
Toggle temporarily from GRUB or permanently with systemd default target.
Implementation
At GRUB, press e on the Ubuntu entry, add systemd.unit=multi-user.target to the linux line, Ctrl+X to boot. Permanent: sudo systemctl set-default multi-user.target; revert with graphical.target.
Start GUI on demand: sudo systemctl start gdm or lightdm.
When implementing guidance from Ubuntu – Boot into Text Mode / Console / Command Line, start in a controlled environment that mirrors production versions of operating systems, runtimes, and network policies. Capture a baseline before changes: export configs, snapshot VMs, or tag releases in source control so rollback stays straightforward if behavior regresses.
Document prerequisites, expected outcomes, and verification steps in a short runbook. Automated checks—smoke tests, health endpoints, or query validations—catch regressions early when platforms receive patches. Security belongs in every workflow: apply least privilege, rotate secrets, and review audit logs after deployment.
If results differ across machines, compare environment variables, permission models, time zones, and regional settings. Intermittent issues often trace to caching layers, stale DNS, or duplicated services bound to the same port.
Example
sudo systemctl set-default multi-user.target
sudo reboot
# Return to desktop:
sudo systemctl set-default graphical.targetTips
- SSH works regardless of local GUI.
- Nomodeset kernel param helps broken NVIDIA drivers.
- Document before remote headless changes.
- Server images skip GUI by default.
- Re-verify after reboots, certificate renewals, or failover exercises.
- Align monitoring and alerts with the failure modes described in this guide.
- Keep vendor documentation links handy for breaking changes between versions.
- Pair automation with a manual spot check during initial production rollout.