'ColorManager' D-Bus service (colord) fails to start

  • Done
  • quality assurance status badge
Details
4 participants
  • Jack Hill
  • Ludovic Courtès
  • Tobias Geerinckx-Rice
  • Pierre Langlois
Owner
unassigned
Submitted by
Pierre Langlois
Severity
important
Merged with
P
P
Pierre Langlois wrote on 24 Oct 2019 22:45
Cannot build a system with colord-service.
(address . bug-guix@gnu.org)
87imodyisc.fsf@gmx.com
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
Attachment: colord-system.scm
P
P
Pierre Langlois wrote on 24 Oct 2019 22:50
(address . 37911@debbugs.gnu.org)(name . Pierre Langlois)(address . pierre.langlois@gmx.com)
87h83xyijg.fsf@gmx.com
Pierre Langlois writes:

Toggle quote (8 lines)
> 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! :-)
(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)))
T
T
Tobias Geerinckx-Rice wrote on 24 Oct 2019 22:51
(address . 37911@debbugs.gnu.org)
87r231g93l.fsf@nckx
Pierre,

Pierre Langlois ???
Toggle quote (7 lines)
> 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
-----BEGIN PGP SIGNATURE-----

iQIzBAEBCgAdFiEEfo+u0AlEeO9y5k0W2Imw8BjFSTwFAl2yDu4ACgkQ2Imw8BjF
STxfYw/+JSLFeOYaPK1j7l5yG7HrisFF8LZpJreQPUh2jwhPZU/fJsoaUZxUhohw
xVWbdF2qNdVjOf2kYwxkW7tmod/5K6j11U71iKvW/YRQZlsJT7H1UeIrXlkCrVmO
lQfTqTdZDXEHTVri3vreUjOqT6ibUTZeKtP97hQd/qyvZkXLRm3yDIkWU8+0oorC
Fs36ceoTko7qTvJicqsVCfPrp5vAiLlRALIjKG/k6QpXiyA3sWKyUyMkc212WqDH
ke3muDTFPnbGI8ccxz6muUUSAMvqqWpaPYZ1WSsAr3k3yhzABGu9OdcsxtxPM9YA
cl/aCclkcg4SXwBPDoPfZetnVoCpzxR5pZiE0ZmeZDa+LGogy4ng7QVN138Cj2aS
IIdWOjl4jlzDe9YztDYmnNUdwE5GLdKUpJN+A8j2LDxRR7luTS++ILHL+1Y7JitN
6CZQBErLAyqAAy5Qn32GKnDiQ4ldyCyhqDRPv8nzto6Gk4zM8UPuZ9FxFy+i9nGK
XB92RiHcv6k1KwquaiFhmSTQaj0N+gnPLNqP5n2OzTBGGuj0iHeCtols+zW/rgsE
J9u5GBqV23in9YzZkXYYE34R911yqmoHLIZt1UjegFRBLnkaS6jxRw/dL70y6ws5
PlipWVXW/RiF17E2FWNWnVxNHvx36SbcTutSM1wElXlfvhqPYhg=
=U4lU
-----END PGP SIGNATURE-----

P
P
Pierre Langlois wrote on 24 Oct 2019 22:59
(address . 37911@debbugs.gnu.org)(name . Pierre Langlois)(address . pierre.langlois@gmx.com)
87ftjhyi4l.fsf@gmx.com
Pierre Langlois writes:

Toggle quote (37 lines)
> (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
J
J
Jack Hill wrote on 24 Oct 2019 23:19
(name . Pierre Langlois)(address . pierre.langlois@gmx.com)(address . 37911@debbugs.gnu.org)
alpine.DEB.2.20.1910241713580.11560@marsh.hcoop.net
On Thu, 24 Oct 2019, Pierre Langlois wrote:

Toggle quote (5 lines)
> 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.


I did spot another issue with colord since the recent core-updates merge:
https://issues.guix.gnu.org/issue/37843It seems like it is no longer
being started automatically via dbus?

Hope that helps,
Jack
L
L
Ludovic Courtès wrote on 25 Oct 2019 23:05
(name . Jack Hill)(address . jackhill@jackhill.us)
87eez0mt7g.fsf@gnu.org
Hello,

Jack Hill <jackhill@jackhill.us> skribis:

Toggle quote (19 lines)
> 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:

Toggle snippet (3 lines)
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.

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’.
L
L
Ludovic Courtès wrote on 28 Oct 2019 23:17
control message for bug #37911
(address . control@debbugs.gnu.org)
87o8y0frag.fsf@gnu.org
severity 37911 important
quit
L
L
Ludovic Courtès wrote on 1 Nov 2019 23:30
control message for bug #37843
(address . control@debbugs.gnu.org)
87y2wz9qlx.fsf@gnu.org
merge 37843 37911
quit
L
L
Ludovic Courtès wrote on 2 Nov 2019 00:13
(address . control@debbugs.gnu.org)
87v9s39omj.fsf@gnu.org
merge 37843 37911
quit
L
L
Ludovic Courtès wrote on 2 Nov 2019 00:14
(address . control@debbugs.gnu.org)
87tv7n9oli.fsf@gnu.org
retitle 37843 'ColorManager' D-Bus service (colord) fails to start
quit
L
L
Ludovic Courtès wrote on 2 Nov 2019 00:17
Re: bug#37911: Cannot build a system with colord-service.
(name . Jack Hill)(address . jackhill@jackhill.us)
87mudf9ogd.fsf@gnu.org
Hi Jack and all,

Ludovic Courtès <ludo@gnu.org> skribis:

Toggle quote (2 lines)
> Jack Hill <jackhill@jackhill.us> skribis:

[...]

Toggle quote (11 lines)
>> 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’.
P
P
Pierre Langlois wrote on 2 Nov 2019 15:11
(name . Ludovic Courtès)(address . ludo@gnu.org)
87r22q74gt.fsf@gmx.com
Hi Ludo,

Ludovic Courtès writes:

Toggle quote (25 lines)
> Hi Jack and all,
>
> Ludovic Courtès <ludo@gnu.org> skribis:
>
>> Jack Hill <jackhill@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
Closed
J
J
Jack Hill wrote on 2 Nov 2019 15:14
(name . Ludovic Courtès)(address . ludo@gnu.org)
alpine.DEB.2.20.1911021013590.11560@marsh.hcoop.net
On Sat, 2 Nov 2019, Ludovic Courtès wrote:

Toggle quote (8 lines)
> 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
L
L
Ludovic Courtès wrote on 4 Nov 2019 18:20
(name . Pierre Langlois)(address . pierre.langlois@gmx.com)
878sov8snr.fsf@gnu.org
Hello,

Pierre Langlois <pierre.langlois@gmx.com> skribis:

Toggle quote (4 lines)
> 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@jackhill.us> skribis:

Toggle quote (2 lines)
> Yes, I can confirm that it works now.

Awesome, closing!

Thank you,
Ludo’.
Closed
?
Your comment

This issue is archived.

To comment on this conversation send an email to 37911@debbugs.gnu.org

To respond to this issue using the mumi CLI, first switch to it
mumi current 37911
Then, you may apply the latest patchset in this issue (with sign off)
mumi am -- -s
Or, compose a reply to this issue
mumi compose
Or, send patches to this issue
mumi send-email *.patch