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
Created attachment 598287 [details] File: backtrace
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
*** Bug 879971 has been marked as a duplicate of this bug. ***