Bug 215816

Summary: graphics/colord breaks dispwin (argyllcms) profile installation
Product: Ports & Packages Reporter: Anindya Mukherjee <anindya49>
Component: Individual Port(s)Assignee: Koop Mast <kwm>
Status: New ---    
Severity: Affects Some People CC: bsam, w.schwarzenfeld
Priority: --- Flags: bugzilla: maintainer-feedback? (kwm)
Version: Latest   
Hardware: Any   
OS: Any   

Description Anindya Mukherjee 2017-01-06 04:17:14 UTC
I've been using a fully colour-managed desktop with x11-wm/windowmaker, xiccd (compiled from source) and graphics/colord. My setup is based on this guide: Thread 51153.

In the last update to graphics/colord, the build was changed to support libcolordcompat. See: http://www.freshports.org/graphics/colord. Unfortunately, this breaks installation of profiles (setting the X Atom) using dispwin from graphics/argyllcms. I believe this is due to a bug in libcolordcompat. The error is exactly the same as the one in this bug report for colord: https://bugs.freedesktop.org/show_bug.cgi?id=98870.

Note that the bug report is for colord 1.3.4, and claims it works for 1.3.3. However, I think that 1.2.12, which is the port version, is also broken in the same way.

I was able to make it work again by manually editing the Makefile and pkg-plist for the port to not use libcolordcompat. This further confirms my suspicion above.

I posted this in case someone else has this problem, and also to suggest that libcolordcompat be made a port option, instead of hard-coding it in. I understand that we cannot do anything about the actual bug till it's fixed upstream, but making libcolordcompat optional will make it easier to work around it.

System details:
uname -a
FreeBSD giskard 11.0-RELEASE-p2 FreeBSD 11.0-RELEASE-p2 #0: Mon Oct 24 06:55:27 UTC 2016     root@amd64-builder.daemonology.net:/usr/obj/usr/src/sys/GENERIC  \


colord version: colord-1.2.12
Comment 1 Walter Schwarzenfeld freebsd_triage 2018-01-14 03:40:49 UTC
Maintainer feedback?
Comment 2 Walter Schwarzenfeld freebsd_triage 2019-08-08 10:02:57 UTC
argyllcms needs updated:
I can confirm it is working with the updated version of argyllcms (2.0.0-1), which is now in the community repo.

Additional the question, if this is still relevant?
Comment 3 Anindya Mukherjee 2019-09-12 22:54:06 UTC
Thank you for testing. When can we expect an update for argyllcms in ports?
Comment 4 Walter Schwarzenfeld freebsd_triage 2019-09-13 18:37:35 UTC
Tried update of argyllcms bug #240568. Please, test it.