Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Description of problem: Not able to open virtual machine manager (virt-manager) through root user.
Version-Release number of selected component (if applicable):
libvirt-python-0.10.2-46.el6_6.2.x86_64
virt-what-1.11-1.1.el6.x86_64
python-virtinst-0.600.0-24.el6.noarch
virt-manager-0.9.0-28.el6.x86_64
virt-v2v-0.9.1-5.el6_5.x86_64
virt-who-0.3-3.el6.noarch
virt-top-1.0.4-3.11.el6.x86_64
virt-viewer-0.6.0-11.el6.x86_64
libvirt-client-0.10.2-46.el6_6.2.x86_64
libvirt-0.10.2-46.el6_6.2.x86_64
How reproducible:
Steps to Reproduce:
1.virt-manager
2. command only work if I run with dbus-launch command with "exit-with-session" option.
3.
Actual results:
getting below error msg when run virt-manager command.
Error starting Virtual Machine Manager: Failed to contact configuration server; some possible causes are that you need to enable TCP/IP networking for ORBit, or you have stale NFS locks due to a system crash. See http://projects.gnome.org/gconf/ for information. (Details - 1: Failed to get connection to session: 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.)
Traceback (most recent call last):
File "/usr/share/virt-manager/virt-manager.py", line 400, in <module>
main()
File "/usr/share/virt-manager/virt-manager.py", line 329, in main
config = virtManager.config.vmmConfig(appname, appversion, glade_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: Failed to contact configuration server; some possible causes are that you need to enable TCP/IP networking for ORBit, or you have stale NFS locks due to a system crash. See http://projects.gnome.org/gconf/ for information. (Details - 1: Failed to get connection to session: 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.)
Expected results:
its should be open virtual machin manager when run the virt-manager command.
Additional info:
Comment 2Giuseppe Scrivano
2015-01-07 08:42:39 UTC
Could you confirm that this test script fails for you when launched as root with the same error as your report?
-----------------------------------------------------------------
$ cat /tmp/test_gconf.py
#!/usr/bin/python
import gconf
gconf_dir = "/apps/virt-manager"
conf = gconf.client_get_default()
conf.add_dir(gconf_dir, gconf.CLIENT_PRELOAD_NONE)
-----------------------------------------------------------------
Does the problem persist after a reboot?
Still facing Same issue. :-(
below the output from the script
/usr/bin/python
Python 2.6.6 (r266:84292, Dec 7 2011, 20:48:22)
[GCC 4.4.6 20110731 (Red Hat 4.4.6-3)] on linux2
Type "help", "copyright", "credits" or "license" for more information.
>>> import gconf
>>> gconf_dir = "/apps/virt-manager"
>>> conf = gconf.client_get_default()
>>> conf.add_dir(gconf_dir, gconf.CLIENT_PRELOAD_NONE)
Traceback (most recent call last):
File "<stdin>", line 1, in <module>
glib.GError: Failed to contact configuration server; some possible causes are that you need to enable TCP/IP networking for ORBit, or you have stale NFS locks due to a system crash. See http://projects.gnome.org/gconf/ for information. (Details - 1: Failed to get connection to session: 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.)
Comment 4Giuseppe Scrivano
2015-01-30 09:39:03 UTC
the problem is not in virt-manager as it assumes that gconf is working properly, other applications might face the same issue.
Is the dbus daemon running?
I am closing this as WONTFIX, as there is nothing to do in virt-manager, but feel free to comment on this issue.