Bug 702791 - virt-manager fails to start from a fresh fc15 install
Summary: virt-manager fails to start from a fresh fc15 install
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: Fedora
Classification: Fedora
Component: virt-manager
Version: 15
Hardware: x86_64
OS: Linux
unspecified
low
Target Milestone: ---
Assignee: Cole Robinson
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-05-07 09:05 UTC by Gary Lucas
Modified: 2011-05-09 14:22 UTC (History)
5 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2011-05-09 14:22:13 UTC
Type: ---


Attachments (Terms of Use)

Description Gary Lucas 2011-05-07 09:05:19 UTC
Description of problem:
> start virt-manager from shell.  Get error message


Version-Release number of selected component (if applicable):
virt-manager-0.8.7-4.fc15.noarch

How reproducible:
100%

Steps to Reproduce:
1. Type 'virt-manager' into console.
2. Error message:



Actual results:
# virt-manager 
Traceback (most recent call last):
  File "/usr/share/virt-manager/virt-manager.py", line 466, in <module>
    main()
  File "/usr/share/virt-manager/virt-manager.py", line 360, in main
    raise gtk_error
RuntimeError: could not open display

Expected results:
virt-manager launches.

Additional info:
This worked in f14

Comment 1 Gary Lucas 2011-05-07 09:06:28 UTC
NOte: I start with virt-manager from fc14, updated to the rawhide to see if that would make a difference.  Same effect either way.

Comment 2 Gary Lucas 2011-05-07 15:59:27 UTC
Can now start virt-manager

If I'm in a root shell I get the above error.  If I start virt-manager as non-root it can't talk to my libvirtd...

However the following works:
sudo virt-manager

And virt-manager successfully starts.

Comment 3 Cole Robinson 2011-05-09 14:22:13 UTC
I assume you used 'su' to switch to root rather than 'su -'. The former will prevent all GTK apps from running AFAIK.

Closing as NOTABUG


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