Summary: | x11-misc/colord-0.1.34 - In function ‘cd_sensor_open_usb_device’: ../cd-sensor.c:1186:52: error: ‘CdSensorPrivate’ has no member named ‘device’ | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Cengiz Gunay <cengique> |
Component: | [OLD] GNOME | Assignee: | Gentoo Linux Gnome Desktop Team <gnome> |
Status: | RESOLVED FIXED | ||
Severity: | normal | ||
Priority: | Normal | ||
Version: | unspecified | ||
Hardware: | AMD64 | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- | |
Attachments: |
emerge --info '=x11-misc/colord-0.1.34::gentoo'
build log updated build.log for 1.0.3 |
Description
Cengiz Gunay
2013-08-23 23:34:00 UTC
Created attachment 356806 [details]
emerge --info '=x11-misc/colord-0.1.34::gentoo'
Created attachment 356810 [details]
build log
As a temporary solution, I was able to remove colord from my system by removing the colord use flag from these packages:
>=gnome-base/gnome-control-center-3.8.4.1-r1 -colord
>=gnome-base/gnome-settings-daemon-3.8.4 -colord
x11-libs/gtk+ -colord
Then, re-emerging them:
emerge -1vN gnome-base/gnome-settings-daemon gnome-base/gnome-control-center x11-libs/gtk+
And then removing colord:
emerge -v --depclean x11-misc/colord gnome-extra/gnome-color-manager
That should be safe and stop if there are more dependencies.
Still happens after I completed my system update to ~amd64. You are saying that this is still a problem with colord-1.0.3 ? Could you please post an updated build.log ? Created attachment 358306 [details]
updated build.log for 1.0.3
The problem is, you were emerging colord with USE="gusb -udev". Looking at colord's source, it's clear that gusb requires udev, but we were missing that requirement from the ebuild. + 08 Sep 2013; Alexandre Rostovtsev <tetromino@gentoo.org> + colord-0.1.28.ebuild, colord-0.1.31.ebuild, colord-0.1.34.ebuild, + colord-1.0.3.ebuild: + USE=gusb requires USE=udev (bug #482276, thanks to Cengiz Gunay). That was it! It works for me, too. Thanks. |