On Fedora 17 updated: virt-manager-0.9.4-2.fc17.noarch libvirt-0.10.2.1-1.fc17.x86_64 after a reboot, virt-manager no longer starts. Used to! virt-manager & [1] 1676 [root@sixcore ~]# (virt-manager:1676): GConf-WARNING **: Client failed to connect to the D-BUS daemon: Failed to connect to socket /tmp/dbus-0v4E2bXlqf: Connection refused Traceback (most recent call last): File "/usr/share/virt-manager/virt-manager.py", line 386, in <module> main() File "/usr/share/virt-manager/virt-manager.py", line 321, in main config = virtManager.config.vmmConfig(appname, appversion, ui_dir) File "/usr/share/virt-manager/virtManager/config.py", line 98, in __init__ self.conf.add_dir(self.conf_dir, gconf.CLIENT_PRELOAD_NONE) GError: No D-BUS daemon running [root@sixcore ~]# systemctl status dbus.service dbus.service - D-Bus System Message Bus Loaded: loaded (/usr/lib/systemd/system/dbus.service; enabled) Active: active (running) since Mon, 29 Oct 2012 16:53:41 -0400; 2s ago Process: 1669 ExecStartPre=/bin/rm -f /var/run/messagebus.pid (code=exited, status=0/SUCCESS) Process: 1666 ExecStartPre=/bin/dbus-uuidgen --ensure (code=exited, status=0/SUCCESS) Main PID: 1672 (dbus-daemon) CGroup: name=systemd:/system/dbus.service └ 1672 /bin/dbus-daemon --system --address=systemd: --nofork --systemd-activation Any help appreciated, sean