After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 118273 - Pan stops downloading queued tasks
Pan stops downloading queued tasks
Status: RESOLVED DUPLICATE of bug 113405
Product: Pan
Classification: Other
Component: general
pre-0.14.1 betas
Other Linux
: Normal normal
: ---
Assigned To: Charles Kerr
Pan QA Team
Depends on:
Blocks:
 
 
Reported: 2003-07-25 08:38 UTC by hjohn
Modified: 2006-06-18 05:03 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description hjohn 2003-07-25 08:38:38 UTC
I queue up about 50 tasks, and let PAN handle the downloading.  Since I've 
switched from 0.13.something to 0.14.0.91 (2 days ago) it has happened 3 
or 4 times in 2 days that PAN will download a few tasks, and download a 
lot of the tasks partially (leaving them at varying percentages 10-90%) in 
the Task Manager window.  It then just stops downloading those tasks 
(there's like 30-40 tasks left, but Pan says there are no connections) -- 
restarting them doesn't work (but that's probably been addressed in 
0.14.0.92 if I interpreted the changelog correctly), so the only option 
for me is to quit pan, restart it and then select Resume Tasks.  It then 
continues as normal, but may exhibit the same problem after a while.

I suspect it may be my newsserver (it is limited to 3 connections, same as 
I have PAN set), and it might be returning errors sometimes.  Still, PAN 
should retry any failed / partially downloaded tasks.  The 0.13 version 
didn't seem to have as hard a time dealing with failed tasks, although it 
would leave one or 2 tasks out of 100 sometimes, which I had to restart 
manually (it retried things a lot).

I can probably reproduce it easily (it just takes a while to happen).  
I've tried running pan with -debug, but that didn't seem to produce 
anything meaningful after it stopped downloading.

I will be trying to narrow the problem down further (limiting connections 
to 1 or 2 for example) and anything I see suggested here.
Comment 1 Charles Kerr 2003-07-25 15:53:26 UTC
Failed-due-to-network-error tasks should restart themselves
automatically, and failed-due-to-502-errors-or-whatever
tasks should be able to be restarted manually, in 0.14.0.92. :)

*** This bug has been marked as a duplicate of 113405 ***