Issue Tracker—Component: DisplayCAL

Add new ticket

41 tickets (36 closed, 5 open)
#5863AttributeError: ‘NoneType’ object has no attribute ‘strip’Bruno PaganiResolved1112017-02-12
#5855i1 Pro2 + TvLogic XVM 32WFunKKinG 3.2.3New102017-02-12
#5732Spyder 3 Elite and projectorRaoulNew602017-01-30
#5480BSOD – PAGE_FAULT_IN_NONPAGED_AREA – HIDClass.sys – W10 – i1Display ProseiferfloWorks For Me302017-01-12
#5420relatively high CPU usage of profile loader applet on WindowsDale 3.2.3Won't Fix302017-01-08
#5354Profile Loader Crashes after attaching a beamerSylvio Kurze 3.2.2Fixed202017-01-04
#5037profile loader throws error when Windows resumes from sleepMichael Levy 3.2.1Fixed302016-12-03
#5031Generating diagnostic 3D views of testcharts failes – error msg: SSLV3_ALERT_HANDSHAKE_FAILUREulfertg 3.2.1Fixed102016-12-03
#4996Windows 10 Home: Cannot install Argyll CMS instrument drivers – Unexpected COM Error, OLE error 0x80041002Manuelcm 3.2.1Fixed102016-11-27
#4949DisplayCAL 3.2.0: All tools fail to start on macOS Sierra (10.12.0 and 10.12.1)Frank Petzold 3.2.0Resolved202016-11-24
#4790Resolve as pattern generator doesn’t workBenedict HeinzlFixed902016-11-02
#4780Color profiles are applied to the wrong display (following the videocard numbering instead of the display model)Mokona512
#4753ColorMunki Photo Self-Calibration Built-LampSergio Santos For Me402016-10-30
#4609surreal colors when DispCAL is opened. Cant Install profiles.Joseph Aaron Campbell 3.1.7 and Argyll 1.9.2Works For Me502016-10-17
#4497Uniformity test in external displayRaikkon35 3.1.7New002016-10-08
#4130Error in (SVN r4089)Jean-Luc Coulon svn 4089Fixed102016-09-15
#4100‘H’ format requires 0<=number<=65535Martin WestallFixed102016-09-13
#3900I can’t even press the Calibrate & Profile button.kangarueWorks For Me102016-08-31
#3783How long does the resolve cal process take?Michael BorensteinInvalid102016-08-15
#3524Spyder 5 eliteSamir SawantInvalid202016-07-12

Ticket Tags

Ticket Legend

Can't Fix The reported issue is not in scope for this project, e.g. the problem is related to an external project and needs to be fixed there.
Duplicate There is already another ticket about the same issue. See the ticket comments for a link to the original ticket.
FixedThe reported issue has been fixed. If a milestone is given, it indicates the minimum version that will include the fix.
Implemented The feature or enhancement has been implemented. If a milestone is given, it indicates the minimum version that will include the feature or enhancement.
Invalid The ticket is not a valid bug report, feature request or enhancement.
Rejected The reported issue is not really a problem, or the feature/enhancement was decided to be unsuitable for implementation.
Resolved The reported issue is believed to be resolved, but review may be needed to determine if it is really fixed. Occasionally also used to leave a fixed ticket open to be able to collate feedback.
Won't Fix The reported issue does not warrant a fix.
Works For Me The reported issue could not be reproduced.