Description of problem: When a non-default color profile has been selected for a display, it is not actually applied during KDE startup. I have to use the System Settings --> Color applet to "toggle" the display's profile to something else and then back to the desired color profile, at which point it is actually applied. Version-Release number of selected component (if applicable): colord-kde.x86_64 0.2.0-2.fc18 How reproducible: 100% Steps to Reproduce: 1. Use the Color applet to select a visually distinctive color profile for a display. ("Test profile: Blue" seems to work best.) Note that the display immediately looks bluish, because the selected color profile has been applied. 2. Log out and log back in to KDE. 3. Note that display does not have a bluish appearance. 4. Open Color applet and note that "Test profile: Blue" is still the selected profile for the display, even thought it's not actually being used. 5. Select the default profile for the display and then re-select "Test profile: Blue". Note that the display once again appears bluish. Actual results: Selected color profile is not applied at KDE startup. Expected results: Selected color profile should be automatically applied. Additional info: GNOME does not suffer from this issue. The selected profile is used automatically (even if it has been selected in KDE).
New release (fixing this bug and others) pending, stay tuned :)
(In reply to comment #1) > New release (fixing this bug and others) pending, stay tuned :) Hmm, I don't see anything in Koji. I hope you're not planning on waiting for a new upstream release.
*** Bug 956333 has been marked as a duplicate of this bug. ***
Created attachment 740867 [details] SPEC file to build from upstream git I don't have any confidence that there will be a new upstream release any time soon. Here is a SPEC file to build from the current git snapshot, which fixes both this issue and 956333.
Yes there will be, I have only a few TODOs pending before I do one.
(In reply to Daniel Nicoletti from comment #5) > Yes there will be, I have only a few TODOs pending before I do one. I am happy to see that my scepticism was unfounded. Thank you, Daniel! Lukáš - Can we get an update to 0.3.0? (And I'd suggest updating the %files section, so that the RPM doesn't claim /usr/share/kde4/services/kded.) Thanks!
colord-kde-0.3.0-1.fc18 has been submitted as an update for Fedora 18. https://admin.fedoraproject.org/updates/colord-kde-0.3.0-1.fc18
Package colord-kde-0.3.0-1.fc18: * should fix your issue, * was pushed to the Fedora 18 testing repository, * should be available at your local mirror within two days. Update it with: # su -c 'yum update --enablerepo=updates-testing colord-kde-0.3.0-1.fc18' as soon as you are able to, then reboot. Please go to the following url: https://admin.fedoraproject.org/updates/FEDORA-2013-9402/colord-kde-0.3.0-1.fc18 then log in and leave karma (feedback).
colord-kde-0.3.0-1.fc18 has been pushed to the Fedora 18 stable repository. If problems still persist, please make note of it in this bug report.