Dear Maintainer,

Can't launch virt-manager without crash :

virt-manager --no-fork --debug
2013-08-22 13:26:41,949 (cli:71): virt-manager startup
2013-08-22 13:26:41,949 (virt-manager:306): Launched as: /usr/share/virt-
manager/virt-manager.py --no-fork --debug
2013-08-22 13:26:41,949 (virt-manager:307): GTK version: (2, 24, 20)
2013-08-22 13:26:41,949 (virt-manager:308): virt-manager version: 0.9.5
2013-08-22 13:26:41,949 (virt-manager:309): virtManager import: <module
'virtManager' from '/usr/share/virt-manager/virtManager/__init__.pyc'>
2013-08-22 13:26:42,017 (cli:118): virtinst version: 0.600.4
2013-08-22 13:26:42,018 (cli:119): virtinst import: <module 'virtinst' from
'/usr/lib/pymodules/python2.7/virtinst/__init__.pyc'>

(virt-manager:25092): 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-08-22 13:26:42,045 (virt-manager:409): 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


And DBUS seems to be running :
 ps -ef | grep dbus
message+  3571     1  0 12:13 ?        00:00:00 /usr/bin/dbus-daemon --system
jpp       6269     1  0 12:13 ?        00:00:00 dbus-launch
--autolaunch=518bdeca03136aa1ef07c46100000008 --binary-syntax --close-stderr
jpp       6270  6148  0 12:13 ?        00:00:00 /usr/bin/ssh-agent /usr/bin
/dbus-launch --exit-with-session gnome-session-fallback
jpp       6274     1  0 12:13 ?        00:00:00 /usr/bin/dbus-launch --exit-
with-session gnome-session-fallback
jpp       6276     1  0 12:13 ?        00:00:00 /usr/bin/dbus-daemon --fork
--print-pid 5 --print-address 7 --session
jpp       6277     1  0 12:13 ?        00:00:00 /usr/bin/dbus-daemon --fork
--print-pid 5 --print-address 7 --session
jpp       6292  6285  0 12:13 ?        00:00:00 /usr/bin/dbus-daemon --config-
file=/etc/at-spi2/accessibility.conf --nofork --print-address 3

Regards

JP P

severity 720484 normal

So is DBus available or isn't it? Just having the daemon running tells
us little (you're not even telling us the user you're running the
program with). Check DBUS_SESSION_BUS_ADDRESS.

Note that this is after all a gconf error. Did you try running gconftool
from within the same session?
 -- Guido