Some days back I was trying to start #virt-manager application from my fedora 18 system and got the error :
The error details looked :
Error starting Virtual Machine Manager: No D-BUS daemon running
Traceback (most recent call last):
File “/usr/share/virt-manager/virt-manager.py”, line 402, in <module>
main()
File “/usr/share/virt-manager/virt-manager.py”, line 333, 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
But when checking ‘dbus’ status I noticed, it’s up and running.
$ service dbus status
Redirecting to /bin/systemctl status dbus.service
dbus.service – D-Bus System Message Bus
Loaded: loaded (/usr/lib/systemd/system/dbus.service; static)
Active: active (running) since Sat 2013-05-18 21:11:06 IST; 2 days ago
Main PID: 539 (dbus-daemon)
CGroup: name=systemd:/system/dbus.service
├─ 539 /bin/dbus-daemon –system –address=systemd: –nofork –nopidfile –systemd-activation
├─ 756 /usr/sbin/modem-manager
└─5023 /usr/lib64/realmd/realmd
then whats the issue?
Later I found, I am able to run #virt-manager as a non-previleged user
then I tried again as root, that too worked.. Only this shell gives me error, unfortunately, it was a shell where I did “su” to become “root”, later trying “su-” also worked. So something going on with “su” and “virt-manager”…
Thank you, ‘su -‘ worked for me whereas ‘su’ didn’t.