Bug 588008 - [abrt] crash in deluge-1.1.9-3.fc12: Process /usr/bin/python was killed by signal 11 (SIGSEGV)
Summary: [abrt] crash in deluge-1.1.9-3.fc12: Process /usr/bin/python was killed by si...
Alias: None
Product: Fedora
Classification: Fedora
Component: deluge
Version: 12
Hardware: i686
OS: Linux
Target Milestone: ---
Assignee: Peter Gordon
QA Contact: Fedora Extras Quality Assurance
Whiteboard: abrt_hash:6bee6560c04e8af8e8e1c37e485...
Depends On:
TreeView+ depends on / blocked
Reported: 2010-05-02 05:14 UTC by cornel panceac
Modified: 2010-12-03 15:12 UTC (History)
1 user (show)

Clone Of:
Last Closed: 2010-12-03 15:12:28 UTC

Attachments (Terms of Use)
File: backtrace (119.88 KB, text/plain)
2010-05-02 05:14 UTC, cornel panceac
no flags Details

Description cornel panceac 2010-05-02 05:14:40 UTC
abrt 1.0.9 detected a crash.

architecture: i686
Attached file: backtrace
cmdline: /usr/bin/python /usr/bin/deluged --port=58846 --config=/home/guzu/.config/deluge
component: deluge
executable: /usr/bin/python
global_uuid: 6bee6560c04e8af8e8e1c37e4853d37766b4c443
package: deluge-1.1.9-3.fc12
rating: 4
reason: Process /usr/bin/python was killed by signal 11 (SIGSEGV)
release: Fedora release 12 (Constantine)

just started deluge ...

$ deluge
/usr/lib/python2.6/site-packages/deluge/ui/gtkui/statusbar.py:109: DeprecationWarning: Use the new widget gtk.Tooltip
  self.tooltips = gtk.Tooltips()
/usr/lib/python2.6/site-packages/deluge/ui/gtkui/statusbar.py:229: DeprecationWarning: Use the new widget gtk.Tooltip
  self.tooltips.set_tip(item.get_eventbox(), tooltip)
/usr/lib/python2.6/site-packages/deluge/ui/gtkui/statusbar.py:175: DeprecationWarning: Use the new widget gtk.Tooltip
  self.tooltips.set_tip(self.dht_item.get_eventbox(), "DHT Nodes")
/usr/lib/python2.6/site-packages/deluge/ui/tracker_icons.py:70: DeprecationWarning: BaseException.message has been deprecated as of Python 2.6
  log.debug("%s %s %s" % (url, e, e.message))
[ERROR   ] 08:08:31 client:158 Socket or XMLRPC error: <ProtocolError for localclient:4579fbb734c9d7a06b7edf0035acea12b8c01fb1@ -1 >

How to reproduce
1.unable to reporduce. seems to appear randomly. 

Comment 1 cornel panceac 2010-05-02 05:14:44 UTC
Created attachment 410763 [details]
File: backtrace

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

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 12'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 12 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 2010-12-03 15:12:28 UTC
Fedora 12 changed to end-of-life (EOL) status on 2010-12-02. Fedora 12 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.