[colord] [ *SOLVED* ] RE: trouble getting colord to work

[Florin Gherendi]

Hi again!

 

No answer so far, but I've eventually solved the problem by myself. I am
posting the solution here cause it was a tricky one.

First: the "Could not connect" message was coming from glib (ugly that it
doesn't say that). Glib does not explicitly require dbus, but it uses some
dbus dirs. Therefore I had to patch glib so that it finds the dbus dirs in
/opt and not in the root filesystem.

Second: dbus had a problem:  "make install"  wasn't performing "ldconfig"
automatically. That makes dbus-daemon-launch-helper unable to load
/opt/usr/lib/libdbus-1.so.3 when running as messagebus user from the libexec
dir. This is why dbus-daemon wasn't launching any service.

I hope this would be useful for someone!

 

Have a nice time! J

Florin

 

 

From: Florin Gherendi [mailto:florin_gf at yahoo.fr] 
Sent: Wednesday, June 01, 2016 11:54 PM
To: colord at lists.freedesktop.org
Subject: trouble getting colord to work

 

Hi everybody!

I am new to this list. I am trying to make a port of colord on a DD-WRT WiFi
router with ARM processor, because it would be useful for CUPS. I've
"hacked" a lot of things to work on that router, even a native gcc and a
quite well working LinuxFromScratch base system, I even have GTK+3 working
(remotely with Mesa and all). Also, DBus responds well to tests. 

My setup is a little bit nonstandard, since everything is installed in the
/opt directory, because the root file system is read only, however I've got
everything working well, with source modifications for some of the packages
(to replace /etc with /opt/etc and so on). 

 

Now my problem: I cannot get colord DBus service to start. "colormgr
get-devices" gives me "No connection to colord: Could not connect: No such
file or directory" ; something similar for "colord-session-example". Well,
the error message gives barely any information, and I have no means to know
what is the file or directory it cannot find, and it looks pretty difficult
to debug with gdb. Can anyone give me a clue where to start diagnostics?

I could suspect a DBus config that prevents it to launch colord, but I am
not sure. 

My Valgrind version (3.10) is a bit old and it would take some time to
compile 3.11 in order to run the tests for colord-1.3.2 with "make check",
but the individual tests ran without Valgrind  from command line give me all
"Passed".

 

dbus-send --system            \

  --dest=org.freedesktop.DBus \

  --type=method_call          \

  --print-reply               \

  /org/freedesktop/DBus       \

  org.freedesktop.DBus.ListNames

 

will give

 

method return time=1464813810.680715 sender=org.freedesktop.DBus ->
destination=:1.2 serial=3 reply_serial=2

   array [

      string "org.freedesktop.DBus"

      string ":1.2"

   ] 

 

So the colord service is not listed, even if
org.freedesktop.ColorManager.service is present in
/opt/usr/share/dbus-1/system-services and points to the right location of
colord. Of course, dbus is configured to search for everything in /opt, not
in root filesystem; I've even modifed the DBus sources and replaced all
/etc, /usr and /var with the /opt prefixed versions. 

What am I missing?

Thanks for any clue!

Florin

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.freedesktop.org/archives/colord/attachments/20160606/16f66867/attachment.html>