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 362268 - Win2K Dial Up Failure, on reconnect Pan does not automatically restart tasks
Win2K Dial Up Failure, on reconnect Pan does not automatically restart tasks
Status: RESOLVED DUPLICATE of bug 125997
Product: Pan
Classification: Other
Component: general
pre-1.0 betas
Other All
: Normal normal
: ---
Assigned To: Charles Kerr
Pan QA Team
Depends on:
Blocks:
 
 
Reported: 2006-10-15 02:23 UTC by Ian Anderson
Modified: 2006-10-18 18:21 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description Ian Anderson 2006-10-15 02:23:13 UTC
Please describe the problem:
When dialup fails, and automatically reconnects
on Win2K, Pan does not automatically restart
tasks.
I noted the behavior in both Pan versions 0.115, and 0.116.
Automatic reconnection, and restarting of tasks works
in Pan version 0.14.2.
The behavior is reproducible by manually 
disconnecting the dialup modem, and then 
reconnecting.
In version 0.14.2 it appears that Pan would
log a socket error, on a modem disconnect,
and then continually check the network interface
until reconnected, then Pan would reconnect to 
the news server and restart the queued tasks.
Versions 0.115, and 0.116, both report a socket
error, but no other messages.


Steps to reproduce:
1. Disconnect the Modem Connection in Win2K
2. Redial, and reconnect
3. 


Actual results:
Pan fails to automatically restart tasks

Expected results:
Pan would automatically detect the network interface as being back online, reconnect to the newsserver, and restart the queued tasks

Does this happen every time?
Yes

Other information:
Comment 1 Charles Kerr 2006-10-18 18:21:32 UTC
Thanks for the bug report. This particular bug has already been reported into our bug tracking system, but please feel free to report any further bugs you find.


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