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.
Bug 869145 - virt-manager not opening using sudo access
Summary: virt-manager not opening using sudo access
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: virt-manager
Version: 6.3
Hardware: x86_64
OS: Linux
unspecified
high
Target Milestone: rc
: 6.3
Assignee: virt-mgr-maint
QA Contact: Virtualization Bugs
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2012-10-23 07:04 UTC by Vijaykumar
Modified: 2012-10-24 15:03 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2012-10-24 15:03:37 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)

Description Vijaykumar 2012-10-23 07:04:34 UTC
Description of problem:
Normal user with sudo access unable to open virt-manager. Getting below error.

[vijneman@KVMHost-5CF3FC94C58C Desktop]$ sudo virt-manager
[sudo] password for vijneman: 
No protocol specified
Traceback (most recent call last):
  File "/usr/share/virt-manager/virt-manager.py", line 383, in <module>
    main()
  File "/usr/share/virt-manager/virt-manager.py", line 286, in main
    raise gtk_error
RuntimeError: could not open display

Version-Release number of selected component (if applicable):


How reproducible:
sudo virt-manager

Steps to Reproduce:
1.Login to server with normal user.
2.start vnc with normal user and login to vnc session
3. run sudo virt-manager
  
Actual results:

[vijneman@KVMHost-5CF3FC94C58C Desktop]$ sudo virt-manager
[sudo] password for vijneman: 
No protocol specified
Traceback (most recent call last):
  File "/usr/share/virt-manager/virt-manager.py", line 383, in <module>
    main()
  File "/usr/share/virt-manager/virt-manager.py", line 286, in main
    raise gtk_error
RuntimeError: could not open display
Expected results:
Virt-manager suppose to be open

Additional info:

Comment 2 Dave Allan 2012-10-23 13:37:19 UTC
You need to allow virt-manager permissions to your xdisplay.

Comment 3 Vijaykumar 2012-10-24 11:34:00 UTC
Please any body know the solution for this, still I am unable to open the virt-manager.

Comment 4 Dave Allan 2012-10-24 15:03:37 UTC
Bugzilla is not a tool for asking usage questions.  For Red Hat product questions please contact the support organization or for upstream questions please see: http://libvirt.org/contact.html  Please don't reopen the BZ.


Note You need to log in before you can comment on or make changes to this bug.