Description of problem: Virt-manager fails to open, not completely sure if this was caused by an update, but my guess. As a test I updated libvirt and virt-manager from testing, same problem. [root@main andy]# virt-manager (virt-manager:1970): GConf-WARNING **: Client failed to connect to the D-BUS 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. [root@main andy]# Details from the Error on the GUI: Error starting Virtual Machine Manager: No D-BUS daemon running Traceback (most recent call last): File "/usr/share/virt-manager/virt-manager.py", line 392, in <module> main() File "/usr/share/virt-manager/virt-manager.py", line 327, in main options.testfirstrun) File "/usr/share/virt-manager/virtManager/config.py", line 99, in __init__ self.conf.add_dir(self.conf_dir, gconf.CLIENT_PRELOAD_NONE) GError: No D-BUS daemon running Version-Release number of selected component (if applicable): [root@main andy]# rpm -qa|grep virt-manager virt-manager-0.9.4-3.fc17.noarch virt-manager-common-0.9.4-3.fc17.noarch [root@main andy]# rpm -qa|grep libvirt libvirt-0.9.11.8-2.fc17.x86_64 libvirt-daemon-0.9.11.8-2.fc17.x86_64 libvirt-daemon-config-nwfilter-0.9.11.8-2.fc17.x86_64 libvirt-client-0.9.11.8-2.fc17.x86_64 libvirt-python-0.9.11.8-2.fc17.x86_64 libvirt-daemon-config-network-0.9.11.8-2.fc17.x86_64 [root@main andy]# rpm -qa|grep dbus abrt-dbus-2.0.18-1.fc17.x86_64 dbus-python-0.83.0-9.fc17.x86_64 dbus-x11-1.4.10-7.fc17.x86_64 dbus-1.4.10-7.fc17.x86_64 dbus-glib-0.98-2.fc17.x86_64 dbus-libs-1.4.10-7.fc17.x86_64 gambas3-gb-dbus-3.3.4-2.fc17.x86_64 python-slip-dbus-0.2.20-2.fc17.noarch [root@main andy]# [root@main andy]# systemctl status dbus dbus.service - D-Bus System Message Bus Loaded: loaded (/usr/lib/systemd/system/dbus.service; static) Active: active (running) since Thu, 27 Dec 2012 16:43:49 -0500; 39min ago Main PID: 701 (dbus-daemon) CGroup: name=systemd:/system/dbus.service ├ 701 /bin/dbus-daemon --system --address=systemd: --nofork --systemd-activation ├ 705 /usr/libexec/polkit-1/polkitd --no-debug ├ 719 /usr/sbin/modem-manager └ 2182 /usr/libexec/fprintd Dec 27 16:54:58 main dbus[701]: [system] Activating service name='org.freedesktop.PackageKit' (using servicehelper) Dec 27 16:54:58 main dbus-daemon[701]: dbus[701]: [system] Successfully activated service 'org.freedesktop.PackageKit' Dec 27 16:54:58 main dbus[701]: [system] Successfully activated service 'org.freedesktop.PackageKit' Dec 27 17:22:58 main dbus-daemon[701]: dbus[701]: [system] Activating service name='net.reactivated.Fprint' (using servicehelper) Dec 27 17:22:58 main dbus[701]: [system] Activating service name='net.reactivated.Fprint' (using servicehelper) Dec 27 17:22:58 main dbus-daemon[701]: Launching FprintObject Dec 27 17:22:58 main dbus-daemon[701]: dbus[701]: [system] Successfully activated service 'net.reactivated.Fprint' Dec 27 17:22:58 main dbus[701]: [system] Successfully activated service 'net.reactivated.Fprint' Dec 27 17:22:58 main dbus-daemon[701]: ** Message: D-Bus service launched with name: net.reactivated.Fprint Dec 27 17:22:58 main dbus-daemon[701]: ** Message: entering main loop [root@main andy]# [root@main andy]# uname -a; cat /etc/*release Linux main 3.6.10-2.fc17.x86_64 #1 SMP Tue Dec 11 18:07:34 UTC 2012 x86_64 x86_64 x86_64 GNU/Linux Fedora release 17 (Beefy Miracle) NAME=Fedora VERSION="17 (Beefy Miracle)" ID=fedora VERSION_ID=17 PRETTY_NAME="Fedora 17 (Beefy Miracle)" ANSI_COLOR="0;34" CPE_NAME="cpe:/o:fedoraproject:fedora:17" Fedora release 17 (Beefy Miracle) Fedora release 17 (Beefy Miracle) [root@main andy]# How reproducible: Everytime Happy to provide any further details, test etc.
I have found that if I restart the dbus service after the complete system boot, it works. This is also 100% repeatable.
Thanks for the report Andy. Does 'virt-manager --debug' also reproduce the failure?
Please see the below output with the debug switch: From the GUI: Error starting Virtual Machine Manager: No D-BUS daemon running Traceback (most recent call last): File "/usr/share/virt-manager/virt-manager.py", line 392, in <module> main() File "/usr/share/virt-manager/virt-manager.py", line 327, in main options.testfirstrun) File "/usr/share/virt-manager/virtManager/config.py", line 99, in __init__ self.conf.add_dir(self.conf_dir, gconf.CLIENT_PRELOAD_NONE) GError: No D-BUS daemon running Console output: [root@main andy]# virt-manager --debug 2013-01-06 13:16:11,435 (cli:71): virt-manager startup 2013-01-06 13:16:11,435 (virt-manager:302): Launched as: /usr/share/virt-manager/virt-manager.py --debug 2013-01-06 13:16:11,435 (virt-manager:303): GTK version: (2, 24, 13) 2013-01-06 13:16:11,435 (virt-manager:304): virt-manager version: 0.9.4 2013-01-06 13:16:11,436 (virt-manager:305): virtManager import: <module 'virtManager' from '/usr/share/virt-manager/virtManager/__init__.pyc'> 2013-01-06 13:16:11,494 (cli:118): virtinst version: 0.600.3 2013-01-06 13:16:11,494 (cli:119): virtinst import: <module 'virtinst' from '/usr/lib/python2.7/site-packages/virtinst/__init__.pyc'> (virt-manager:1756): GConf-WARNING **: Client failed to connect to the D-BUS 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. 2013-01-06 13:16:11,520 (virt-manager:399): No D-BUS daemon running Traceback (most recent call last): File "/usr/share/virt-manager/virt-manager.py", line 392, in <module> main() File "/usr/share/virt-manager/virt-manager.py", line 327, in main options.testfirstrun) File "/usr/share/virt-manager/virtManager/config.py", line 99, in __init__ self.conf.add_dir(self.conf_dir, gconf.CLIENT_PRELOAD_NONE) GError: No D-BUS daemon running [root@main andy]#
Mmmmm, OK, this is probably my fault. When I "su" to root, I receive the above error. When I "su -" it works normally. For whatever reason just "su" to root used to work when launching virt-manager. I don't normally use the menu option to launch virt-manager, but when I do it also functions normally. Not sure why "su" used to work but I realize "su -" is correct when launching anything with a GUI. Likely operator error, not a bug! Please confirm and feel free to close. Thanks
Thanks for following up Andy Yeah there is a lot of weirdness with dbus and 'su', it's always recommended to use 'su -' in this case. We've had several bugs like this over the years, though not sure why 'su' was working for you before. Closing as NOTABUG
Sometimes, even the above method doesn't work. In that case, one has to become root and type the following command: # dbus-uuidgen > /var/lib/dbus/machine-id
(In reply to Nehal J Wani from comment #6) > Sometimes, even the above method doesn't work. In that case, one has to > become root and type the following command: > > # dbus-uuidgen > /var/lib/dbus/machine-id Just want to comment that I encounter this issue today and Nehal's command to help.
Another workaround for this problem is: # dbus-launch virt-manager