Ken Moffat wrote:
I've now finished building everything on my current system (using
what I call "sysv", i.e. LFS with systemd, but using sysvinit).
I figured I would need to test all the apps I actually use because
of the reports of problems with gcc-4.9. My first runtime failure
came from parole, which did nothing. Starting it in a term gave me:
parole-CRITICAL **: Failed to initialize Xfconf: Using X11 for
dbus-daemon autolaunch was disabled at compile time, set your
DBUS_SESSION_BUS_ADDRESS instead
Google was unhelpful, no recent results which seemed to be
related to my problem. I confirmed that dbus-launch had been
installed, and that the dbus initscript is running.
After using strace without getting any useful indications (every
library appeared to open ok), I tried searching for the "Using X11
for dbus-daemon autolaunch is disabled at compile time" message in
the output from 'strings'. Not in the parole binary, nor in the
xfce libaries I looked at.
Went back to google, kept getting old dbus results. So then I used
string on /usr/bin/dbus* : the message comes from dbus-daemon
itself. My reading is that we _do_ need to reinstall (at least)
dbus-daemon, as well as dbus-launch after installing xorg. I
suppose that systems using systemd might be different and liable to
break.
It seems to me that we ought to do a "regular" install of dbus.
Certainly, that appears to be the easiest apparent solution on a
non-systemd machine.
I'm currently looking into the power management issues of lxde for the
sysv and sysd environments. It seems that your problem is related. One
of the things I'm starting to look at is the dbus internals. To my
knowledge, the only thing that uses Xorg in dbus is dbus-launch, but
I'll check that again.
-- Bruce
--
http://lists.linuxfromscratch.org/listinfo/blfs-dev
FAQ: http://www.linuxfromscratch.org/blfs/faq.html
Unsubscribe: See the above information page
