Showing results 261 through 280 of 339 tickets

Ticket	Summary	Reporter	Component			Milestone	Type	Status/Resolution		+1s	Date▼
#7486	Profile gets unloaded when using duplicate display on Windows 10	lones710	DisplayCAL 3.3.1				Bug	Can't Fix	5	0	2017-06-09
#7442	‘NoneType’ object has no attribute ‘DeviceKey’	Bram Dispa	DisplayCAL				Bug	Works For Me	13	0	2017-06-06
#7152	i1 Display Error – new_disprd() failed with ‘Instrument Access Failed’	Viktor	ArgyllCMS 1.9.2				Bug	Resolved	4	0	2017-05-23
#7111	Cannot install new profile but preview works great	Martijn Braam	colord				Bug	Can't Fix	4	0	2017-05-19
#6341	New version of profile loader causes stuttering of mouse pointer / video playback (Windows)	boday	DisplayCAL 3.2.4			3.3	Bug	Fixed	8	1	2017-03-21
#6339	New version of profile loader causes stuttering of mouse pointer / video playback (Windows)	boday	3.2.4				Bug	Duplicate	0	0	2017-03-21
#6167	Spyder5 dispcal: Error – new_disprd() failed with ‘Instrument Access Failed’ on LMDE2	ronaldtimmermann	ArgyllCMS 1.9.2				Bug	Resolved	23	0	2017-03-10
#6137	It’s impossible to update profile without reset profile?	tony-calc	DisplayCAL 3.2.4				Feature Request	Works For Me	3	0	2017-03-09
#6135	It’s impossible to change WB without re-calibration?	tony-calc	DisplayCAL 3.2.4				Feature Request	Rejected	1	0	2017-03-09
#6129	Instrument Access Failed for Lenovo P50 X-Rite Pantone sensor	Thomas Danecker	ArgyllCMS				Bug	Not A Bug	1	2	2017-03-08
#6099	Message: ‘NoneType’ object has no attribute ‘DeviceKey’	Ruud de Vreugd	DisplayCAL 3.2.4				Bug	Works For Me	3	0	2017-03-03
#6068	Ask about WB with CIE xy chromaticity and Algorithm.	tony-calc	DisplayCAL 3.2.4				Enhancement	Resolved	1	0	2017-02-26
#6016	Menu bar and sidebars with yellow tint (even in screenshots) with new profile.	benjamino	DisplayCAL				Bug	Not A Bug	1	0	2017-02-22
#5873	Fedora 25 Mate, Profile fails to install	Berwyn					Bug	Not A Bug	3	0	2017-02-13
#5863	AttributeError: ‘NoneType’ object has no attribute ‘strip’	Bruno Pagani	DisplayCAL			3.2.4	Bug	Fixed	11	1	2017-02-12
#5855	i1 Pro2 + TvLogic XVM 32W	FunKKinG	DisplayCAL 3.2.3				Feature Request	Invalid	1	0	2017-02-12
#5759	Spyder2 Instrument Access Failed (Communications failure) Windows 7	Bob R	ArgyllCMS 1.9.2				Bug	New	1	0	2017-02-01
#5732	Spyder 3 Elite and projector	Raoul	DisplayCAL				Enhancement	Not A Bug	6	0	2017-01-30
#5720	Report on uncalibrated display device – dispcal: Error – Got bad color temperature conversion	Asimov	ArgyllCMS				Bug	Won't Fix	1	0	2017-01-29
#5616	CentOS 7: i1Display3 Rev. B – dispcal: Error – display read failed with ‘Instrument Access Failed’ (communication problem)	David	ArgyllCMS 1.9.2				Bug	New	1	0	2017-01-22

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.