Description of problem: System Settings - Color reports no registered devices, and suggests colord isn't running. Version-Release number of selected component (if applicable): Fedora-Live-KDE-x86_64-rawhide-20140523.iso How reproducible: Always. Steps to Reproduce: 1. Open System Settings - Color Actual results: "You do not have any devices registered; Make sure colord module on kded is running." Expected results: At least the display device should be registered automatically. Additional info: See Screenshot and journal attachments.
Created attachment 907315 [details] screenshot of system settings - color
Created attachment 907318 [details] journalctl -b -l -o short-monotonic
Created attachment 907321 [details] journal journalctl -b -l -o short-monotonic I'm not seeing a colord failure, so I'm not sure what's going on. [ 44.667092] localhost colord[1466]: Daemon ready for requests
please post output to the following commands: rpm -q colord colord-kde systemctl status colord
colord-1.2.0-1.fc21.x86_64 colord-kde-0.3.0-2.fc20.x86_64 # systemctl status colord ● colord.service - Manage, Install and Generate Color Profiles Loaded: loaded (/usr/lib/systemd/system/colord.service; static) Active: active (running) since Tue 2014-06-10 12:46:02 MDT; 14s ago Main PID: 965 (colord) CGroup: /system.slice/colord.service └─965 /usr/libexec/colord Jun 10 12:46:02 localhost.localdomain colord[965]: Using mapping database file /var/lib/colord/mapping.db Jun 10 12:46:02 localhost.localdomain colord[965]: Using device database file /var/lib/colord/storage.db Jun 10 12:46:02 localhost.localdomain colord[965]: loaded plugin libcd_plugin_camera.so Jun 10 12:46:02 localhost.localdomain colord[965]: loaded plugin libcd_plugin_scanner.so Jun 10 12:46:02 localhost.localdomain colord[965]: Daemon ready for requests Jun 10 12:46:02 localhost.localdomain systemd[1]: colord.service's D-Bus name org.freedesktop.ColorManager now registered by :1.21 Jun 10 12:46:02 localhost.localdomain systemd[1]: colord.service changed start -> running Jun 10 12:46:02 localhost.localdomain systemd[1]: Job colord.service/start finished, result=done Jun 10 12:46:02 localhost.localdomain systemd[1]: Started Manage, Install and Generate Color Profiles. Jun 10 12:46:03 localhost.localdomain colord[965]: Device added: xrandr-default
Actually comment 5 is wrong, that's for an installed system, and this problem doesn't happen on an installed system, only when booted from live media. I'll try again from the live booted system and report back.
OK from the live system. # systemctl status colord ● colord.service - Manage, Install and Generate Color Profiles Loaded: loaded (/usr/lib/systemd/system/colord.service; static) Active: active (running) since Tue 2014-06-10 14:49:28 EDT; 27min ago Main PID: 1470 (colord) CGroup: /system.slice/colord.service └─1470 /usr/libexec/colord Jun 10 14:49:28 localhost colord[1470]: Using mapping database file /var/lib/colord/mapping.db Jun 10 14:49:28 localhost colord[1470]: Using device database file /var/lib/colord/storage.db Jun 10 14:49:28 localhost colord[1470]: loaded plugin libcd_plugin_camera.so Jun 10 14:49:28 localhost colord[1470]: loaded plugin libcd_plugin_scanner.so Jun 10 14:49:28 localhost colord[1470]: Daemon ready for requests Jun 10 14:49:28 localhost systemd[1]: Started Manage, Install and Generate Color Profiles.
This bug appears to have been reported against 'rawhide' during the Fedora 22 development cycle. Changing version to '22'. More information and reason for this action is here: https://fedoraproject.org/wiki/Fedora_Program_Management/HouseKeeping/Fedora22
Fedora 22 changed to end-of-life (EOL) status on 2016-07-19. Fedora 22 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed.