After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 628738 - D-Bus misconfigured in jhbuild
D-Bus misconfigured in jhbuild
Status: RESOLVED FIXED
Product: jhbuild
Classification: Infrastructure
Component: general
unspecified
Other Linux
: Normal normal
: ---
Assigned To: Jhbuild maintainers
Jhbuild QA
Depends on:
Blocks:
 
 
Reported: 2010-09-03 21:34 UTC by Travis Reitter
Modified: 2010-11-01 11:13 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description Travis Reitter 2010-09-03 21:34:18 UTC
It seems like dbus (at least for jhbuild's setup) is misconfigured. If I launch a program that would start dbus services through activation, I get this error:

process 18908: D-Bus library appears to be incorrectly set up; failed to read machine uuid: Failed to open "/opt/gnome/var/lib/dbus/machine-id": No such file or directory
See the manual page for dbus-uuidgen to correct this issue.
  D-Bus not built with -rdynamic so unable to print a backtrace
Aborted

Symlinking fixes the symptom:

ln -s /var/lib/dbus/machine-id /opt/gnome/var/lib/dbus/machine-id

And my .bashrc has

export XDG_DATA_DIRS=/opt/gnome/share:/usr/share:$XDG_DATA_DIRS

so that shouldn't be a problem either.
Comment 1 Frederic Peters 2010-09-06 15:53:23 UTC
Right, var/lib/dbus/machine-id should be a link to the system file if you want to use the system dbus while building dbus in jhbuild. Also I believe var/run/dbus should also be a link.

Would you provide a patch to the documentation to note the issue?
Comment 2 Craig Keogh 2010-11-01 11:13:41 UTC
Thanks for reporting Travis and thanks for the details.

Done. http://git.gnome.org/browse/jhbuild/commit/?id=cc608d745fbd13713202d55cabbd64d1eb83c72f