Comment 5 for bug 57389

I ran into this while using Edgy on a chroot, which has no /dev or /var/run/dbus --bind mounted, so Edgy's nautilus can't see running dbus. I didn't think of looking dependencies recursively, so I guess this is sorted.

That dbus restart bug seems to plague many (all?) applications that connect to running dbus instance. I've experienced it with rhythmbox and banshee at least.

You can close this as rejected.