Bug 600927 - [abrt] crash in prelude-notify-0.9-0.4.20080814svn10860.fc12: __init__.py:371:__getitem__:AttributeError: /usr/bin/python: undefined symbol: XScreenSaverAllocInfo
Summary: [abrt] crash in prelude-notify-0.9-0.4.20080814svn10860.fc12: __init__.py:371...
Alias: None
Product: Fedora
Classification: Fedora
Component: prelude-notify
Version: 13
Hardware: i686
OS: Linux
Target Milestone: ---
Assignee: Steve Grubb
QA Contact: Fedora Extras Quality Assurance
Whiteboard: abrt_hash:6cfa4db8
Depends On:
TreeView+ depends on / blocked
Reported: 2010-06-06 18:02 UTC by tomek.by
Modified: 2011-06-27 17:39 UTC (History)
2 users (show)

Clone Of:
Last Closed: 2011-06-27 17:39:28 UTC

Attachments (Terms of Use)
File: backtrace (815 bytes, text/plain)
2010-06-06 18:02 UTC, tomek.by
no flags Details

Description tomek.by 2010-06-06 18:02:13 UTC
abrt 1.1.0 detected a crash.

architecture: i686
cmdline: /usr/bin/python /usr/bin/prelude-notify
component: prelude-notify
executable: /usr/bin/prelude-notify
package: prelude-notify-0.9-0.4.20080814svn10860.fc12
reason: __init__.py:371:__getitem__:AttributeError: /usr/bin/python: undefined symbol: XScreenSaverAllocInfo
release: Fedora release 13 (Goddard)

__init__.py:371:__getitem__:AttributeError: /usr/bin/python: undefined symbol: XScreenSaverAllocInfo

Traceback (most recent call last):
  File "/usr/bin/prelude-notify", line 41, in <module>
    idle = x11idle.X11Idle()
  File "/usr/lib/python2.6/site-packages/PreludeNotify/x11idle.py", line 41, in __init__
    self.xss.XScreenSaverAllocInfo.restype = ctypes.POINTER(XScreenSaverInfo)
  File "/usr/lib/python2.6/ctypes/__init__.py", line 366, in __getattr__
    func = self.__getitem__(name)
  File "/usr/lib/python2.6/ctypes/__init__.py", line 371, in __getitem__
    func = self._FuncPtr((name_or_ordinal, self))
AttributeError: /usr/bin/python: undefined symbol: XScreenSaverAllocInfo

Local variables in innermost frame:
name_or_ordinal: 'XScreenSaverAllocInfo'
self: <CDLL 'None', handle 3cb8f8 at 8950c2c>

Comment 1 tomek.by 2010-06-06 18:02:15 UTC
Created attachment 421628 [details]
File: backtrace

Comment 2 Luke Macken 2010-07-01 02:21:03 UTC
Package: prelude-notify-0.9-0.4.20080814svn10860.fc12
Architecture: i686
OS Release: Fedora release 13 (Goddard)

How to reproduce
1. Boot up the F13 live security lab
2. Click prelude-notify
3. Poof.

Comment 3 Bug Zapper 2011-06-02 11:49:32 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 4 Bug Zapper 2011-06-27 17:39:28 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.