I load up Quasar with a few (last number was 15) torrents, let 'er rip. VPN goes down, all stops. I shutdown Kodi to utilize resources to troubleshoot loss of VPN connectivity. Upon restarting Kodi, Quasar has retained and resumes only 6 torrents. All others are simply gone, but still leaving enormous file lint in the download directory, that then must be deleted without accidentally deleting things that are still in progress. NOT OKAY.
If I close it with 15 torrents in progress, it should RESUME WITH 15 TORRENTS RESUMED. I don't know of too many torrent clients that don't... In fact, only this one.
If it cannot due to file corruption (due to bad shutdown, since Kodi NEVER shuts down gracefully), it should verify data on torrents before resume, like EVERY OTHER TORRENT CLIENT DOES.
Current Behavior
Um, really?
## Your Environment
Version used:
Present environment =
uname -a = Linux parrot 4.14.0-parrot13-686-pae #1 SMP Parrot 4.14.13-1parrot13 (2018-01-21) i686 GNU/Linux
cat /proc/cpuinfo = AMD E1-2500 APU with Radeon(TM) HD Graphics
free -h = total used free shared buff/cache available
Mem: 3.2G 2.3G 246M 66M 626M 475M
Swap: 4.0G 1.1G 2.9G
df -h = Filesystem Size Used Avail Use% Mounted on
udev 1.6G 0 1.6G 0% /dev
tmpfs 327M 27M 301M 8% /run
/dev/sda10 53G 26G 24G 52% /
tmpfs 1.6G 5.7M 1.6G 1% /dev/shm
tmpfs 5.0M 4.0K 5.0M 1% /run/lock
tmpfs 1.6G 0 1.6G 0% /sys/fs/cgroup
/dev/sda9 291G 226G 51G 82% /home
/dev/sda2 360M 187M 173M 52% /boot/efi
tmpfs 327M 32K 327M 1% /run/user/1000
Kodi = 5:17.6-dmo2 from deb-multimedia.org (and pulling this shows me that there's an update)
Quasar = 0.9.78
But, this has happened repeatedly since Quasar's intro 2ish years ago or more, on several different systems, thru several different versions of all involved (all OS' have been Debian-based, whether Ubuntu, Bodhi, Parrot, etc.)
placidities
commented
5 years ago
I load up Quasar with a few (last number was 15) torrents, let 'er rip. VPN goes down, all stops. I shutdown Kodi to utilize resources to troubleshoot loss of VPN connectivity. Upon restarting Kodi, Quasar has retained and resumes only 6 torrents. All others are simply gone, but still leaving enormous file lint in the download directory, that then must be deleted without accidentally deleting things that are still in progress. NOT OKAY.
Results of "cat kodi.old.log | grep ERROR" then cat that | grep quasar = https://pastebin.com/TtdgSiS8 Seemingly much more relevant are the results of the same for current log (post-restart) = https://pastebin.com/93NhhBJC
Expected Behavior
If I close it with 15 torrents in progress, it should RESUME WITH 15 TORRENTS RESUMED. I don't know of too many torrent clients that don't... In fact, only this one. If it cannot due to file corruption (due to bad shutdown, since Kodi NEVER shuts down gracefully), it should verify data on torrents before resume, like EVERY OTHER TORRENT CLIENT DOES.
Current Behavior
Um, really? ## Your EnvironmentBut, this has happened repeatedly since Quasar's intro 2ish years ago or more, on several different systems, thru several different versions of all involved (all OS' have been Debian-based, whether Ubuntu, Bodhi, Parrot, etc.)