Red Hat Bugzilla – Bug 589548
virt-manager: gconf error launching app as root
Last modified: 2010-06-10 11:34:31 EDT
Created attachment 411987 [details]
The error's screenshot after we type int virt-manager
Description of problem:
Input virt-manager commadn in terminal as root,But I can't start it.
Version-Release number of selected component (if applicable):
[unanao@dhcp-65-37 ~]$ cat /etc/redhat-release
Red Hat Enterprise Linux Server release 6.0 Beta (Santiago)
[unanao@dhcp-65-37 ~]$ rpm -qa |grep libvirt
[unanao@dhcp-65-37 ~]$ rpm -q virt-manager
Steps to Reproduce:
1.Open the terminal
2.Switch to root
Got the popup window and get the error message.I have put the pop-up window's screenshot in the attachment.
When we type in virt-manager as root ,we can start the virt-manager.
The testing is on a cleaned machine.
This request was evaluated by Red Hat Product Management for inclusion in a Red
Hat Enterprise Linux major release. Product Management has requested further
review of this request by Red Hat Engineering, for potential inclusion in a Red
Hat Enterprise Linux Major release. This request is not yet committed for
How exactly are you launching the application? Are you logging in as root or using 'su'? Can you provide the exact steps to reproduce?
(In reply to comment #3)
> How exactly are you launching the application? Are you logging in as root or
> using 'su'? Can you provide the exact steps to reproduce?
I'm sorry!I have replyied so late!Because I applied for one week to return my university.
I use 'su',My procedure is :
[unanao@dhcp-65-37 ~]$ su
[root@dhcp-65-37 unanao]# virt-manager
And then I will get a pop-window,get the message:
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.)
Using just plain 'su' will cause issues with other display and gconf using apps as well. Use 'su -' to actually start a new environment, which should solve the issues you reported.