colord isn’t specifically related to a Jetson and might be related to printers or scanners (or the software even if you don’t have a printer or scanner). First, is the system updated? Here’s what I’d suggest…
First check that there is no error in “sha1sum -c /etc/nv_tegra_release”. If there is, and if it is a libglx.so error, run this command to fix:
<b>sudo ln -sf /usr/lib/aarch64-linux-gnu/tegra/libglx.so /usr/lib/xorg/modules/extensions/libglx.so</b>
Then run “sudo apt update” followed by “sudo apt-get upgrade”. After this, before you do anything else, check again if “sha1sum -c /etc/nv_tegra_release” shows an error with libglx.so. If it does, just fix it with that above command (mesa package is required and there is more than one mesa-related package…on of those packages when updated overwrites the NVIDIA version which will break the GUI if you log out or reboot). Once packages are updated you can do some debugging.
The way to see if colord is running:
systemctl status colord.service
colord saves and restores color profile information with devices which might need some form of color calibration, e.g., scanners and printers. It would probably crash if there were permission issues when writing, or if disk space ran out. See how much space you have:
df -H /
When colord talks to different parts of the system it uses dbus. What makes this particularly difficult is that you get your error while logging in with the GUI, but you can’t use the dbus-monitor tool unless there is a running GUI (it’s a session tool for apps to talk to each other…it can’t send a message without a session). If the above systemctl command shows colord.service is not running, then the error is from prior to your login, and might not be as hard to locate. If colord.service is running, then there is an error revolving around your login session.
Is colord.service running? After login to the GUI do you see anything from “dmesg | egrep -i colord”?