2009/9/16 Cliff McDiarmid <[email protected]>: > Thanks for the advice James, but the problem still persists. Haven't had any > time to mess with it in the last week(I use 2nd LFS on another partition), > but I think It's a dbus problem, although would welcome advice to the > contrary. I can get an xterm with clock etc, but when I startx (have > .Xinitrc in users account with the above in it) I'm thrown back to command > prompt. End of log reads: > > startkde: Starting up... > Failed to start message bus: Element <servicedir> is not allowed in this > contextEOF in dbus-launch reading address from bus daemon > startkde: Could not start D-Bus. Can you call qdbus? > > If I call qdbus get: > > Could not connect to D-Bus server: > org.freedesktop.DBus.Error.Spawn.ExecFailed: > /usr/bin/dbus-launch terminated abnormally with the following error: > Autolaunch > error: X11 initialization failed > > I assume this is the problem - anybody? > Sundry not-adequately-resolved posts in google. One was in czech, and translate.google left a lot of the words untranslated :-(
Have you tried upgrading dbus to the version in the development book (1.2.16) ? If you use hal, do you have a current version ? To me, this feels as if it might be like the dbus/hal problems some people apparently saw following the attempts to fix the dbus vulnerability. ĸen -- After tragedy, and farce, "OMG poneys!" -- http://linuxfromscratch.org/mailman/listinfo/blfs-support FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
