Showing results 281 through 300 of 329 tickets

Ticket	Summary	Reporter	Component			Milestone	Type	Status/Resolution		+1s	Date▼
#4949	DisplayCAL 3.2.0: All tools fail to start on macOS Sierra (10.12.0 and 10.12.1)	Frank Petzold	DisplayCAL 3.2.0				Bug	Resolved	2	0	2016-11-24
#4890	High probability unexpected stop with ColorMunki photo on step “Profiling”	haoli	ArgyllCMS				Bug	Works For Me	1	0	2016-11-19
#4855	Profile 3D HTML view suddenly goes to black (at least in Chrome 54.0.2840.99)	arspr	X3D Viewer				Bug	Works For Me	2	1	2016-11-14
#4790	Resolve as pattern generator doesn’t work	Benedict Heinzl	DisplayCAL			3.2	Bug	Fixed	9	0	2016-11-02
#4780	Color profiles are applied to the wrong display (following the videocard numbering instead of the display model)	Mokona512	DisplayCAL 3.1.6.0			3.1.7.1	Bug	Fixed	4	0	2016-11-02
#4753	ColorMunki Photo Self-Calibration Built-Lamp	Sergio Santos	DisplayCAL 3.1.7.2				Bug	Works For Me	4	0	2016-10-30
#4614	Automatic update with zero install fails	Oliver Bedford	0install				Bug	Fixed	2	0	2016-10-17
#4609	surreal colors when DispCAL is opened. Cant Install profiles.	Joseph Aaron Campbell	DisplayCAL 3.1.7 and Argyll 1.9.2				Bug	Works For Me	5	0	2016-10-17
#4604	auto update of Argyll fails on Windows; due to attempt to download old version number	Dale	Website				Bug	Fixed	3	0	2016-10-17
#4582	Error in dispread on Linux (ColorMunki Smile, Argyll 1.8.3)	ZombieLinux	ArgyllCMS			1.9	Bug	Fixed	1	0	2016-10-16
#4497	Uniformity test in external display	Raikkon35	DisplayCAL 3.1.7				Feature Request	New	0	1	2016-10-08
#4130	Error in ICCProfile.py (SVN r4089)	Jean-Luc Coulon	DisplayCAL svn 4089				Bug	Fixed	1	0	2016-09-15
#4100	‘H’ format requires 0<=number<=65535	Martin Westall	DisplayCAL			3.1.7	Bug	Fixed	1	0	2016-09-13
#4089	Linux: ColorMunki Photo – dispcal: Error – new_disprd failed with ‘Instrument Access Failed’	maxtr	ArgyllCMS 1.8.3				Bug	Duplicate	1	0	2016-09-13
#4066	Black background prevents the RGB adjustment	Raikkon35	ArgyllCMS				Enhancement	New	1	0	2016-09-12
#3976	Windows 10: ColorMunki Display – dispcal: Error – new_disprd failed with ‘Instrument Access Failed’ err 24	rlisario	ArgyllCMS 1.8.3				Bug	New	6	0	2016-09-05
#3965	Aborting Dispcal GUI on centos 7 with newly nvida driver.	daemyeong	ArgyllCMS			1.9 Beta	Bug	Duplicate	5	0	2016-09-05
#3900	I can’t even press the Calibrate & Profile button.	kangarue	DisplayCAL				Bug	Works For Me	1	0	2016-08-31
#3895	Jeti specbos 1201 – dispcal: Error – new_disprd() failed with ‘Instrument Access Failed’	Pete Naples	ArgyllCMS				Bug	New	1	0	2016-08-28
#3783	How long does the resolve cal process take?	Michael B	DisplayCAL				Bug	Invalid	1	0	2016-08-15

Last 5 closed tickets

Ticket	Summary	Reporter	Component			Milestone	Type	Status/Resolution		+1s	Date▼
#25467	DisplayCAL-apply-profiles.exe use ram too much .! need enhancement.	tony-calc	DisplayCAL 3.8.9.3				Enhancement	Rejected	0	1	2020-07-12
#22804	Verification crashes with BadMatch error	Austin Butler	DisplayCAL 3.8.9.3				Bug	Not A Bug	1	0	2020-02-10
#22507	crash with 3D profile information	Patrick Câtel	X3D Viewer 3.8.9.3				Bug	Works For Me	2	0	2020-01-31
#22450	Computing update to calibration curves hangs on 3rd patch	saltarob					Bug	Resolved	2	0	2020-01-27
#22345	Add support for ambient mode readings in DisplayCAL	SirMaster	DisplayCAL				Feature Request	Duplicate	0	0	2020-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.
Fixed	The 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.