Issue Tracker

Add new ticket

193/339
339 tickets (193 closed, 146 open)
TicketSummaryReporterComponentMilestoneTypeStatus/Resolution+1sDate▼
#37406Waiting for connection 192.168.50.33:20002MatthiasashfordBugNew002022-10-21
#37206Diagnostic: -d parameter 1 out of rangeRune PedersenBugNew312022-09-28
#37202Eizo CG222W + Big Sur and Monterey + Spyder3 ProDavideDisplayCAL 3.8.9.3BugNew002022-09-26
#37200Eizo CG222W + Big Sur and Monterey + Spyder3 ProDavideDisplayCAL 3.8.9.3BugNew002022-09-26
#37198Eizo CG222W + Big Sur and Monterey + Spyder3 ProDavideDisplayCAL 3.8.9.3BugNew002022-09-26
#37188diagnostics -d parameter 1 out of rangeAntonisDisplayCALBugNew322022-09-24
#37068No Instrument Dropdown and Start calibration key not activeDonald SandholmDisplayCALBugNew102022-09-18
#36843Feature request: Option to launch DisplayCAL from Profile Loader tray iconanthroidDisplayCAL 3.8.9.3Feature RequestNew002022-09-10
#36208No one here, Just move to https://github.com/eoyilmaz/displaycal-py3tony-calcDisplayCALEnhancementNew112022-07-31
#36163Python TypeError, visual whitepoint editorwwklnd 3.9.6BugNew002022-07-25
#36030Error Message after Start MeasurementCharles SilvermanDisplayCAL 3.8.9.3BugNew002022-07-16
#35923dispread: Error – new_disprd failed with ‘Unknown calibration display type ↲ ↳ selection’DAI YALIDisplayCAL 3.8.9.3BugNew002022-07-06
#35661Xrite Calibrite Colorchecker display pro problemtomwmanBugNew112022-06-19
#34939DisplayCAL not working with secondary monitorsPleaseHelp2020DisplayCALBugNew002022-03-28
#34929dispread: Error – new_disprd failed with ‘Instrument Access Failed’Sergey KArgyllCMS 3.8.9.3BugNew002022-03-28
#34537[Errno 8] nodename nor servname provided, or not knownGaloisBugNew002022-02-27
#34534DisplayCal Profile LoaderUrielDisplayCALBugNew102022-02-27
#34465Cannot view correction of monitor with similar name in colorimeter corrections databasedogelitionWebsiteBugNew002022-02-21
#34107Profile created is named after display that was calibrated the last time DisplayCAL ran instead of the most recent displayZianDisplayCALBugNew012022-02-04
#34043Can’t signup to forumdisplayMonkeyWebsiteBugNew102022-02-02

Last 5 closed tickets

TicketSummaryReporterComponentMilestoneTypeStatus/Resolution+1sDate▼
#25467DisplayCAL-apply-profiles.exe use ram too much .! need enhancement.tony-calcDisplayCAL 3.8.9.3EnhancementRejected012020-07-12
#22804Verification crashes with BadMatch errorAustin ButlerDisplayCAL 3.8.9.3BugNot A Bug102020-02-10
#22507crash with 3D profile informationPatrick CâtelX3D Viewer 3.8.9.3BugWorks 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