From mboxrd@z Thu Jan 1 00:00:00 1970 From: Ludovic =?UTF-8?Q?Court=C3=A8s?= Subject: bug#37843: bug#37911: Cannot build a system with colord-service. Date: Sat, 02 Nov 2019 00:17:06 +0100 Message-ID: <87mudf9ogd.fsf@gnu.org> References: <87imodyisc.fsf@gmx.com> <87h83xyijg.fsf@gmx.com> <87ftjhyi4l.fsf@gmx.com> <87eez0mt7g.fsf@gnu.org> 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]:44029) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1iQgB9-0001zx-L0 for bug-guix@gnu.org; Fri, 01 Nov 2019 19:18:04 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1iQgB8-0008VY-FY for bug-guix@gnu.org; Fri, 01 Nov 2019 19:18:03 -0400 Received: from debbugs.gnu.org ([209.51.188.43]:48699) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16) (Exim 4.71) (envelope-from ) id 1iQgB7-0008TT-V6 for bug-guix@gnu.org; Fri, 01 Nov 2019 19:18:02 -0400 Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.84_2) (envelope-from ) id 1iQgB7-0008G3-Mw for bug-guix@gnu.org; Fri, 01 Nov 2019 19:18:01 -0400 Sender: "Debbugs-submit" Resent-Message-ID: In-Reply-To: <87eez0mt7g.fsf@gnu.org> ("Ludovic \=\?utf-8\?Q\?Court\=C3\=A8s\=22'\?\= \=\?utf-8\?Q\?s\?\= message of "Fri, 25 Oct 2019 23:05:39 +0200") 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: 37843@debbugs.gnu.org, 37911@debbugs.gnu.org Hi Jack and all, Ludovic Court=C3=A8s skribis: > Jack Hill skribis: [...] >> 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: > > 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 > > So something somewhere is unhappy. Commit 33f9778bc83086837b99e5c5e99cd514cb0d154e fixes this and colord now starts correctly again. I believe that should also fix the =E2=80=9Cnight light=E2=80=9D feature in= GNOME. I tested it in a VM but it was hard to tell if it was working. Could you confirm, Jack? Thanks, Ludo=E2=80=99.