Custom Query (2449 matches)

Filters
 
Or
 
  
 
Columns

Show under each result:


Results (631 - 633 of 2449)

Ticket Resolution Summary Owner Reporter
#2329 Duplicate Deluge creates parent directories for output B-Con
Description

Problem

Deluge creates the necessary parent directories of it. However, it does not own the parent directory of the torrent output and thus should not manage it. Creating it is being overly helpful and the problems with auto-creating it include:

a) The parent directory may intentionally be missing

b) Deluge may create the directory with the wrong permissions

Steps to reproduce

1) Download torrent

2) Exit Deluge

3) Move said torrent and delete torrent's parent directory

4) Open Deluge

5) Deluge will create the parent directory and re-download the the torrent

Example

I had all torrents saved in a path like /storage/data/torrents/. (Eg: /storage/data/torrents/TORRENT_NAME.) /storage/data was a mountpoint for another filesystem. I quit Deluge, unmounted /storage/data, and rebooted. Deluge was set to auto-start on boot and it created /storage/data/torrents and then started to re-download everything. This both filled up the filesystem for /storage and caused undesired leeching.

Desired behavior

If the parent directory for a torrent is missing Deluge should not create it and instead fail to proceed.

#192 WorksForMe deluged 0.6 crashes with python error andar durand1@gmail.com
Description

Deluged doesn't seem to like starting at times. If I first turn the computer on, it seems to load the daemon ok. But if I shut the daemon down and then start it again, I get this python error:

[DEBUG   ] torrent:542 Attempting to save torrent file: heroes.torrent
[DEBUG   ] pluginmanager:147 run_post_session_load
Traceback (most recent call last):
  File "/usr/bin/deluged", line 7, in ?
    sys.exit(
  File "/usr/lib/python2.4/site-packages/deluge/main.py", line 101, in start_daemon
    Daemon(options, args)
  File "/usr/lib/python2.4/site-packages/deluge/core/daemon.py", line 44, in __init__
    self.core = Core(options.port).run()
  File "/usr/lib/python2.4/site-packages/deluge/core/core.py", line 252, in run
    component.start()
  File "/usr/lib/python2.4/site-packages/deluge/component.py", line 194, in start
    _ComponentRegistry.start()
  File "/usr/lib/python2.4/site-packages/deluge/component.py", line 114, in start
    self.start_component(component)
  File "/usr/lib/python2.4/site-packages/deluge/component.py", line 121, in start_component
    self.start_component(depend)
  File "/usr/lib/python2.4/site-packages/deluge/component.py", line 126, in start_component
    self.components[name].start()
  File "/usr/lib/python2.4/site-packages/deluge/core/torrentmanager.py", line 150, in start
    self.load_state()
  File "/usr/lib/python2.4/site-packages/deluge/core/torrentmanager.py", line 532, in load_state
    self.torrents[torrent_id].handle.resume()
KeyError: 'dcd81b918cfc6ddfd150025b7271f3c8bb4446b4'

This is when clicking on start daemon in the webui but the same happens with the gtkui. I've got deluge 0.6 running fine on my ubuntu hardy computer but not on my gentoo computer. Is it because I'm using python-2.4 on gentoo?

#765 WorksForMe deluged 1.1.1 fails to start on gentoo andar marcelocoelho@gmail.com
Description

After updating from 1.0.4 to 1.1.1, deluged doesn't start. If I remove the --background option from the start-stop-daemon I get the following error:

 terminate called after throwing an instance of 'boost::python::error_already_set'

I change the default home location to a different location. This also happens with 1.1.0

dev-libs/boost 1.35.0-r2 dev-util/boost-build 1.35.0-r1

Batch Modify
Note: See TracBatchModify for help on using batch modify.
Note: See TracQuery for help on using queries.