Bug 957192

Summary:	Colorhug fails to calibrate screen
Product:	[Fedora] Fedora	Reporter:	bbzsz
Component:	gnome-color-manager	Assignee:	Richard Hughes <rhughes>
Status:	CLOSED EOL	QA Contact:	Fedora Extras Quality Assurance <extras-qa>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	19	CC:	acc-bugz-redhat, bbzsz, iny, ormandj, rhughes
Target Milestone:	---
Target Release:	---
Hardware:	i686
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2015-02-17 15:04:48 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description bbzsz 2013-04-26 14:53:14 UTC

Description of problem:
Tried calibrating my screen with a colorhug on Fedora 19 Alpha. It brings up the screen to put the colorhug on and I pressed start, it remained white and the colorhug's LED was off. 

(This same colorhug works flawlessly on Fedora 18 so it's not a hardware problem)

Version-Release number of selected component (if applicable):
gnome-color-manager-3.8.1-1.fc19.i686
colord-0.1.33-1.fc19.i686

How reproducible:


Steps to Reproduce:
1. Plug colorhug in
2. Click Calibrate button with screen selected
3. Select 'high 40 minutes'
4. Click continue on brightness question
5. Place colorhug on square
6. Click start
  
Actual results:
Square turns white and progress bar progresses without any other changes on the screen and the colorhug's LED remains off.

Expected results:
Square changes colours as the colorhug calibrates the screen (colorhug LED on showing calibration in progress).

Comment 1 Richard Hughes 2013-04-29 15:42:41 UTC

(In reply to comment #0)
> Square turns white and progress bar progresses without any other changes on
> the screen and the colorhug's LED remains off.

Does the progressbar get to 100%? Does it produce a profile? If so, can you attach it here please. Thanks.

Comment 2 Richard Hughes 2013-04-30 10:57:19 UTC

I think this might be the same bug as https://bugzilla.gnome.org/show_bug.cgi?id=699250

Comment 3 bbzsz 2013-05-02 22:52:26 UTC

Okay. I have re-run the calibration and waited longer this time. It actually does change colour (the first 10 minutes or so it's so subtle I didn't realise). After maybe 20 - 30 minutes (on the 'High' option) it then says that the calibration has failed and could not create the calibration profile.

The blue bar duing the time did progress.

Comment 4 Richard Hughes 2013-12-11 10:40:43 UTC

Can you try with argyllcms-1.6.2 please, thanks.

Comment 5 tuxor 2013-12-11 20:12:52 UTC

The calibration still fails for me with argyllcms 1.6.2 from updates-testing. I attached the debug output to the bug linked to in Comment #2 on Gnome Bugzilla.

Comment 6 David Orman 2014-04-04 02:20:51 UTC

I have the same problem, using an i1Display 2 (modified udev as per your commit for another bug report) with Fedora 20. Low/Medium work fine, High fails about 3/4 through. Let me know what information I can provide to help you with this issue.

Comment 7 tuxor 2014-10-26 22:58:01 UTC

Isn't it a bit tough that the ColorHug hasn't been working with Fedora since 19 (i.e. from the beginning of 2013), even though the inventor of ColorHug is more or less part of the Fedora team? Even with Fedora 21, calibration with ColorHug isn't functional (see bug #1157279).

Comment 8 Fedora End Of Life 2015-01-09 17:58:51 UTC

This message is a notice that Fedora 19 is now at end of life. Fedora 
has stopped maintaining and issuing updates for Fedora 19. It is 
Fedora's policy to close all bug reports from releases that are no 
longer maintained. Approximately 4 (four) weeks from now this bug will
be closed as EOL if it remains open with a Fedora 'version' of '19'.

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 19 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.

Comment 9 Fedora End Of Life 2015-02-17 15:04:48 UTC

Fedora 19 changed to end-of-life (EOL) status on 2015-01-06. Fedora 19 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.