Opened 10 years ago

Closed 9 years ago

#1907 closed bug (Fixed)

deluged sometimes not saving torrent state on exit

Reported by: B2BF Owned by:
Priority: major Milestone: 1.3.4
Component: Core Version: 1.3.2
Keywords: download order, queue numbers Cc:

Description

I've got Deluge 1.3.2 on Ubuntu 10.04. And I noticed, that Deluge mixes download order on start or exit (so, the first torrent to be download before exit can become the 14th after the next start). I mean the queue numbers are changing.

http://forum.deluge-torrent.org/viewtopic.php?f=7&t=37241

Change History (6)

comment:1 Changed 10 years ago by Cas

  • Milestone changed from Future to 1.3.4

comment:2 Changed 10 years ago by B2BF

You asked: "How are you exiting Deluge? Is it closing cleanly?"

To exit Deluge I just click with LMB at Deluge icon on a taskbar (where the date and the time are) and then choose "Exit" from the menu. Sometimes it does, sometime it doesn't (especially, if it was running for several days). Anyway, the queue numbers are changing.

How can I find out if it is closing cleanly? Any log?

comment:3 Changed 10 years ago by Cas

If it does not close properly then it will not save an updated state file thus makes sense for the order to be different.

The logs will show if the state file was saved successfully:

http://dev.deluge-torrent.org/wiki/Faq#EnableDelugeLogging

comment:4 follow-up: Changed 9 years ago by Ryan8

I have the same issue. Deluge prints to stdout "[WARNING ] 01:37:56 core:161 Failed to save lt state: 'session' object has no attribute 'state'"

comment:5 in reply to: ↑ 4 Changed 9 years ago by Cas

  • Milestone changed from 1.3.4 to 1.3.x
  • Summary changed from Deluge 1.3.2 mixes download order of torrents on start or exit... to deluged sometimes not saving torrent state on exit

Replying to Ryan8:

I have the same issue. Deluge prints to stdout "[WARNING ] 01:37:56 core:161 Failed to save lt state: 'session' object has no attribute 'state'"

I'm afraid that warning is irrelevant to the issue. It will require more debugging to determine exactly why it fails to save state file but I have seen the issue occur.

comment:6 Changed 9 years ago by Cas

  • Milestone changed from 1.3.x to 1.3.4
  • Resolution set to fixed
  • Status changed from new to closed

A fix was applied to 1.3-stable that should sort this issue: 0676aaf91

Reopen and update if still facing issues.

Note: See TracTickets for help on using tickets.