Skip site navigation (1)Skip section navigation (2)
Date:      Fri, 06 Jan 2017 04:17:14 +0000
From:      bugzilla-noreply@freebsd.org
To:        freebsd-ports-bugs@FreeBSD.org
Subject:   [Bug 215816] graphics/colord breaks dispwin (argyllcms) profile installation
Message-ID:  <bug-215816-13@https.bugs.freebsd.org/bugzilla/>

next in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D215816

            Bug ID: 215816
           Summary: graphics/colord breaks dispwin (argyllcms) profile
                    installation
           Product: Ports & Packages
           Version: Latest
          Hardware: Any
                OS: Any
            Status: New
          Severity: Affects Some People
          Priority: ---
         Component: Individual Port(s)
          Assignee: kwm@FreeBSD.org
          Reporter: anindya49@hotmail.com
          Assignee: kwm@FreeBSD.org
             Flags: maintainer-feedback?(kwm@FreeBSD.org)

I've been using a fully colour-managed desktop with x11-wm/windowmaker, xic=
cd
(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. Unfortunat=
ely,
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=3D98870.

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-p=
list
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 th=
at
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:5=
5:27
UTC 2016     root@amd64-builder.daemonology.net:/usr/obj/usr/src/sys/GENERI=
C  \
amd64

freebsd-version
11.0-RELEASE-p6

colord version: colord-1.2.12

--=20
You are receiving this mail because:
You are the assignee for the bug.=



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-215816-13>