Bug 1991561 - colord's SE39UY04 profile is worse than no profile
Summary: colord's SE39UY04 profile is worse than no profile
Keywords:
Status: CLOSED EOL
Alias: None
Product: Fedora
Classification: Fedora
Component: colord
Version: 35
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Richard Hughes
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2021-08-09 12:36 UTC by D. Hugh Redelmeier
Modified: 2022-12-13 15:33 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: ---
Doc Text:
Clone Of:
Environment:
Last Closed: 2022-12-13 15:33:49 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)

Description D. Hugh Redelmeier 2021-08-09 12:36:36 UTC
Description of problem:
The colour profile for the Seiki SE39UY04 is horrible, at least for mine.
Everything has a yellow cast.
There was no profile in Fedora 33 and that was much much better.


Version-Release number of selected component (if applicable):
colord-1.4.5-2.fc34.x86_64

How reproducible:
100%

Steps to Reproduce:
1. use Seiki SE39UY04
2. observe horrible colours

Actual results:
A terrible yellow cast to everything on screen.

Expected results:
A display at least as nice as on Fedora 33

Additional info:
As a work-around, I told Gnome to use the profile for a Dell UP3216Q.  The result seem much better.  Dell 2405fpw seems similar.

Suggested fix: delete the SE39UY04 profile.
Alternative: get me a calibration tool and I'll try to create a better profile.

Comment 1 Ben Cotton 2022-05-12 16:28:10 UTC
This message is a reminder that Fedora Linux 34 is nearing its end of life.
Fedora will stop maintaining and issuing updates for Fedora Linux 34 on 2022-06-07.
It is Fedora's policy to close all bug reports from releases that are no longer
maintained. At that time this bug will be closed as EOL if it remains open with a
'version' of '34'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, change the 'version' 
to a later Fedora Linux version.

Thank you for reporting this issue and we are sorry that we were not 
able to fix it before Fedora Linux 34 is end of life. If you would still like 
to see this bug fixed and are able to reproduce it against a later version 
of Fedora Linux, you are encouraged to change the 'version' to a later version
prior to this bug being closed.

Comment 2 D. Hugh Redelmeier 2022-05-26 18:58:00 UTC
Still true on Fedora 35.  This is on a system upgraded from Fedora 34 using the DNF procedure.

Comment 3 Ben Cotton 2022-11-29 17:03:06 UTC
This message is a reminder that Fedora Linux 35 is nearing its end of life.
Fedora will stop maintaining and issuing updates for Fedora Linux 35 on 2022-12-13.
It is Fedora's policy to close all bug reports from releases that are no longer
maintained. At that time this bug will be closed as EOL if it remains open with a
'version' of '35'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, change the 'version' 
to a later Fedora Linux version.

Thank you for reporting this issue and we are sorry that we were not 
able to fix it before Fedora Linux 35 is end of life. If you would still like 
to see this bug fixed and are able to reproduce it against a later version 
of Fedora Linux, you are encouraged to change the 'version' to a later version
prior to this bug being closed.

Comment 4 Ben Cotton 2022-12-13 15:33:49 UTC
Fedora Linux 35 entered end-of-life (EOL) status on 2022-12-13.

Fedora Linux 35 is no longer maintained, which means that it
will not receive any further security or bug fix updates. As a result we
are closing this bug.

If you can reproduce this bug against a currently maintained version of Fedora Linux
please feel free to reopen this bug against that version. Note that the version
field may be hidden. Click the "Show advanced fields" button if you do not see
the version field.

If you are unable to reopen this bug, please file a new report against an
active release.

Thank you for reporting this bug and we are sorry it could not be fixed.


Note You need to log in before you can comment on or make changes to this bug.