The colord service is a system daemon in Linux designed to map and manage color profiles (ICC profiles) for output devices, ensuring accurate color reproduction across monitors, printers, and scanners. It interfaces closely with desktop environments (like GNOME or KDE) and the X11/Wayland display servers. However, on a headless Ubuntu Server installation—which by definition lacks a graphical user interface, connected monitors, or local printing hardware—the colord daemon is completely unnecessary. It starts at boot, consumes minor system resources (RAM and CPU time during initialization), and occasionally polls D-Bus for hardware that doesn’t exist.
This guide explains how to completely disable the colord daemon in Ubuntu Server, streamlining your server’s process tree by removing irrelevant desktop-oriented services.
Stop and Mask the Colord Daemon
Because colord is deeply integrated into the D-Bus messaging system and can be triggered via socket activation by other overzealous desktop-adjacent packages that may have been inadvertently installed as dependencies, we must disable and aggressively mask the service.
- Log into your Ubuntu Server via SSH using an account with
sudoprivileges. - First, stop the daemon if it is currently running:
sudo systemctl stop colord.service - Next, disable the service to prevent it from loading on the next boot:
sudo systemctl disable colord.service - To guarantee that no other D-Bus client or init script can accidentally wake it up, mask the service entirely:
sudo systemctl mask colord.service
Verify the Service Lockdown
By masking the service, you have effectively symlinked its unit file to /dev/null, ensuring the systemd manager cannot execute it under any circumstances, even if requested by an application layer.
To verify the lockdown is successful, run the following command to check the status of the daemon:
systemctl status colord.serviceThe output will clearly state that the service is masked. You have successfully optimized your headless server by ensuring that graphical color management routines are never initialized.