Bug 602751 - [abrt] crash in gmixer-1.3-15.fc13: display.py:120:__init__:DisplayConnectionError: Can't connect to display "": No protocol specified
Summary: [abrt] crash in gmixer-1.3-15.fc13: display.py:120:__init__:DisplayConnection...
Alias: None
Product: Fedora
Classification: Fedora
Component: python-xlib
Version: 13
Hardware: i686
OS: Linux
Target Milestone: ---
Assignee: Jef Spaleta
QA Contact: Fedora Extras Quality Assurance
Whiteboard: abrt_hash:70ec8fc6
Depends On:
TreeView+ depends on / blocked
Reported: 2010-06-10 16:20 UTC by Chris Miller
Modified: 2011-06-27 17:57 UTC (History)
1 user (show)

Clone Of:
Last Closed: 2011-06-27 17:57:25 UTC

Attachments (Terms of Use)
File: backtrace (1.18 KB, text/plain)
2010-06-10 16:20 UTC, Chris Miller
no flags Details

Description Chris Miller 2010-06-10 16:20:10 UTC
abrt 1.1.0 detected a crash.

architecture: i686
cmdline: /usr/bin/python -OO /usr/bin/gmixer -d
component: gmixer
executable: /usr/bin/gmixer
package: gmixer-1.3-15.fc13
reason: display.py:120:__init__:DisplayConnectionError: Can't connect to display "": No protocol specified
release: Fedora release 13 (Goddard)

display.py:120:__init__:DisplayConnectionError: Can't connect to display "": No protocol specified

Traceback (most recent call last):
  File "/usr/lib/python2.6/site-packages/gtktrayicon.py", line 114, in on_realize
    xdisplay = self.get_xdisplay()
  File "/usr/lib/python2.6/site-packages/gtktrayicon.py", line 161, in get_xdisplay
    xdisplay =  Xdisplay.Display(name)
  File "/usr/lib/python2.6/site-packages/Xlib/display.py", line 83, in __init__
    self.display = _BaseDisplay(display)
  File "/usr/lib/python2.6/site-packages/Xlib/display.py", line 65, in __init__
    apply(protocol.display.Display.__init__, (self, ) + args, keys)
  File "/usr/lib/python2.6/site-packages/Xlib/protocol/display.py", line 120, in __init__
    raise error.DisplayConnectionError(self.display_name, r.reason)
DisplayConnectionError: Can't connect to display "": No protocol specified

Local variables in innermost frame:
name: ''
displayno: 11
self: <Xlib.display._BaseDisplay instance at 0x921846c>
display: ''
auth_data: ''
auth_name: ''
host: ''
r: <Xlib.protocol.display.ConnectionSetupRequest instance at 0x922144c>
screenno: 0
order: 108

Comment 1 Chris Miller 2010-06-10 16:20:11 UTC
Created attachment 422962 [details]
File: backtrace

Comment 2 Bug Zapper 2011-06-02 11:19:19 UTC
This message is a reminder that Fedora 13 is nearing its end of life.
Approximately 30 (thirty) days from now Fedora will stop maintaining
and issuing updates for Fedora 13.  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 '13'.

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 13's end of life.

Bug Reporter: Thank you for reporting this issue and we are sorry that 
we may not be able to fix it before Fedora 13 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 please change the 'version' of this 
bug to the applicable version.  If you are unable to change the version, 
please add a comment here and someone will do it for you.

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.

The process we are following is described here: 

Comment 3 Bug Zapper 2011-06-27 17:57:25 UTC
Fedora 13 changed to end-of-life (EOL) status on 2011-06-25. Fedora 13 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.

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.