Showing results 281 through 300 of 339 tickets

Ticket	Summary	Reporter	Component			Milestone	Type	Status/Resolution		+1s	Date▼
#5480	BSOD – PAGE_FAULT_IN_NONPAGED_AREA – HIDClass.sys – W10 – i1Display Pro	seiferflo	DisplayCAL				Bug	Works For Me	3	0	2017-01-12
#5458	Profile Avatar	drewbyty	Website				Bug	Works For Me	2	0	2017-01-09
#5420	relatively high CPU usage of profile loader applet on Windows	Dale	DisplayCAL 3.2.3				Enhancement	Won't Fix	3	0	2017-01-08
#5354	Profile Loader Crashes after attaching a beamer	Sylvio Kurze	DisplayCAL 3.2.2			3.2.3	Bug	Fixed	2	0	2017-01-04
#5224	Linux Mint 17.2: Spyder5 – dispcal: Error – new_disprd() failed with ‘Instrument Access Failed’ (Permissions?)	ronaldtimmermann	ArgyllCMS 1.9.2				Bug	Works For Me	13	0	2016-12-25
#5142	DisplayCAL does not start on Ubuntu 16.04	Will Jackson	python-wxgtk3.0				Bug	Can't Fix	1	0	2016-12-18
#5141	Windows 10: ColorMunki Display – dispcal: Error – new_disprd() failed with ‘Instrument Access Failed’ err 18	goku	ArgyllCMS 1.9.2				Bug	New	4	3	2016-12-17
#5110	upgrade 3.1.7.2 -> 3.2.2 on Windows 10 x64 did not upgrade profile loader	Dale	DisplayCAL 0install Setup (Windows)				Bug	Fixed	6	0	2016-12-14
#5037	profile loader throws error when Windows resumes from sleep	Michael Levy	DisplayCAL 3.2.1			3.2.2	Bug	Fixed	3	0	2016-12-03
#5031	Generating diagnostic 3D views of testcharts failes – error msg: SSLV3_ALERT_HANDSHAKE_FAILURE	ulfertg	DisplayCAL 3.2.1			3.2.2	Bug	Fixed	1	0	2016-12-03
#4996	Windows 10 Home: Cannot install Argyll CMS instrument drivers – Unexpected COM Error, OLE error 0x80041002	Manuelcm	DisplayCAL 3.2.1			3.2.2	Bug	Fixed	1	0	2016-11-27
#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

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.