[bug-notifications] [dbus 0004821]: D-Bus library appears to be incorrectly set up
Mantis Bug Tracker
noreply at opencsw.org
Tue Sep 20 11:00:29 CEST 2011
A NOTE has been added to this issue.
======================================================================
https://www.opencsw.org/mantis/view.php?id=4821
======================================================================
Reported By: wcohrs
Assigned To: dam
======================================================================
Project: dbus
Issue ID: 4821
Category: other
Reproducibility: always
Severity: minor
Priority: normal
Status: assigned
======================================================================
Date Submitted: 2011-09-12 09:06 CEST
Last Modified: 2011-09-20 11:00 CEST
======================================================================
Summary: D-Bus library appears to be incorrectly set up
Description:
After upgrade my /opt/csw NFS-Server i have on the NFS clienst this error:
gimp
process 1330: D-Bus library appears to be incorrectly set up; failed to
read machine uuid: Failed to open "/etc/machine-id": No such file or
directory
See the manual page for dbus-uuidgen to correct this issue.
D-Bus not compiled with backtrace support so unable to print a
backtrace
Abort
after i create /etc/machine-id on the NFS client i have this message:
gimp
/opt/csw/bin/dbus-launch terminated abnormally with the following error:
EOF in dbus-launch reading address from bus daemon
Regards
Wolfgang
======================================================================
Relationships ID Summary
----------------------------------------------------------------------
related to 0004815 vim/gtk/dbus error
======================================================================
----------------------------------------------------------------------
(0009284) dam (administrator) - 2011-09-20 11:00
https://www.opencsw.org/mantis/view.php?id=4821#c9284
----------------------------------------------------------------------
The problem is that all the newer packages put their configuration files to
/etc/opt/csw. This has been done to aid sparse zones. If you are running it
on NFS shared /opt/csw you must make sure to synchronize the specific files
manually or issue the post-install from the packages on each host.
More information about the bug-notifications
mailing list