Bug 920026 - [abrt] bleachbit-0.8.7-3.fc18: __init__.py:52:_init:RuntimeError: could not open display
Summary: [abrt] bleachbit-0.8.7-3.fc18: __init__.py:52:_init:RuntimeError: could not o...
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Fedora
Classification: Fedora
Component: bleachbit
Version: 18
Hardware: x86_64
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Rahul Sundaram
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard: abrt_hash:44dad3ed2a40d9c18cbe586456d...
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-03-11 08:04 UTC by goesrex
Modified: 2014-05-02 14:45 UTC (History)
6 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2014-02-05 19:51:23 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)
File: backtrace (972 bytes, text/plain)
2013-03-11 08:04 UTC, goesrex
no flags Details
File: core_backtrace (305 bytes, text/plain)
2013-03-11 08:04 UTC, goesrex
no flags Details
File: environ (3.53 KB, text/plain)
2013-03-11 08:04 UTC, goesrex
no flags Details

Description goesrex 2013-03-11 08:04:47 UTC
Version-Release number of selected component:
bleachbit-0.8.7-3.fc18

Additional info:
cmdline:        python /usr/bin/bleachbit
dso_list:       pygtk2-2.24.0-5.fc18.x86_64
executable:     /usr/bin/bleachbit
kernel:         3.8.1-201.fc18.x86_64
uid:            0

Truncated backtrace:
__init__.py:52:_init:RuntimeError: could not open display

Traceback (most recent call last):
  File "/usr/bin/bleachbit", line 41, 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', '/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/PIL', '/usr/lib64/python2.7/site-packages/pbs', '/usr/lib64/python2.7/site-packages/gtk-2.0', '/usr/lib/python2.7/site-packages', '/usr/lib/python2.7/site-packages/setuptools-0.6c11-py2.7.egg-info', '/usr/share/']

Potential duplicate: bug 843674

Comment 1 goesrex 2013-03-11 08:04:50 UTC
Created attachment 708236 [details]
File: backtrace

Comment 2 goesrex 2013-03-11 08:04:52 UTC
Created attachment 708237 [details]
File: core_backtrace

Comment 3 goesrex 2013-03-11 08:04:54 UTC
Created attachment 708238 [details]
File: environ

Comment 4 iichron714 2013-05-08 16:49:58 UTC
Description of problem:
1. downloaded rpm from sourceforge in response to new version available pop up when opening bleachbit for first time
2. used apper to install the package
3. copied bleachbit as root app to translucent folder on desktop and opened it
4. received selinux error message :BleachBit crashed  _init_.py:52:RuntimeError: could not open display

Name BleachBit
Version bleachbit-0.9.5-1.1

Version-Release number of selected component:
bleachbit-0.9.5-1.1

Additional info:
cmdline:        python /usr/bin/bleachbit
dso_list:       pygtk2-2.24.0-5.fc18.i686
executable:     /usr/bin/bleachbit
kernel:         3.8.11-200.fc18.i686
uid:            0
ureports_counter: 1

Truncated backtrace:
__init__.py:52:_init:RuntimeError: could not open display

Traceback (most recent call last):
  File "/usr/bin/bleachbit", line 41, in <module>
    import gtk
  File "/usr/lib/python2.7/site-packages/gtk-2.0/gtk/__init__.py", line 64, in <module>
    _init()
  File "/usr/lib/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', '/usr/lib/python27.zip', '/usr/lib/python2.7', '/usr/lib/python2.7/plat-linux2', '/usr/lib/python2.7/lib-tk', '/usr/lib/python2.7/lib-old', '/usr/lib/python2.7/lib-dynload', '/usr/lib/python2.7/site-packages', '/usr/lib/python2.7/site-packages/gtk-2.0', '/usr/share/']

Comment 5 david sutherland 2013-10-20 19:31:39 UTC
With the following kernel updates:
     3.10.13-101.fc18.x86_64
     3.10.14-100.fc18.x86_64
     3.11.4-101.fc18.x86_64
I cannot open bleachbit, gedit, or leafpad under sudo root.
Have to revert back to kernel-3.10.12-100.fc18.x86_64.

Comment 6 Fedora End Of Life 2013-12-21 12:03:33 UTC
This message is a reminder that Fedora 18 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 18. 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 WONTFIX if it remains open with a Fedora 
'version' of '18'.

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 prior to Fedora 18's end of life.

Thank you for reporting this issue and we are sorry that we may not be 
able to fix it before Fedora 18 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 to Fedora 18's end of life.

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.

Comment 7 Fedora End Of Life 2014-02-05 19:51:23 UTC
Fedora 18 changed to end-of-life (EOL) status on 2014-01-14. Fedora 18 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.


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