Arch Linux

Leeo97one

Member

From: France

Registered: 2017-07-29

Posts: 8

[colord] No screen detected (solved)

See post #3 for a solution.

Hello,

I noticed a few days ago in GNOME settings that my screen was no longer detected:
http://i.imgur.com/F06ByKB.png
"Unable to detect a device to manage its color"

It turns out that GNOME Color Manager uses colord as backend. So I tried directly with colormgr:

[leeo@leeo-arch-pc ~]$ colormgr get-devices
[leeo@leeo-arch-pc ~]$ sudo colormgr get-devices
[sudo] Mot de passe de leeo : 
[leeo@leeo-arch-pc ~]$ 

But nothing...

My screen is detected by xrandr without problem:

[leeo@leeo-arch-pc ~]$ xrandr 
Screen 0: minimum 8 x 8, current 1920 x 1080, maximum 16384 x 16384
DVI-I-0 disconnected (normal left inverted right x axis y axis)
HDMI-0 connected primary 1920x1080+0+0 (normal left inverted right x axis y axis) 531mm x 299mm
   1920x1080     59.93*+  60.00    59.94    50.00    60.05    60.00    50.04  
   1680x1050     59.95  
   1600x900      75.00    60.00  
   1440x900      59.89  
   1366x768      59.79  
   1280x1024     75.02    70.00    60.02  
   1280x720      60.00    59.94    50.00  
   1152x864      75.00  
   1024x768      75.03    70.07    60.00  
   800x600       75.00    72.19    60.32    56.25  
   720x576       50.00  
   720x480       59.94  
   640x480       75.00    72.81    59.94    59.93  
HDMI-1 disconnected (normal left inverted right x axis y axis)
DVI-I-1 disconnected (normal left inverted right x axis y axis)
DP-0 disconnected (normal left inverted right x axis y axis)
DP-1 disconnected (normal left inverted right x axis y axis)

And so the night mode of GNOME no longer works:

juil. 30 21:11:58 leeo-arch-pc gsd-color[3525]: could not find device: property match 'XRANDR_name'='HDMI-0' does not exist
juil. 30 21:11:59 leeo-arch-pc gsd-color[3525]: could not find device: property match 'XRANDR_name'='HDMI-0' does not exist
juil. 30 21:11:59 leeo-arch-pc gsd-color[3525]: could not find device: property match 'XRANDR_name'='HDMI-0' does not exist
juil. 30 21:12:01 leeo-arch-pc gsd-color[3525]: could not find device: property match 'XRANDR_name'='HDMI-0' does not exist

Knowing that I reinstalled Arch Linux a short time ago and that it worked very well for a few days.

Last edited by Leeo97one (2017-07-31 14:19:40)

jasonwryan

Anarchist

From: .nz

Registered: 2009-05-09

Posts: 30,424

Website

Re: [colord] No screen detected (solved)

Read the Code of Conduct and only post thumbnails http://wiki.archlinux.org/index.php/Cod … s_and_code

---

Arch + dwm   •   Mercurial repos  •   Surfraw

Registered Linux User #482438

Leeo97one

Member

From: France

Registered: 2017-07-29

Posts: 8

Re: [colord] No screen detected (solved)

I found an interesting message in journalctl:

juil. 31 12:48:00 leeo-arch-pc gsd-color[550]: failed to create device: could not check org.freedesktop.color-manager.create-device for auth: GDBus.Error:org.freedesktop.PolicyKit1.Error.NotAuthorized: Only trusted callers (e.g. uid 0 or an action owner) can use CheckAuthorization() for subjects belonging to other identities

I have a solution! You have to delete (or move) the file /usr/share/polkit-1/actions/org.freedesktop.color-manager.create-device.policy and reinstall the colord package.
It's a file created by NoMachine during the installation but I don't know why this prevent gsd-color to create devices...

Last edited by Leeo97one (2017-08-17 12:41:42)

sumit_anantwar

Member

Registered: 2015-03-19

Posts: 3

Re: [colord] No screen detected (solved)

@Leeo97one, you just did not save my day, you saved my week!
Was struggling with this for more than a week, and reinstalled Arch twice.

Thank you !

vik1313

Member

Registered: 2024-01-26

Posts: 13

Re: [colord] No screen detected (solved)

I found an interesting message in journalctl:

juil. 31 12:48:00 leeo-arch-pc gsd-color[550]: failed to create device: could not check org.freedesktop.color-manager.create-device for auth: GDBus.Error:org.freedesktop.PolicyKit1.Error.NotAuthorized: Only trusted callers (e.g. uid 0 or an action owner) can use CheckAuthorization() for subjects belonging to other identities

I have a solution! You have to delete (or move) the file /usr/share/polkit-1/actions/org.freedesktop.color-manager.create-device.policy and reinstall the colord package.
It's a file created by NoMachine during the installation but I don't know why this prevent gsd-color to create devices...

Not working for me........I could not find any such file  org.freedesktop.color-manager.create-device.policy but i deleted the color-policy file and reinstalled colord...but still nothing...not detecting.
Thus nightlight is also not working

lenhuppe

Member

From: New Hampshire USA

Registered: 2018-12-10

Posts: 281

Website

Re: [colord] No screen detected (solved)

I found a workaround on my system. I was getting the following after installing Gnome Shell:

systemctl status colord.service

× colord.service - Manage, Install and Generate Color Profiles
     Loaded: loaded (/usr/lib/systemd/system/colord.service; static)
     Active: failed (Result: exit-code) since Sun 2024-01-28 10:06:46 EST; 28s ago
    Process: 1078 ExecStart=/usr/lib/colord (code=exited, status=1/FAILURE)
   Main PID: 1078 (code=exited, status=1/FAILURE)
        CPU: 37ms

Jan 28 10:06:46 lurch systemd[1]: Starting Manage, Install and Generate Color Profiles...
Jan 28 10:06:46 lurch colord[1078]: CdMain: failed to load mapping database: Can't open database: unable to open database file
Jan 28 10:06:46 lurch systemd[1]: colord.service: Main process exited, code=exited, status=1/FAILURE
Jan 28 10:06:46 lurch systemd[1]: colord.service: Failed with result 'exit-code'.
Jan 28 10:06:46 lurch systemd[1]: Failed to start Manage, Install and Generate Color Profiles.

After looking closer at colord I tried the following:

sudo /usr/lib/colord --immediate-exit
sudo systemctl daemon-reload
sudo systemctl start colord.service

Now I am getting the following:

systemctl status colord.service

● colord.service - Manage, Install and Generate Color Profiles
     Loaded: loaded (/usr/lib/systemd/system/colord.service; static)
     Active: active (running) since Sun 2024-01-28 10:09:04 EST; 10ms ago
   Main PID: 2328 (colord)
      Tasks: 5 (limit: 37602)
     Memory: 4.7M (peak: 4.9M)
        CPU: 30ms
     CGroup: /system.slice/colord.service
             └─2328 /usr/lib/colord

Jan 28 10:09:04 lurch systemd[1]: Starting Manage, Install and Generate Color Profiles...
Jan 28 10:09:04 lurch systemd[1]: Started Manage, Install and Generate Color Profiles.

When I looked closer I found that the colord.service file changed a lot in the last update.

colord version 1.4.7-1

[Unit]
Description=Manage, Install and Generate Color Profiles

[Service]
Type=dbus
BusName=org.freedesktop.ColorManager
ExecStart=/usr/lib/colord
User=colord
PrivateTmp=yes
ProtectSystem=strict
ProtectHome=true
ProtectHostname=true
ProtectKernelTunables=true
ProtectKernelModules=true
ProtectKernelLogs=true
ProtectControlGroups=true
RestrictRealtime=true
RestrictAddressFamilies=AF_UNIX

# drop all capabilities
CapabilityBoundingSet=~CAP_SETUID CAP_SETGID CAP_SETPCAP CAP_SYS_ADMIN CAP_SYS_PTRACE CAP_CHOWN CAP_FSETID CAP_SETFCAP CAP_DAC_OVERRIDE CAP_DAC_READ_SEARCH CAP_FOWNER CAP_IPC_OWNER CAP_NET_ADMIN CAP_SYS_RAWIO CAP_SYS_TIME CAP_AUDIT_CONTROL CAP_AUDIT_READ CAP_AUDIT_WRITE CAP_KILL CAP_MKNOD CAP_NET_BIND_SERVICE CAP_NET_BROADCAST CAP_NET_RAW CAP_SYS_NICE CAP_SYS_RESOURCE CAP_MAC_ADMIN CAP_MAC_OVERRIDE CAP_SYS_BOOT CAP_LINUX_IMMUTABLE CAP_IPC_LOCK CAP_SYS_CHROOT CAP_BLOCK_SUSPEND CAP_LEASE CAP_SYS_PACCT CAP_SYS_TTY_CONFIG CAP_WAKE_ALARM

NoNewPrivileges=true
PrivateUsers=true
ProtectProc=invisible
ProcSubset=pid
RestrictSUIDSGID=true
SystemCallArchitectures=native

RestrictNamespaces=~cgroup user pid net uts mnt ipc

LockPersonality=true
MemoryDenyWriteExecute=true
RemoveIPC=true

colord version 1.4.6-1

[Unit]
Description=Manage, Install and Generate Color Profiles

[Service]
Type=dbus
BusName=org.freedesktop.ColorManager
ExecStart=/usr/lib/colord
User=colord
# We think that udev's AF_NETLINK messages are being filtered when
# network namespacing is on.
# PrivateNetwork=yes
PrivateTmp=yes

Along the way I saw a message when running 'systemctl status colord' that stated something about starting too soon.

Perhaps someone more versed in systemd service files can offer some advice on this one.

---

"I'm suspicious of people who don't like dogs, but I trust a dog when it doesn't like a person."  -- Bill Murray

bluewolf

Member

Registered: 2022-01-04

Posts: 2

Re: [colord] No screen detected (solved)

sudo /usr/lib/colord --immediate-exit
sudo systemctl daemon-reload
sudo systemctl start colord.service

Now I am getting the following:

systemctl status colord.service

Lenhuppe - big thank you for this workaround. I saved a ton of time to sort this issue.

Last edited by bluewolf (2024-02-03 18:55:48)

AmrLou

Member

Registered: 2024-02-03

Posts: 9

Re: [colord] No screen detected (solved)

lenhuppe thanks so much! I nearly lost any hope in using such a basic function like night color on my fresh gnome.

seth

Member

Registered: 2012-09-03

Posts: 58,687

Re: [colord] No screen detected (solved)

Please see https://bbs.archlinux.org/viewtopic.php … 2#p2147772 instead of the restart dance.

---

How to upload text · How to boot w/o GUI · Disable Windows Fast-Start! · Fix your xinitrc

ewaller

Administrator

From: Pasadena, CA

Registered: 2009-07-13

Posts: 20,193

Re: [colord] No screen detected (solved)

Please see https://bbs.archlinux.org/viewtopic.php … 2#p2147772 instead of the restart dance.

I concur.   Closing this thread.

---

Nothing is too wonderful to be true, if it be consistent with the laws of nature -- Michael Faraday
Sometimes it is the people no one can imagine anything of who do the things no one can imagine. -- Alan Turing
---
How to Ask Questions the Smart Way