I installed a color profile for my LCD monitor. When I start KDE, the correct profile is applied but 1second later, it is disabled. I see that because the background picture changes dramatically. Why? Frédéric
On Jul 17, 2014, at 1:21 PM, Frédéric Bron frederic.bron@m4x.org wrote:
I installed a color profile for my LCD monitor.
Where did it come from? Most manufacturer supplied ICC profiles are junk. a.) Frequently aren't made correctly; b.) don't actually describe the display's behavior better than the colord created on based on EDID primaries, often worse.
When I start KDE, the correct profile is applied but 1second later, it is disabled. I see that because the background picture changes dramatically. Why?
Can you see anything in the journal at the time of starting KDE and subsequent disabling?
In a shell use journalctl -f, and then in a separate shell start KDE and note anything in the "journal following" shell if there's anything related at the time the profile is disabled.
What do you get for? colormgr get-devices
Chris Murphy
On Mon, 2014-07-21 at 13:48 -0600, Chris Murphy wrote:
Most manufacturer supplied ICC profiles are junk. a.) Frequently aren't made correctly; b.) don't actually describe the display's behavior better than the colord created on based on EDID primaries, often worse.
Considering that you can connect several, allegedly, identical monitors to view the same image simultaneously, and get glaringly obvious differences between each monitor, I'm not surprised.
There's a very wide tolerance in electronics, including the actual display, as well as what drives it. You really need profiles to be a measurement of the actual display that you're using, taking into account its user-settings and your room lighting.
Hi, thanks for help,
I installed a color profile for my LCD monitor.
Where did it come from?
I measured it with a colorimeter using argyllcms.
What do you get for? colormgr get-devices
... Object Path: /org/freedesktop/ColorManager/devices/xrandr_Chi_Mei_Optoelectronics_corp__fred_1000 ... Type: display Enabled: Yes Embedded: Yes Model: P170HMx Vendor: Clevo Serial: unknown Seat: seat0 Scope: temp Colorspace: rgb Device ID: xrandr-Chi Mei Optoelectronics corp. Profile 1: icc-9eb6fda60c1c8fcffd3111c8931dd354 /var/lib/colord/icc/P170HMx-nvidia-brightness4.2014-01-12_22-58-25.precise_matrix.icc Profile 2: icc-3e9bad7a0d3e98539aff767539cc891d /home/fred/.local/share/icc/edid-67b7d71da13bf89f5583ec6c33a36b1b.icc Metadata: OutputPriority=primary Metadata: XRANDR_name=LVDS-0 Metadata: OwnerCmdline=kded4 Metadata: OutputEdidMd5=67b7d71da13bf89f5583ec6c33a36b1b
When I start KDE, the correct profile is applied but 1second later, it is disabled. I see that because the background picture changes dramatically. Why?
Can you see anything in the journal at the time of starting KDE and subsequent disabling?
The log is attached. What follows may be relevant. It seems to me that the profile is correctly applied. I do not see anything removing it. However, I discovered that without the nvidia proprietary driver, there is no issue... I filed a bug at nvidia but I doubt anybody will answer... https://devtalk.nvidia.com/default/topic/762690/linux/after-a-few-seconds-th...
colord[842]: Profile added: icc-47e361dbcd0364df8d8878267f9d3810 colord[842]: Profile added: icc-3e9bad7a0d3e98539aff767539cc891d colord[842]: Automatic database add icc-3e9bad7a0d3e98539aff767539cc891d to xrandr-Chi Mei Optoelectronics corp. colord[842]: Automatic database add icc-9eb6fda60c1c8fcffd3111c8931dd354 to xrandr-Chi Mei Optoelectronics corp. colord[842]: Automatic metadata add icc-3e9bad7a0d3e98539aff767539cc891d to xrandr-Chi Mei Optoelectronics corp. colord[842]: Device added: xrandr-Chi Mei Optoelectronics corp.
Frédéric
On 22 July 2014 20:33, Frédéric Bron frederic.bron@m4x.org wrote:
The log is attached. What follows may be relevant. It seems to me that the profile is correctly applied. I do not see anything removing it. However, I discovered that without the nvidia proprietary driver, there is no issue...
Make sure there's no non-free process clearing the gamma ramps. The non-free driver just isn't very XRANDR 1.3 compliant, and I only test with the nouveau driver.
Richard.
Make sure there's no non-free process clearing the gamma ramps. The non-free driver just isn't very XRANDR 1.3 compliant, and I only test with the nouveau driver.
Yes, this is the issue. With nouveau, it works and with the nvidia proprietary driver, it does not. However, the nouveau driver is not suitable for my children who play minecraft. I posted a bug report on nvidia but I never see any answer there. Thanks, Frédéric
-
Chris Murphy -
Frédéric Bron -
Richard Hughes -
Tim