Deluge
It just happened to me aswell!
I'm going crazy. These files are nowhere. What the hell is happening to Deluge?
Now I can't even switch back do uTorrent!
Deluge Deleted All of My Torrents for No Reason
Re: Deluge Deleted All of My Torrents for No Reason
Please do not resurrect a 3 year old post with 'me too'.
What is the precise issue that you are seeing?
What is the precise issue that you are seeing?
Re: Deluge Deleted All of My Torrents for No Reason
Well... I was using uTorrent for a long long time and decided to give Deluge a second try (had used it a long time ago).
I downloaded and installed it normally. When I used the "auto-add" feature to quickly list all my torrent files, it listed them all and deleted them.
Plus, some torrent folders (with the actual files I downloaded in it) got totally deleted aswell.
And now i'm redownloading 224 full torrents (lost more than 1,3TB).
The .torrent files are lost and now can't switch back to uTorrent.
Where are my .torrent files and my full torrent's archives?
I downloaded and installed it normally. When I used the "auto-add" feature to quickly list all my torrent files, it listed them all and deleted them.
Plus, some torrent folders (with the actual files I downloaded in it) got totally deleted aswell.
And now i'm redownloading 224 full torrents (lost more than 1,3TB).
The .torrent files are lost and now can't switch back to uTorrent.
Where are my .torrent files and my full torrent's archives?
Re: Deluge Deleted All of My Torrents for No Reason
What version of Deluge?
The .torrent files will be in your config state folder, renamed to <infohash>.torrent.
As for the torrent data it sound like the folders have been overwritten but not sure how that has happened unless you had maybe renamed the files in utorrent?
The .torrent files will be in your config state folder, renamed to <infohash>.torrent.
As for the torrent data it sound like the folders have been overwritten but not sure how that has happened unless you had maybe renamed the files in utorrent?
Re: Deluge Deleted All of My Torrents for No Reason
It's Deluge 1.3.5.
I never rename any torrents. I only label them with the label feature on uTorrent (which doesn't change the torrent's data).
By the way, where can I find that folder?
I never rename any torrents. I only label them with the label feature on uTorrent (which doesn't change the torrent's data).
By the way, where can I find that folder?
Last edited by fabio on Sun Dec 09, 2012 2:12 am, edited 1 time in total.
Re: Deluge Deleted All of My Torrents for No Reason
I'm redownloading every .torrent file and going back to uTorrent.
Older versions of Deluge seemed to work better.
Anyway, no more Deluge for me.
Thanks for the help.
Older versions of Deluge seemed to work better.
Anyway, no more Deluge for me.
Thanks for the help.
-
dandy
Re: Deluge Deleted All of My Torrents for No Reason
I think I can clarify this behaviour a bit.
This has happened to me several times now and it always happens when I inadvertantly start the deluge daemon (deluged) via command line from within a working directory that no longer exists.
For example; On a Linux box, I have a directory, let's say it is ~/torrents/foo
In a shell I change to that directory;
Then I go off and do other stuff, including using the deluge-gtk client to delete the foo torrent including all files. Then I close the daemon when exiting by using the "quit and shutdown daemon" option.
Time passes;
Eventually, I go back to my shell session so that I can start deluged again, and you will note that it is still sitting in /home/me/torrents/foo which no longer exists. ie: My prompt looks like this;
me@ubuntu:/home/me/torrents/foo$
I then start the deluged daemon by typing 'deluged' like so;
me@ubuntu:/home/me/torrents/foo$ deluged
This generates a bunch of python errors and when I reopen deluge-gtk there are no torrents running. Restarting deluged, deluge-gtk, or even the whole PC achieves nothing.
I can look in ~/.config/deluge/state and see torrent files there, but only for those torrents that had started downloading. Torrents that were queued at 0.0% are not there. The completed and partially completed torrrent data still exists and after "checking files" is done they will continue from where they were. But any queued torrents that had not been started will be lost and you will need to remember what they were and re-add them again.
That is a pain though, so lately I have taken to queuing all newly added torrents to the top for a few minutes so they begin downloading and thereby create the appropriate file in the state directory just as a precaution.
So, how does one go about filing a bug for this?
This has happened to me several times now and it always happens when I inadvertantly start the deluge daemon (deluged) via command line from within a working directory that no longer exists.
For example; On a Linux box, I have a directory, let's say it is ~/torrents/foo
In a shell I change to that directory;
Then I go off and do other stuff, including using the deluge-gtk client to delete the foo torrent including all files. Then I close the daemon when exiting by using the "quit and shutdown daemon" option.
Time passes;
Eventually, I go back to my shell session so that I can start deluged again, and you will note that it is still sitting in /home/me/torrents/foo which no longer exists. ie: My prompt looks like this;
me@ubuntu:/home/me/torrents/foo$
I then start the deluged daemon by typing 'deluged' like so;
me@ubuntu:/home/me/torrents/foo$ deluged
This generates a bunch of python errors and when I reopen deluge-gtk there are no torrents running. Restarting deluged, deluge-gtk, or even the whole PC achieves nothing.
I can look in ~/.config/deluge/state and see torrent files there, but only for those torrents that had started downloading. Torrents that were queued at 0.0% are not there. The completed and partially completed torrrent data still exists and after "checking files" is done they will continue from where they were. But any queued torrents that had not been started will be lost and you will need to remember what they were and re-add them again.
That is a pain though, so lately I have taken to queuing all newly added torrents to the top for a few minutes so they begin downloading and thereby create the appropriate file in the state directory just as a precaution.
So, how does one go about filing a bug for this?