Magnus Larsson wrote:

  I had a somewhat similar problem on a sysvinit build a week or more
ago - posted on blfs-dev, so it should be in the archives.  My
problem was that parole refused to start with the "X11" message.
Using 'strings' I discovered that message came from dbus-daemon (I
think).  I reinstalled all of dbus and the problem went away, and
the message was no longer in that executable.

  Note that I do not run any desktop environment.

  I also built a throwaway systemd system using the book as it was.
Again, parole had this problem.  I did not attempt to rebuild dbus
in _that_ system, systemd had already been removed from lfs.  So, I
do not consider that my workaround - (re)build dbus after glib and
thus after X - is necessarily correct for systemd users, nor for
users of full desktop environments, but it matches what BLFS-svn is
(again) doing.

  I must admit that I would not have thought of trying
export $(dbus-launch)
and since my problem was as a normal user I'm not sure if it would
have helped.

ĸen



Then konsole or dolphin etc starts and works normally as root.

Yup.

I start system-wide D-Bus daemon using etc/rc.d/init.d/dbus from blfs
bootscripts

I start KDE and the session dbus daemon using a .xinitrc
cat ~/.xinitrc
# Begin .xinitrc
exec ck-launch-session dbus-launch --exit-with-session startkde
# End .xinitrc

This is pretty much the same reason we dumped systemd in -dev.  It
doesn't play nice when consolekit is linked with systemd libraries and
using a System V init.

   -- Bruce




Hello Ken, Bruce and all,

Thank you for your help.

What is the best way out of this?

removing "ck-launch-session" from "exec ck-launch-session dbus-launch
--exit-with-session startkde does not help.

I also tried rebuilding d-bus-1.8.0. No change.

My KDE "kdesu konsole" and "kdesu dolphin" icons do nothing. I get the
kdesu window for root password and then nothing. (I do not yet have a
mail client on kde and ssh -X from this computer to BLFS system seem to
mess up things even more, I will try and send a clean log later).

What is the best way out of this given my baseline of LFS systemd for
/dev and sysVinit for init + BLFS with consolekit?

Do I have to uninstall consolekit and start over from LFS level or from
BLFS KDE level and reinstall large pieces or can I do something smarter?
Remove systemd and change to eudev, separately?

Well, what I did was start over from the current LFS-svn on a fresh partition. Have you tried working from the system booting systemd?

The problem is that the systemd libraries infiltrate a lot of packages and pollute a lot of them.

  -- Bruce

--
http://lists.linuxfromscratch.org/listinfo/blfs-support
FAQ: http://www.linuxfromscratch.org/blfs/faq.html
Unsubscribe: See the above information page

Reply via email to