From mboxrd@z Thu Jan 1 00:00:00 1970 From: Ludovic =?UTF-8?Q?Court=C3=A8s?= Subject: bug#37911: Cannot build a system with colord-service. Date: Fri, 25 Oct 2019 23:05:39 +0200 Message-ID: <87eez0mt7g.fsf@gnu.org> References: <87imodyisc.fsf@gmx.com> <87h83xyijg.fsf@gmx.com> <87ftjhyi4l.fsf@gmx.com> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Return-path: Received: from eggs.gnu.org ([2001:470:142:3::10]:38962) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1iO6mf-0007TB-Ua for bug-guix@gnu.org; Fri, 25 Oct 2019 17:06:11 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1iO6me-0007W0-By for bug-guix@gnu.org; Fri, 25 Oct 2019 17:06:09 -0400 Received: from debbugs.gnu.org ([209.51.188.43]:58877) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16) (Exim 4.71) (envelope-from ) id 1iO6mX-0007UL-TY for bug-guix@gnu.org; Fri, 25 Oct 2019 17:06:02 -0400 Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.84_2) (envelope-from ) id 1iO6mX-0002Ra-Lt for bug-guix@gnu.org; Fri, 25 Oct 2019 17:06:01 -0400 Sender: "Debbugs-submit" Resent-Message-ID: In-Reply-To: (Jack Hill's message of "Thu, 24 Oct 2019 17:19:52 -0400 (EDT)") List-Id: Bug reports for GNU Guix List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: bug-guix-bounces+gcggb-bug-guix=m.gmane.org@gnu.org Sender: "bug-Guix" To: Jack Hill Cc: 37911@debbugs.gnu.org Hello, Jack Hill skribis: > On Thu, 24 Oct 2019, Pierre Langlois wrote: > >> In gnome's settings it tells me that there are no devices that can be >> colour managed, I had assumed that was because colord was missing from >> the config but that's probably not it. Is it working for other people? >> If so it's probably just my hardware (ThinkPad x220). > > I think it is not able to manage devices because the Argyll CMS > dependency [0] is missing in Guix. Unfortunately, it seems to also > depend on the discontinued Jam build tool [1], so there is a little > bit of work to be done. > > [0] https://argyllcms.com/ > [1] https://www.perforce.com/documentation/jam-documentation > > I did spot another issue with colord since the recent core-updates > merge: https://issues.guix.gnu.org/issue/37843 It seems like it is no > longer being started automatically via dbus? Indeed, stracing dbus-daemon while going to the GNOME settings panel, =E2=80=9CColor=E2=80=9D tag, I see: --8<---------------cut here---------------start------------->8--- 459 sendmsg(48, {msg_name=3DNULL, msg_namelen=3D0, msg_iov=3D[{iov_base= =3D"l\3\1\1\213\0\0\0\3\0\0\0m\0\0\0\6\1s\0\5\0\0\0:1.95\0\0\0\4\1s\0'\0\0\= 0org.freedesktop.DBus.Error.AccessDenied\0\5\1u\0\2\0\0\0\10\1g\0\1s\0\0\7\= 1s\0\24\0\0\0org.freedesktop.DBus\0\0\0\0", iov_len=3D128}, {iov_base=3D"\2= 06\0\0\0Connection \":1.95\" is not allowed to own the service \"org.freede= sktop.ColorManager\" due to security policies in the configuration file\0",= iov_len=3D139}], msg_iovlen=3D2, msg_controllen=3D0, msg_flags=3D0}, MSG_N= OSIGNAL --8<---------------cut here---------------end--------------->8--- So something somewhere is unhappy. I diff=E2=80=99d the =E2=80=98org.freedesktop.color.policy=E2=80=99 files o= f colord 1.4.3 and 1.4.4 and there are no functional differences. Ludo=E2=80=99.