GNU bug report logs -
#37911
'ColorManager' D-Bus service (colord) fails to start
Previous Next
To add a comment to this bug, you must first unarchive it, by sending
a message to control AT debbugs.gnu.org, with unarchive 37911 in the body.
You can then email your comments to 37911 AT debbugs.gnu.org in the normal way.
Toggle the display of automated, internal messages from the tracker.
Report forwarded
to
bug-guix <at> gnu.org
:
bug#37911
; Package
guix
.
(Thu, 24 Oct 2019 20:46:02 GMT)
Full text and
rfc822 format available.
Acknowledgement sent
to
Pierre Langlois <pierre.langlois <at> gmx.com>
:
New bug report received and forwarded. Copy sent to
bug-guix <at> gnu.org
.
(Thu, 24 Oct 2019 20:46:02 GMT)
Full text and
rfc822 format available.
Message #5 received at submit <at> debbugs.gnu.org (full text, mbox):
[Message part 1 (text/plain, inline)]
Hello Guix!
I tried to add (service colord-service) to my config and I got a
error back :-(. I reduced my system to the minimum but the problem is
persist.
Here's the backtrace I get with the colord-system.scm config attached:
```
$ guix system build colord-system.scm
(snip)
27692 entries processed in 10.3 s
successfully built /gnu/store/76v9hszcal0llfs7q8yapp6v0rnjwmkr-manual-database.drv
building /gnu/store/xs3khl253kzrf14cn2jz5hpabd69j88v-dbus-system-services.drv...
find-files: /gnu/store/nqr4xi6yyxzlyxmpvq668ckiksf0k96a-wpa-supplicant-2.9/share/dbus-1/: No such file or directory
find-files: /gnu/store/hpgsfyn3qn0lxp1p9nwcg6fbvslwpf59-gdm-3.30.3/share/dbus-1/: No such file or directory
Backtrace:
3 (primitive-load "/gnu/store/r5qblihnlj5ysy47k94a6s316mf?")
In ice-9/eval.scm:
619:8 2 (_ #f)
In srfi/srfi-1.scm:
640:9 1 (for-each #<procedure 7ffff3cb97e0 at ice-9/eval.scm:3?> ?)
In unknown file:
0 (symlink "/gnu/store/9641z2pcm85gx0xqi51i78m6k229nryr-?" ?)
ERROR: In procedure symlink:
In procedure symlink: File exists
builder for `/gnu/store/xs3khl253kzrf14cn2jz5hpabd69j88v-dbus-system-services.drv' failed with exit code 1
build of /gnu/store/xs3khl253kzrf14cn2jz5hpabd69j88v-dbus-system-services.drv failed
View build log at '/var/log/guix/drvs/xs/3khl253kzrf14cn2jz5hpabd69j88v-dbus-system-services.drv.bz2'.
cannot build derivation `/gnu/store/sla70asv0sf2c7gn4a5v50qkmy019703-dbus-configuration.drv': 1 dependencies couldn't be built
building /gnu/store/wq1naiygmpa01hn201l2i6ihd1bz44l1-etc-polkit-1.drv...
cannot build derivation `/gnu/store/vmnby0bcy575pylvbw5lva4k7zyrxrgd-etc.drv': 1 dependencies couldn't be built
building /gnu/store/4zr21fl9wsyy591rglgw47yzw9nnia2g-gdm-custom.conf.drv...
cannot build derivation `/gnu/store/yc1mdlzqqwd24x7gkxa9n6qfmjzx83zg-system.drv': 1 dependencies couldn't be built
guix system: error: build of `/gnu/store/yc1mdlzqqwd24x7gkxa9n6qfmjzx83zg-system.drv' failed
```
Do you know what's going on?
Thanks!
Pierre
[colord-system.scm (application/octet-stream, attachment)]
Information forwarded
to
bug-guix <at> gnu.org
:
bug#37911
; Package
guix
.
(Thu, 24 Oct 2019 20:51:02 GMT)
Full text and
rfc822 format available.
Message #8 received at 37911 <at> debbugs.gnu.org (full text, mbox):
[Message part 1 (text/plain, inline)]
Pierre Langlois writes:
> Hello Guix!
>
> I tried to add (service colord-service) to my config and I got a
> error back :-(. I reduced my system to the minimum but the problem is
> persist.
>
> Here's the backtrace I get with the colord-system.scm config attached:
And now attached with the correct mime type... sorry! :-)
[colord-system.scm (text/plain, attachment)]
Information forwarded
to
bug-guix <at> gnu.org
:
bug#37911
; Package
guix
.
(Thu, 24 Oct 2019 20:53:01 GMT)
Full text and
rfc822 format available.
Message #11 received at 37911 <at> debbugs.gnu.org (full text, mbox):
[Message part 1 (text/plain, inline)]
Pierre,
Pierre Langlois 写道:
> Hello Guix!
>
> I tried to add (service colord-service) to my config and I got a
> error back :-(. I reduced my system to the minimum but the
> problem is
> persist.
Probably related to my recent colord update to fix simple-scan.
I'll take a look.
Thanks!
T G-R
[signature.asc (application/pgp-signature, inline)]
Information forwarded
to
bug-guix <at> gnu.org
:
bug#37911
; Package
guix
.
(Thu, 24 Oct 2019 21:00:02 GMT)
Full text and
rfc822 format available.
Message #14 received at 37911 <at> debbugs.gnu.org (full text, mbox):
Pierre Langlois writes:
> (use-modules
> (gnu bootloader grub)
> (gnu bootloader)
> (gnu services desktop)
> (gnu system file-systems))
>
> (operating-system
> (host-name "hello")
> (bootloader (bootloader-configuration
> (bootloader grub-efi-bootloader)
> (target "/boot/efi")))
> (file-systems (cons*
> (file-system
> (device (file-system-label "guix"))
> (mount-point "/")
> (type "ext4"))
> (file-system
> (device "/dev/nvme0n1p1")
> (mount-point "/boot/efi")
> (type "vfat"))
> (file-system
> (device (file-system-label "data"))
> (mount-point "/home")
> (type "ext4"))
> %fuse-control-file-system
> %base-file-systems))
> (timezone "Europe/London")
> (locale "en_GB.UTF-8")
> (users (cons* (user-account
> (name "pierre")
> (uid 1000)
> (group "users"))
> %base-user-accounts))
> (services (cons*
> (colord-service)
> %desktop-services)))
Oh, I just realized (colord-service) is in %desktop-services
already... ooops my bad!
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).
Sorry for the noise!
Pierre
Information forwarded
to
bug-guix <at> gnu.org
:
bug#37911
; Package
guix
.
(Thu, 24 Oct 2019 21:20:02 GMT)
Full text and
rfc822 format available.
Message #17 received at 37911 <at> debbugs.gnu.org (full text, mbox):
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?
Hope that helps,
Jack
Information forwarded
to
bug-guix <at> gnu.org
:
bug#37911
; Package
guix
.
(Fri, 25 Oct 2019 21:06:01 GMT)
Full text and
rfc822 format available.
Message #20 received at 37911 <at> debbugs.gnu.org (full text, mbox):
Hello,
Jack Hill <jackhill <at> jackhill.us> 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,
“Color” tag, I see:
--8<---------------cut here---------------start------------->8---
459 sendmsg(48, {msg_name=NULL, msg_namelen=0, msg_iov=[{iov_base="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=128}, {iov_base="\206\0\0\0Connection \":1.95\" is not allowed to own the service \"org.freedesktop.ColorManager\" due to security policies in the configuration file\0", iov_len=139}], msg_iovlen=2, msg_controllen=0, msg_flags=0}, MSG_NOSIGNAL <unfinished ...>
--8<---------------cut here---------------end--------------->8---
So something somewhere is unhappy.
I diff’d the ‘org.freedesktop.color.policy’ files of colord 1.4.3 and
1.4.4 and there are no functional differences.
Ludo’.
Severity set to 'important' from 'normal'
Request was from
Ludovic Courtès <ludo <at> gnu.org>
to
control <at> debbugs.gnu.org
.
(Mon, 28 Oct 2019 22:19:01 GMT)
Full text and
rfc822 format available.
Merged 37843 37911.
Request was from
Ludovic Courtès <ludo <at> gnu.org>
to
control <at> debbugs.gnu.org
.
(Fri, 01 Nov 2019 22:31:04 GMT)
Full text and
rfc822 format available.
Merged 37843 37911.
Request was from
Ludovic Courtès <ludo <at> gnu.org>
to
control <at> debbugs.gnu.org
.
(Fri, 01 Nov 2019 23:14:02 GMT)
Full text and
rfc822 format available.
Changed bug title to ''ColorManager' D-Bus service (colord) fails to start' from 'Cannot build a system with colord-service.'
Request was from
Ludovic Courtès <ludo <at> gnu.org>
to
control <at> debbugs.gnu.org
.
(Fri, 01 Nov 2019 23:15:03 GMT)
Full text and
rfc822 format available.
Information forwarded
to
bug-guix <at> gnu.org
:
bug#37911
; Package
guix
.
(Fri, 01 Nov 2019 23:18:02 GMT)
Full text and
rfc822 format available.
Message #31 received at 37911 <at> debbugs.gnu.org (full text, mbox):
Hi Jack and all,
Ludovic Courtès <ludo <at> gnu.org> skribis:
> Jack Hill <jackhill <at> jackhill.us> 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,
> “Color” tag, I see:
>
> 459 sendmsg(48, {msg_name=NULL, msg_namelen=0, msg_iov=[{iov_base="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=128}, {iov_base="\206\0\0\0Connection \":1.95\" is not allowed to own the service \"org.freedesktop.ColorManager\" due to security policies in the configuration file\0", iov_len=139}], msg_iovlen=2, msg_controllen=0, msg_flags=0}, MSG_NOSIGNAL <unfinished ...>
>
> So something somewhere is unhappy.
Commit 33f9778bc83086837b99e5c5e99cd514cb0d154e fixes this and colord
now starts correctly again.
I believe that should also fix the “night light” 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’.
Reply sent
to
Pierre Langlois <pierre.langlois <at> gmx.com>
:
You have taken responsibility.
(Sat, 02 Nov 2019 14:13:02 GMT)
Full text and
rfc822 format available.
Notification sent
to
Pierre Langlois <pierre.langlois <at> gmx.com>
:
bug acknowledged by developer.
(Sat, 02 Nov 2019 14:13:02 GMT)
Full text and
rfc822 format available.
Message #36 received at 37911-done <at> debbugs.gnu.org (full text, mbox):
Hi Ludo,
Ludovic Courtès writes:
> Hi Jack and all,
>
> Ludovic Courtès <ludo <at> gnu.org> skribis:
>
>> Jack Hill <jackhill <at> jackhill.us> 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,
>> “Color” tag, I see:
>>
>> 459 sendmsg(48, {msg_name=NULL, msg_namelen=0, msg_iov=[{iov_base="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=128}, {iov_base="\206\0\0\0Connection \":1.95\" is not allowed to own the service \"org.freedesktop.ColorManager\" due to security policies in the configuration file\0", iov_len=139}], msg_iovlen=2, msg_controllen=0, msg_flags=0}, MSG_NOSIGNAL <unfinished ...>
>>
>> So something somewhere is unhappy.
>
> Commit 33f9778bc83086837b99e5c5e99cd514cb0d154e fixes this and colord
> now starts correctly again.
>
> I believe that should also fix the “night light” feature in GNOME. I
> tested it in a VM but it was hard to tell if it was working.
I can confirm it's working for me on GNOME on my thinkpad! I can use the
night light settings and the laptop screen was detected in the "Color"
section of the settings. And I can see the colord daemon is running.
This is awesome, thank you!
Marking 37911 as done, I'll let Jack close 37843 if he's happy with it.
Pierre
Reply sent
to
Pierre Langlois <pierre.langlois <at> gmx.com>
:
You have taken responsibility.
(Sat, 02 Nov 2019 14:13:03 GMT)
Full text and
rfc822 format available.
Notification sent
to
Jack Hill <jackhill <at> jackhill.us>
:
bug acknowledged by developer.
(Sat, 02 Nov 2019 14:13:03 GMT)
Full text and
rfc822 format available.
Information forwarded
to
bug-guix <at> gnu.org
:
bug#37911
; Package
guix
.
(Sat, 02 Nov 2019 14:15:02 GMT)
Full text and
rfc822 format available.
Message #44 received at 37911 <at> debbugs.gnu.org (full text, mbox):
[Message part 1 (text/plain, inline)]
On Sat, 2 Nov 2019, Ludovic Courtès wrote:
> Commit 33f9778bc83086837b99e5c5e99cd514cb0d154e fixes this and colord
> now starts correctly again.
>
> I believe that should also fix the “night light” feature in GNOME. I
> tested it in a VM but it was hard to tell if it was working.
>
> Could you confirm, Jack?
Yes, I can confirm that it works now.
Many thanks,
Jack
Information forwarded
to
bug-guix <at> gnu.org
:
bug#37911
; Package
guix
.
(Mon, 04 Nov 2019 17:21:02 GMT)
Full text and
rfc822 format available.
Message #47 received at 37911-done <at> debbugs.gnu.org (full text, mbox):
Hello,
Pierre Langlois <pierre.langlois <at> gmx.com> skribis:
> I can confirm it's working for me on GNOME on my thinkpad! I can use the
> night light settings and the laptop screen was detected in the "Color"
> section of the settings. And I can see the colord daemon is running.
Jack Hill <jackhill <at> jackhill.us> skribis:
> Yes, I can confirm that it works now.
Awesome, closing!
Thank you,
Ludo’.
bug archived.
Request was from
Debbugs Internal Request <help-debbugs <at> gnu.org>
to
internal_control <at> debbugs.gnu.org
.
(Tue, 03 Dec 2019 12:24:04 GMT)
Full text and
rfc822 format available.
This bug report was last modified 4 years and 117 days ago.
Previous Next
GNU bug tracking system
Copyright (C) 1999 Darren O. Benham,
1997,2003 nCipher Corporation Ltd,
1994-97 Ian Jackson.