Bug 585046 - [abrt] crash in deluge-1.2.0-1.fc13: addtorrentdialog.py:448:set_default_options:KeyError: 'download_location'
Summary: [abrt] crash in deluge-1.2.0-1.fc13: addtorrentdialog.py:448:set_default_opti...
Alias: None
Product: Fedora
Classification: Fedora
Component: deluge
Version: 13
Hardware: x86_64
OS: Linux
Target Milestone: ---
Assignee: Rahul Sundaram
QA Contact: Fedora Extras Quality Assurance
Whiteboard: abrt_hash:f6394a0a
Depends On:
TreeView+ depends on / blocked
Reported: 2010-04-23 01:08 UTC by Aron Parsons
Modified: 2011-06-27 15:48 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Last Closed: 2011-06-27 15:48:54 UTC
Type: ---

Attachments (Terms of Use)
File: backtrace (725 bytes, text/plain)
2010-04-23 01:08 UTC, Aron Parsons
no flags Details

Description Aron Parsons 2010-04-23 01:08:10 UTC
abrt 1.0.9 detected a crash.

architecture: x86_64
cmdline: /usr/bin/python /usr/bin/deluge-gtk /tmp/South.Park.S14E06.720p.HDTV.x264-IMMERSE.torrent
comment: Deluge daemon is running on another system.  The crash happens on the client running the GTK frontend.
component: deluge
executable: /usr/bin/deluge-gtk
package: deluge-1.2.0-1.fc13
reason: addtorrentdialog.py:448:set_default_options:KeyError: 'download_location'
release: Fedora release 13 (Goddard)

addtorrentdialog.py:448:set_default_options:KeyError: 'download_location'

Traceback (most recent call last):
  File "/usr/lib/python2.6/site-packages/deluge/ui/gtkui/addtorrentdialog.py", line 278, in _on_torrent_changed
    self.update_torrent_options(model.get_value(row, 0))
  File "/usr/lib/python2.6/site-packages/deluge/ui/gtkui/addtorrentdialog.py", line 348, in update_torrent_options
  File "/usr/lib/python2.6/site-packages/deluge/ui/gtkui/addtorrentdialog.py", line 448, in set_default_options
KeyError: 'download_location'

Local variables in innermost frame:
self: <deluge.ui.gtkui.addtorrentdialog.AddTorrentDialog object at 0x1689b10>

How to reproduce
1. Download a torrent in Firefox
2. Have it automatically load in Deluge

Comment 1 Aron Parsons 2010-04-23 01:08:12 UTC
Created attachment 408477 [details]
File: backtrace

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

Comment 3 Bug Zapper 2011-06-02 14:58:21 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 15:48:54 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.