Hide Forgot
Description of problem: Gnome Color Manager only shows printers to calibrate. I do not see any displays. Version-Release number of selected component (if applicable): 3.22.2-1.fc25 How reproducible: Same result on three machines upgraded from F24 (which suffered the same problem as did prior releases). Steps to Reproduce: 1. Start Color from the settings page 2. Look for display to calibrate 3. Actual results: No display to calibrate Expected results: Display listed to calibrate using colorimeter Additional info: There was a problem about this but I cannot find it now, it could have been raised on F22 or before. Impact? Minimal to me, other than an extra few prints getting things correct. What it does do is stop me recommending Fedora to any keen photographers.
I have been looking through reports of similar problems on ubuntu and other distributions. They all report this starts to happen after gdm went to wayland. Is it perhaps true that wayland does not support colour management? If so this problem should be moved to the wayland team/GDM. I will have to look at other display managers until they fix that. I believe that the problem is not with gnome-color-manager.
This message is a reminder that Fedora 25 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 25. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a Fedora 'version' of '25'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 25 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
Updated version to Fedora 26 to keep this on the radar. I have not had a chance to try Fedora 27 yet. If Fedora 27 fixes the problem then please close.
This message is a reminder that Fedora 26 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 26. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a Fedora 'version' of '26'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 26 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
Fedora 26 changed to end-of-life (EOL) status on 2018-05-29. Fedora 26 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.