Am Samstag 08 Januar 2011 schrieb Justin Clift:

On 09/01/2011, at 3:29 AM, Matthias Meyer wrote:

...

Hi,

Since today I can't start virt-manager anymore :-( Failed to connect to socket /tmp/dbus-yhDz4m8loi By the way the same message as I get from qdbus.

There are no files called /tmp/dbus* on my system but some dbus applications are running: linux-dev:~# ps ax | grep dbus 1774 ? Ss 0:00 /usr/bin/dbus-daemon --system 2436 ? S 0:00 dbus-launch --autolaunch 1996d3ce005bf1ed73cca8164d21a0b5 --binary-syntax --close-stderr 2437 ? Ss 0:00 /usr/bin/dbus-daemon --fork --print-pid 5 --print-address 7 --session

The error-message-box containing: most common cause is a missing or misconfigured D-Bus session bus daemon. See http://projects.gnome.org/gconf/ But I've removed gnome and installed KDE.

Hi Matthias,

(I'm about to get some sleep, so won't be of direct help with this.)

But, you forgot to mention which linux distro you're using. RHEL? Fedora? Ubuntu? Slackware? etc. :)

Regards and best wishes,

Justin Clift

Sorry :-) I am using Debian testing (sqeeze) -- Don't Panic

Am Montag 10 Januar 2011 schrieb Nicolas Sebrecht:

The 08/01/11, Matthias Meyer wrote:

...

Hi,

Since today I can't start virt-manager anymore :-( Failed to connect to socket /tmp/dbus-yhDz4m8loi By the way the same message as I get from qdbus.

I hit a similar problem.

It happens when I connect with ssh to different hosts with X11 redirection. I can't launch multiple virt-manager session this way on multiple hosts. I need to completely disconnect the previous ssh session where a virt-manager instance was launched.

Not sure it is the same issue, though.

-- Nicolas Sebrecht

I don't believe that is the same problem. My problem occurs just after reboot too. In the meantime I've reinstalled my laptop with debian stable. br Matthias -- Don't Panic