Cliff McDiarmid wrote:
> No probs, its running.
>
?? strange.
> Anyway, do people think dbus is the problem?
>
I still think that that error message is indicating the problem.
When the user space message bus starts up, it should set
DBUS_SESSION_BUS_ADDRESS. To see this, you are going to need to echo it
to a file since you don't have a console running.
I have this:
## test for an existing bus daemon, just to be safe
if test -z "$DBUS_SESSION_BUS_ADDRESS" ; then
## if not found, launch a new one
eval `dbus-launch --sh-syntax --exit-with-session`
echo "D-BUS per-session daemon address is: $DBUS_SESSION_BUS_ADDRESS"
fi
which I copied from the documentation. But, it doesn't help if you
don't have a console for it to be echoed to. So, direct the echo to a
file. Remember to make sure that the file can be written to. What I do
is create a file in /root/ and change the permissions to 666.
--
JRT
--
http://linuxfromscratch.org/mailman/listinfo/blfs-support
FAQ: http://www.linuxfromscratch.org/blfs/faq.html
Unsubscribe: See the above information page
