Issue Tracker—New Tickets

Add new ticket

90/124
124 tickets (90 closed, 34 open)
TicketSummaryReporterComponentMilestoneTypeStatus/Resolution+1sDate▼
#10138calibrate lenovo y50 (rec 709)oscaravBugNew002018-01-20
#10068DisplayCAL-apply-profiles.exe: unrecognized option `–skip’rafikDisplayCAL 3.4.0.0BugNew1702018-01-16
#10020Cannot Start Calibration with Spyder 3 and Resolve 12.5 on Mac OS Yosemite 10.10.5troyDisplayCALBugNew302018-01-09
#10017Mac Sierra – black too deepcameraboyBugNew102018-01-09
#9990dispread.exe has stopped working (madVR)latexiiArgyllCMS (64-bit) 2.0BugNew602018-01-02
#9864Error when booting Ubuntu 18.04CalbyDisplayCAL 3.3.5-01BugNew102017-12-26
#9861Can’t install profile Ubuntu 18.04CalbyDisplayCAL 3.3.5-01BugNew002017-12-26
#9672Cannot run on El CapitanMorten Hogholm PedersenDisplayCALBugWorks For Me302017-12-02
#9670Spectral correction creation always sets display type=refreshP-T-RDisplayCALBugNew102017-12-02
#9668Ability to define end of process behaviourP-T-RDisplayCALFeature RequestNew002017-12-02
#9507Mouse hangs every three secondsesparrowDisplayCALBugWorks For Me512017-11-14
#9490new_disprd failed with ‘Instrument Access Failed’Jim photogArgyllCMSBugNew002017-11-13
#9174Instrument Access Failed with Klein K10A on multiple machineskoperfildArgyllCMSBugNew002017-10-17
#9123Colormunki not detected on Win7 machinebmcn2002ArgyllCMSBugNew012017-10-12
#8951Display calibration hangs on “Using CAM Jab for clipping”proslambanomenosDisplayCALBugNew1012017-09-21
#8420Problems with Specbos 1201 messurementNeoDeeArgyllCMS 1.9.2BugNew102017-08-16
#7566ColorMunki Photo at Win10 always fails with the dispcal: Error – display read failed with ‘Instrument Access Failed’AlexBArgyllCMSBugNew302017-06-17
#7237Error – new_disprd() failed with “Instrument Access Failed” on Mac OSX SierradspasoskiArgyllCMS 1.9.2BugNew002017-05-29
#6167dispcal: Error – new_disprd() failed with ‘Instrument Access Failed’ on LMDE2ronaldtimmermannArgyllCMS 1.9.2BugNew2302017-03-10
#5759Spyder2 Not workingBob RArgyllCMSBugNew102017-02-01

Last 5 closed tickets

TicketSummaryReporterComponentMilestoneTypeStatus/Resolution+1sDate▼
#9314Cannot detect Spyder5dangelic0DisplayCALBugWorks For Me202017-11-03
#9216Disable “Apply calibration (vcgt)” while creating 3D LUT for madVR by default?bodayDisplayCALEnhancementRejected302017-10-23
#9214Option to disable profile loader pop-up notifications?bodayDisplayCAL3.4Feature RequestImplemented302017-10-22
#9210report on uncorrected deviceAntonio MarcheselliDisplayCAL 3.3.5BugNot A Bug302017-10-22
#9164Windows 7 crash at reboottonymickDisplayCAL Standalone Setup (Windows)BugWorks For Me202017-10-17

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.