Bug 592499 - [abrt] crash in deluge-1.2.0-1.fc13: task.py:91:stop:AssertionError: Tried to stop a LoopingCall that was not running.
Summary: [abrt] crash in deluge-1.2.0-1.fc13: task.py:91:stop:AssertionError: Tried to...
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Fedora
Classification: Fedora
Component: deluge
Version: 13
Hardware: x86_64
OS: Linux
low
medium
Target Milestone: ---
Assignee: Rahul Sundaram
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard: abrt_hash:48a39868
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2010-05-15 00:58 UTC by DELETE ME PLZ!!!
Modified: 2011-06-27 16:22 UTC (History)
10 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2011-06-27 16:22:40 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)
File: backtrace (1.48 KB, text/plain)
2010-05-15 00:58 UTC, DELETE ME PLZ!!!
no flags Details

Description DELETE ME PLZ!!! 2010-05-15 00:58:42 UTC
abrt 1.1.0 detected a crash.

architecture: x86_64
cmdline: /usr/bin/python /usr/bin/deluge-gtk
component: deluge
executable: /usr/bin/deluge-gtk
kernel: 2.6.33.3-85.fc13.x86_64
package: deluge-1.2.0-1.fc13
reason: task.py:91:stop:AssertionError: Tried to stop a LoopingCall that was not running.
release: Fedora release 13 (Goddard)

backtrace
-----
task.py:91:stop:AssertionError: Tried to stop a LoopingCall that was not running.

Traceback (most recent call last):
  File "/usr/bin/deluge-gtk", line 9, in <module>
    load_entry_point('deluge==1.2.0', 'console_scripts', 'deluge-gtk')()
  File "/usr/lib/python2.6/site-packages/deluge/ui/gtkui/gtkui.py", line 107, in start
    Gtk().start()
  File "/usr/lib/python2.6/site-packages/deluge/ui/gtkui/gtkui.py", line 104, in start
    GtkUI(self.args)
  File "/usr/lib/python2.6/site-packages/deluge/ui/gtkui/gtkui.py", line 234, in __init__
    self.shutdown()
  File "/usr/lib/python2.6/site-packages/deluge/ui/gtkui/gtkui.py", line 240, in shutdown
    component.stop()
  File "/usr/lib/python2.6/site-packages/deluge/component.py", line 217, in stop
    _ComponentRegistry.stop()
  File "/usr/lib/python2.6/site-packages/deluge/component.py", line 143, in stop
    self.stop_component(component)
  File "/usr/lib/python2.6/site-packages/deluge/component.py", line 149, in stop_component
    self.components[component].stop()
  File "/usr/lib/python2.6/site-packages/deluge/core/preferencesmanager.py", line 232, in stop
    self.new_release_timer.stop()
  File "/usr/lib64/python2.6/site-packages/twisted/internet/task.py", line 91, in stop
    assert self.running, ("Tried to stop a LoopingCall that was "
AssertionError: Tried to stop a LoopingCall that was not running.

Local variables in innermost frame:
self: LoopingCall<259200>(PreferencesManager._on_new_release_check, *('new_release_check', True), **{})

Comment 1 DELETE ME PLZ!!! 2010-05-15 00:58:44 UTC
Created attachment 414195 [details]
File: backtrace

Comment 2 Valentin Brémond 2010-06-16 11:56:39 UTC
Package: deluge-1.2.0-1.fc13
Architecture: x86_64
OS Release: Fedora release 13 (Goddard)


How to reproduce
-----
1.Install a fresh Fedora 13 release
2.Open Deluge
3.


Comment
-----
This bug happenned only at the first launch of Deluge on a fresh install of Fedora 13.

Comment 3 C Johnson 2010-08-01 10:27:47 UTC
Package: deluge-1.2.3-2.fc13
Architecture: x86_64
OS Release: Fedora release 13 (Goddard)


How to reproduce
-----
1.Deluge had failed to auto add torrents so tried to restart daemon and received crash message
2.
3.

Comment 4 Igor Katalnikov 2010-09-07 16:39:08 UTC
Package: deluge-1.2.3-2.fc13
Architecture: x86_64
OS Release: Fedora release 13 (Goddard)


How to reproduce
-----
1. Check for new version in preferences out and applied.
2. Stil crash while closing Deluge.
3. Sorrow for this fine software.

Comment 5 afgonzaga 2010-10-12 16:25:49 UTC
Package: deluge-1.2.3-2.fc13
Architecture: x86_64
OS Release: Fedora release 13 (Goddard)


How to reproduce
-----
1.  Open Deluge
2.  Close Deluge
3.

Comment 6 Fedora Admin XMLRPC Client 2011-03-16 08:13:08 UTC
This package has changed ownership in the Fedora Package Database.  Reassigning to the new owner of this component.

Comment 7 Bug Zapper 2011-06-02 14:00:50 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: 
http://fedoraproject.org/wiki/BugZappers/HouseKeeping

Comment 8 Bug Zapper 2011-06-27 16:22:40 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.