Bug 840277

Summary: [abrt] virt-manager-0.8.7-2.fc14: virt-manager.py:360:main:RuntimeError: could not open display
Product: [Fedora] Fedora Reporter: chuck elliot <c.elliot>
Component: virt-managerAssignee: Cole Robinson <crobinso>
Status: CLOSED WONTFIX QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 14CC: berrange, crobinso, dpierce, hbrock, jforbes, Triv, virt-maint
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Unspecified   
Whiteboard: abrt_hash:5d555bb6
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2012-08-03 00:49:06 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
File: backtrace none

Description chuck elliot 2012-07-15 09:49:04 UTC
abrt version: 1.1.18
architecture: x86_64
cmdline: python /usr/share/virt-manager/virt-manager.py
component: virt-manager
executable: /usr/share/virt-manager/virt-manager.py
kernel: 2.6.35.14-106.fc14.x86_64
package: virt-manager-0.8.7-2.fc14
reason: virt-manager.py:360:main:RuntimeError: could not open display
release: Fedora release 14 (Laughlin)
time: 1342310035
uid: 0

backtrace
-----
virt-manager.py:360:main:RuntimeError: could not open display

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

Local variables in innermost frame:
gtk_error: RuntimeError('could not open display',)
e: RuntimeError('could not open display',)
warnings: <module 'warnings' from '/usr/lib64/python2.7/warnings.pyc'>
ignore: []
origargs: '/usr/share/virt-manager/virt-manager.py'
gobject: <module 'gobject' from '/usr/lib64/python2.7/site-packages/gtk-2.0/gobject/__init__.pyc'>
options: <Values at 0xc55998: {'profile': None, 'nodbus': None, 'show_domain_console': None, 'no_conn_auto': None, 'uuid': None, 'nofork': None, 'show_domain_editor': None, 'show_domain_performance': None, 'show': None, 'uri': None, 'debug': False}>

How to reproduce
-----
1. run virtmanager from console
2. crash
3. requires X but should decline gracefully

Comment 1 chuck elliot 2012-07-15 09:49:07 UTC
Created attachment 598287 [details]
File: backtrace

Comment 2 Cole Robinson 2012-08-03 00:49:06 UTC
F14 is end of life, and this isn't really a bug, all python GTK apps error in the same way so not something I think we should really have to handle. A backtrace is informative enough IMO

Comment 3 Cole Robinson 2012-12-16 16:05:46 UTC
*** Bug 879971 has been marked as a duplicate of this bug. ***