Issue Tracker—New Tickets

Add new ticket

73/89
89 tickets (73 closed, 16 open)
TicketSummaryReporterComponentMilestoneTypeStatus/Resolution+1sDate▼
#7837“Apply black output offset (100%)” option unavailable in Verification window when Settings is set to Current , but becomes available after briefly visiting Profiling window and going back to VerificationEricNew102017-07-09
#7566ColorMunki Photo at Win10 always fails with the dispcal: Error – display read failed with ‘Instrument Access Failed’AlexBNew002017-06-17
#7442‘NoneType’ object has no attribute ‘DeviceKey’Bram DispaNew1302017-06-06
#7237Error – new_disprd() failed with “Instrument Access Failed” on Mac OSX Sierradspasoski 1.9.2New002017-05-29
#6167dispcal: Error – new_disprd() failed with ‘Instrument Access Failed’ on LMDE2ronaldtimmermann 1.9.2New2202017-03-10
#5759Spyder2 Not workingBob RNew102017-02-01
#5616CentOS 7: i1Display3 Rev. B – dispcal: Error – display read failed with ‘Instrument Access Failed’ (communication problem)David 1.9.2New102017-01-22
#5141Windows 10: ColorMunki Display – dispcal: Error – new_disprd() failed with ‘Instrument Access Failed’ err 18goku 1.9.2New322016-12-17
#4497Uniformity test in external displayRaikkon35 3.1.7New002016-10-08
#4066Black background prevents the RGB adjustmentRaikkon35New102016-09-12
#3976Windows 10: ColorMunki Display – dispcal: Error – new_disprd failed with ‘Instrument Access Failed’ err 24rlisario 1.8.3New602016-09-05
#3895Jeti specbos 1201 – dispcal: Error – new_disprd() failed with ‘Instrument Access Failed’Pete NaplesNew102016-08-28
#3767Windows 7: ColorMunki Display – dispcal: Error – new_disprd() failed with ‘Instrument Access Failed’ (communications failure)iMiKED 1.8.3New102016-08-11
#3156Support for built-in Lenovo Pantone Huey?xane 1.8.3New102016-05-31

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.