Version-Release number of selected component: uzbl-tabbed-0-0.33.20120514git228bc38cbd.fc20 Additional info: reporter: libreport-2.2.2 cmdline: python /usr/bin/uzbl-tabbed dso_list: pygtk2-2.24.0-8.fc20.x86_64 executable: /usr/bin/uzbl-tabbed kernel: 3.14.5-200.fc20.x86_64 runlevel: N 5 type: Python uid: 1000 Truncated backtrace: __init__.py:52:_init:RuntimeError: could not open display Traceback (most recent call last): File "/usr/bin/uzbl-tabbed", line 141, in <module> import gtk File "/usr/lib64/python2.7/site-packages/gtk-2.0/gtk/__init__.py", line 64, in <module> _init() File "/usr/lib64/python2.7/site-packages/gtk-2.0/gtk/__init__.py", line 52, in _init _gtk.init_check() RuntimeError: could not open display Local variables in innermost frame: sys: <module 'sys' (built-in)> sys_path: ['/usr/bin', '/home/rbarlow/devel/pulp/platform/src', '/home/rbarlow/devel/pulp_rpm/pulp_rpm/src', '/home/rbarlow/devel/pulp/pulp_devel', '/home/rbarlow/devel/nectar', '/usr/lib/python2.7/site-packages/requests-1.2.0-py2.7.egg', '/usr/lib/python2.7/site-packages/eventlet-0.12.1-py2.7.egg', '/home/rbarlow/devel/pulp_rpm/plugins', '/usr/lib64/python27.zip', '/usr/lib64/python2.7', '/usr/lib64/python2.7/plat-linux2', '/usr/lib64/python2.7/lib-tk', '/usr/lib64/python2.7/lib-old', '/usr/lib64/python2.7/lib-dynload', '/usr/lib64/python2.7/site-packages', '/usr/lib64/python2.7/site-packages/gst-0.10', '/usr/lib64/python2.7/site-packages/gtk-2.0', '/usr/lib/python2.7/site-packages']
Created attachment 904664 [details] File: backtrace
Created attachment 904665 [details] File: environ
Looks like you're trying to run uzbl-tabbed without X. How did you start uzbl-tabbed?
You know, I think I remember that happening yesterday now that you mention X. I had used ssh to run UZBL, and perhaps I neglected to use the -X flag on ssh. I would expect uzbl to handle this more gracefully though perhaps by printing an error to the terminal and exiting, rather than crashing.
Well, this is actually GTK's exception. Unfortunately, it's a plain old RuntimeError and not something uzbl would be able to give specific instructions about (I imagine the string is translated, so string comparisons would be useless). Reassigning to pygtk in the hope that more information could be given in the exception (or the message be improved to ask the user to check for X).
This package has changed ownership in the Fedora Package Database. Reassigning to the new owner of this component.
This message is a reminder that Fedora 20 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 20. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a Fedora 'version' of '20'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 20 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
Fedora 20 changed to end-of-life (EOL) status on 2015-06-23. Fedora 20 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed.