Hello,

I'm using the latest kde version compiled from source.

I'm working on a construction which creates an environment like GoboLinux, where the normal standard system directories are hidden. My construction is using a FUSE fs and chroot to achieve this.
The root directories are:

/Computer
/Home
/Mounts
/Network
/System

and again, the directories /bin, /boot, /dev, /lib, etc. are there, but hidden.


When using this construction, a chroot is done using pamchroot.

I had this working using the previous kde version (december 2010) but now I've upgraded to the last kde version (4.6.0) my desktop won't start, complaining the connection to dbus is not possible,
(QDBusConnectionPrivate::connectSignal error, possible causes messagebus security policy blocked signal).

Has something changed in the way the dbus session daemon is started??

Stef

I would recommend verifying that ~/.dbus is read-write to your user, and that the environment variable DISPLAY is present and set correctly.

Well


.xsession-errors | grep plasma-desktop no error:

plasma-desktop(6652)/libplasma Plasma::FrameSvg::resizeFrame: Invalid size QSizeF(0, 0)
plasma-desktop(6652)/libakonadi Akonadi::AgentManagerPrivate::createDBusInterface: AgentManager failed to get a valid AgentManager DBus interface. Error is: 1 "org.freedesktop.DBus.Error.NameHasNoOwner" "Could not get owner of name 'org.freedesktop.Akonadi.Control': no such name"
plasma-desktop(6652)/libakonadi Akonadi::SessionPrivate::socketError: Socket error occurred: "QLocalSocket::connectToServer: Invalid name"
plasma-desktop(6652)/libakonadi Akonadi::SessionPrivate::socketError: Socket error occurred: "QLocalSocket::connectToServer: Invalid name"
Invalid D-BUS interface name 'org.kde.plasma-desktop.PlasmaApp' found while parsing introspection
plasma-desktop(6652)/libakonadi Akonadi::SessionPrivate::socketError: Socket error occurred: "QLocalSocket::connectToServer: Invalid name"
plasma-desktop(6652)/plasma StatusNotifierItemSource::refreshCallback: DBusMenu disabled for this application
plasma-desktop(6652)/plasma StatusNotifierItemSource::refreshCallback: DBusMenu disabled for this application
plasma-desktop(6652)/plasma StatusNotifierItemSource::refreshCallback: DBusMenu disabled for this application
plasma-desktop(6652)/plasma StatusNotifierItemSource::refreshCallback: DBusMenu disabled for this application

.xsession-errors | grep plasma-desktop with error


plasma-desktop(12620)/libplasma Plasma::FrameSvg::resizeFrame: Invalid size QSizeF(0, 0)
plasma-desktop(12620)/libplasma Plasma::FrameSvg::resizeFrame: Invalid size QSizeF(0, 0)
plasma-desktop(12620)/libplasma Plasma::FrameSvg::resizeFrame: Invalid size QSizeF(0, 0)
plasma-desktop(12620)/libakonadi Akonadi::AgentManagerPrivate::createDBusInterface: AgentManager failed to get a valid AgentManager DBus interface. Error is: 1 "org.freedesktop.DBus.Error.NameHasNoOwner" "Could not get owner of name 'org.freedesktop.Akonadi.Control': no such name"
plasma-desktop(12620)/libakonadi Akonadi::SessionPrivate::socketError: Socket error occurred: "QLocalSocket::connectToServer: Invalid name"
plasma-desktop(12620)/libakonadi Akonadi::SessionPrivate::socketError: Socket error occurred: "QLocalSocket::connectToServer: Invalid name"
Invalid D-BUS interface name 'org.kde.plasma-desktop.PlasmaApp' found while parsing introspection
plasma-desktop(12619): Communication problem with "plasma-desktop" , it probably crashed.


after that more errors like:

Error message was: "org.freedesktop.DBus.Error.NoReply" : " "Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken." "

ksmserver(11472)/kdeui (KNotification) KNotification::slotReceivedIdError: Error while contacting notify daemon "Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken."
knotify(12611)/phonon (KDE plugin): QDBusError("org.freedesktop.DBus.Error.NoReply", "Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.")
knotify(12611)/phonon (KDE plugin): QDBusError("org.freedesktop.DBus.Error.NoReply", "Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.")

So the plasma desktop has crashed. I'm testing now with a compete new user, having no existing conf.

Get back soon,

Stef

Well thanks for your reaction bcooksley,

I will look into this futher.
My fs, FUSE fs has since a week a new main event loop, using epoll and worker threads. It's very fast, but it's possible that it's blocking. I will dig into this.

I will report back later, hope soon.

Thanks again,

Stef

Looking at the log you posted, it appears that D-Bus itself may be having issues. Does running "dbus-launch" work ok?

Well I've been working on the construction which creates the chroot.

Previous I had the system remounted at :

<chrootpath>/System/Root

and hidden symlinks like

<chrootpath>/bin -> System/Root/bin


Now I've got the system remounted directly like:

mount --bind /bin <chrootpath>/bin
etc.

There is no problem anymore.
The directory <chrootpath>/bin is still created in the fuse fs, and like you see it's possible to remount another fs at it, and hiding it at the same time.

So I've not solved the problem, in the sense I've found the cause.
But it's working again like it should.

Stef