Issue Tracker

Add new ticket

356 tickets (193 closed, 163 open)
#39246Calibrating flanders CM240wragge75BugNew002023-03-20
#39131Cannot load 3D view : file “…[<generator object ProfileInfoFrame.view_3d.. at 0x7faa303c4970>] vs sRGB [A].wrz” does not existfenugrecDisplayCAL 3.9.10BugNew002023-02-27
#39088display cal and Argyll on apple M1 Big Sur for Display2 xrite – MACGiuseppe.miriArgyllCMSBugNew002023-02-14
#38965displaycal -d parameter 2 out of range?WolfyBugNew002023-01-27
#38248Unable to install Argyll driversabdullah hemidaArgyll USB driver installer (Windows)BugNew0122023-01-03
#38216Displaycal can’t download and install newest version of ArgyllCMSGokuo64BugNew062022-12-31
#38162Error – dispd-> read returned error code 2Charles DaigleDisplayCAL
#38082ValueError: cannot convert float NaN to integerrifoDisplayCALBugNew002022-12-15
#37571Discouraged mime in Linux desktop entryAlberto Salvia NovellaDisplayCAL 3.9.6BugNew002022-11-04
#37406Waiting for connection
#37206Diagnostic: -d parameter 1 out of rangeRune PedersenBugNew012022-09-28
#37202Eizo CG222W + Big Sur and Monterey + Spyder3 ProDavideDisplayCAL
#37200Eizo CG222W + Big Sur and Monterey + Spyder3 ProDavideDisplayCAL

Last 5 closed tickets

#25467DisplayCAL-apply-profiles.exe use ram too much .! need enhancement.tony-calcDisplayCAL
#22804Verification crashes with BadMatch errorAustin ButlerDisplayCAL A Bug102020-02-10
#22507crash with 3D profile informationPatrick CâtelX3D Viewer For Me202020-01-31
#22450Computing update to calibration curves hangs on 3rd patchsaltarobBugResolved202020-01-27
#22345Add support for ambient mode readings in DisplayCALSirMasterDisplayCALFeature RequestDuplicate002020-01-20

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.
Not A Bug The reported issue is not a bug.
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.

Display Calibration and Characterization powered by ArgyllCMS