Bug#860991: Bug#859093: colord-kde is missing in stretch
Christian Kanzian
christian.kanzian at gmx.at
Fri Apr 28 13:19:22 UTC 2017
Hi Maximiliano,
Am 2017-04-23 12:22, schrieb Maximiliano Curia:
> Control: retitle -1 "gnome-color-manager: double-free in the argllcms
> fallback code"
>
> ¡Hola Christian!
>
> I'm forwarding the gcm-calibrate part of your report to the
> gnome-color-manager maintainers, it seems that the issue is solved
> upstream with the patch:
> https://github.com/GNOME/gnome-color-manager/commit/edd8cf7598c009c8494396663401da80d12caf9d
>
> Still, I don't have the hardware to test this, maybe the
> gnome-color-manager maintainers can test this, otherwise, they may
> need you to test the patch.
Well, I do have a colorhug 1 which is free for adoption ;-). Just
contact me if it will fit your testing needs.
I will give my best to test a patch as well.
>
> I've set the severity to important, but it could equally be considered
> grave.
>
Thanks,
Christian
> El 2017-03-31 a las 22:29 +0200, Christian Kanzian escribió:
>>> colord-kde is currently in experimental, please consider testing it
>>> and provide some feedback about it in this bug. From the maintainers
>>> side, we don't have the hardware required to calibrate the devices,
>>> so we can only test it partially.
>
>> I use darktable to process my RAWs, which has a small colormanagement
>> test command:
>> -------------------------------------------------------- chri at chk64:~$
>> darktable-cmstest darktable-cmstest version 2.3.0+421~g1dd423c49-dirty
>> this executable was built with colord support enabled darktable itself
>> was built with colord support enabled ... DVI-0 the X atom and
>> colord returned different profiles X atom: _ICC_PROFILE (49272
>> bytes) description: EV2436W 2017-02-22 D6500 2.2 S
>> 3xCurve+MTX colord: "(none)" description: (file
>> not found)
>
>> Better check your system setup - some monitors reported different
>> profiles You may experience inconsistent color rendition between color
>> managed applications
>> --------------------------------------------------------
>
>
>> After installing colord-kde from experimental with $apt-get install -t
>> experimental colord-kde
>
>> I could install my screen-profile from the kde settings.
>
>> -------------------------------------------------------- chri at chk64:~$
>> darktable-cmstest darktable-cmstest version 2.3.0+421~g1dd423c49-dirty
>> this executable was built with colord support enabled darktable itself
>> was built with colord support enabled ... DVI-0 the X atom and
>> colord returned the same profile X atom: _ICC_PROFILE (49272
>> bytes) description: EV2436W 2017-02-22 D6500 2.2 S
>> 3xCurve+MTX colord: "/var/lib/colord/icc/EV2436W 2017-02-22
>> D6500 2.2 S 3xCurve +MTX.icc" description: EV2436W
>> 2017-02-22 D6500 2.2 S 3xCurve+MTX
>>
>> Your system seems to be correctly configured
>> --------------------------------------------------------
>
>> So colord has now the correct screen-profile settings. The profile
>> survives a restart, so I can't confirm
>> https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=858720
>
>> Next I plugged in my ColorHug2, the calibrate button got clickable and
>> I started the calibration process. However, at the end the process
>> ends without notice and no profile is generated. colord-kde seems to
>> call "gcm-calibrate" for the calibration process. I started
>> "gcm-calibrate" in a console and it crashed at the end with
>
>> *** Error in `gcm-calibrate': double free or corruption (fasttop):
>> 0x000055ab358056b0 ***
>
>> This look like this bug:
>> https://bugs.launchpad.net/ubuntu/+source/gnome-color-manager/+bug/1655536
>> which is not caused by colord-kde.
>
>
> Happy hacking,
More information about the pkg-gnome-maintainers
mailing list