Bug 26871 - Deluge 2 does not keep torrent data when upgrading from Mageia 7 => 8
Summary: Deluge 2 does not keep torrent data when upgrading from Mageia 7 => 8
Status: RESOLVED FIXED
Alias: None
Product: Mageia
Classification: Unclassified
Component: RPM Packages (show other bugs)
Version: Cauldron
Hardware: All Linux
Priority: Normal normal
Target Milestone: ---
Assignee: David GEIGER
QA Contact:
URL: https://forum.deluge-torrent.org/view...
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2020-06-28 17:43 CEST by Marcel Pol
Modified: 2020-07-04 08:57 CEST (History)
0 users

See Also:
Source RPM: deluge-2.0.3-3.mga8.src.rpm
CVE:
Status comment:

Attachments
Patch for deluge 2.0.3 to fix loading state with non-ascii characters. (3.44 KB, patch)
2020-06-30 12:58 CEST, Marcel Pol 		Details | Diff
View All Add an attachment (proposed patch, testcase, etc.)

Description Marcel Pol 2020-06-28 17:43:02 CEST 
Description of problem:
When using Mageia 7.1 and deluge-1.3.15-6.mga7, create a torrent. Then upgrade to Mageia 8 and reboot. Deluge will have forgotten the torrents and start as if there was no state in ~/.local/deluge/

Removing ~/.local/deluge and starting again, it does create new data, it is only a problem when upgrading from Mageia 7. It is said to be from non-asscii charaters in the state files.

Version-Release number of selected component (if applicable):
deluge-2.0.3-3.mga8.src.rpm

According to the deluge forum, there seem to be bugfixes in current git for 2.0.4. If that version would be included in Mageia 8, people will not lose their torrent state after upgrading from mga7 => mga8.
Forum link:
https://forum.deluge-torrent.org/viewtopic.php?f=7&t=55508
Comment 1 Marcel Pol 2020-06-30 12:21:54 CEST 
I tried to reproduce it in a VM and now it works for me. If someone else can give their experience, please do.

Installed Deluge in Mageia 7.1, added one torrent. That torrent was downloaded and only used for seeding.
Updated to Mageia 8 Alpha (cauldron). Rebooted and started Deluge. It shows that same torrent as seeding.

As the mentioned patch was about non-ascii characters, it might be that it only fails with some data and not with others.

I can imagine you might want to pick the needed patch instead of updating to a git version:
https://git.deluge-torrent.org/deluge/commit/?h=develop&id=23b3f144fce3424ae874d54a659cb7b8dd624ade
Comment 2 Marcel Pol 2020-06-30 12:58:57 CEST 
Created attachment 11726 [details]
Patch for deluge 2.0.3 to fix loading state with non-ascii characters.

Patch for deluge 2.0.3 to fix loading state with non-ascii characters, taken from git.

It builds for me as %Patch1. 

I tried testing with a chinese torrent, but that also keeps state fine.
I am not sure about how to reproduce it correctly.
Comment 3 Lewis Smith 2020-06-30 20:44:47 CEST 
Thank you for the report and research about it, your various trials.

This looks best for you, David. You may want to class the bug Unconfirmed.

Assignee: bugsquad => geiger.david68210

Comment 4 David GEIGER 2020-07-02 08:26:01 CEST 
Should be fixed with deluge-2.0.3-4.mga8 backporting some upstream fixes!
Comment 5 David GEIGER 2020-07-04 08:57:16 CEST 
Closing as fixed!

Resolution: (none) => FIXED
Status: NEW => RESOLVED
Note You need to log in before you can comment on or make changes to this bug.