seeking help with /var/log/syslog messages
 

I see the following message in /var/log/syslog
There were no lines before or after this one that seemed to be relevant.

Thanks in advance,
~~~ 0;-Dan

colord is a service (see https://www.freedesktop.org/software/colord/intro.html) to read or load color profile data. If it is installed and started as part of a package startup to support color profile devices, but you have no such device or there is no profile to read, that is one of the kinds of messages it may log. I believe that it is non-fatal and may be ignored.

Since nothing I use loads or starts colord and I have no direct experience with it, there may be detail I have missed. IF anyone has better information I would like to read about it.

I found the following online:

• COLORD -- The service
• Color Management
• Linux "color schemes"

Somewhere in the last reference -- maybe the last comment -- are more detailed explanations.

Still wanting to learn what I need to do so that I don't get the error message. Clearly, Linux Mint wants end-users to use [b]colord[/d], so, how do I accomplish that?


Follow-up:
There is a command, 'colormgr', that will report devices that might use 'colord'. On my Mint 18.1 laptop, I get:

Code:

---

prompt$ colormgr get-devices | grep Object

Object Path:  /org/freedesktop/ColorManager/devices/xrandr_LVDS1_saint_1000
Object Path:  /org/freedesktop/ColorManager/devices/cups_oj7300
Object Path:  /org/freedesktop/ColorManager/devices/cups_oj7300_fax

---

For those who might not know:

• xrandr -- part of XORG (X-windows) display system
• cups -- the printing sub-system

Clearly, these are two places where color would matter for any workstation.


Thanks in advance,
~~~ 0;-Dan

maybe
knows?

I have a "Color" applet in my 17.3 Rosa Cinnamon menu, and it shows both Displays and Printers.
Odd, since I only have a B/W.

I agree with wpeckham, ignore it.
The juice may not be worth the squeeze.

Likely some "all-or-nothing, kitchen-sink" approach LM tends to utilize. IMO.
Yes, I said it.

There is one school that would move the flat to another wheel and expect/hope that it goes away. While I might not always fix the flat, I want to know what I ran over.

More specifically, I like to understand the source of error and exception messages. Armed with that understanding, I can decide to ignore or to take action based on knowledge.

Since my primary interest in color-anything is the workstation display, I need to learn how to deal with color versus xrandr.

Thanks in advance,
~~~ 0;-Dan