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 353486 - server connection(s) screw up after pan's been open a while
server connection(s) screw up after pan's been open a while
Status: RESOLVED FIXED
Product: Pan
Classification: Other
Component: general
pre-1.0 betas
Other All
: Normal normal
: 1.0
Assigned To: Charles Kerr
Pan QA Team
: 355142 (view as bug list)
Depends on:
Blocks:
 
 
Reported: 2006-08-29 23:22 UTC by Simon Morgan
Modified: 2006-09-10 06:01 UTC
See Also:
GNOME target: ---
GNOME version: ---


Description Simon Morgan 2006-08-29 23:22:49 UTC 
Please describe the problem:
When pan has been open a while with no activity and I try to do something that uses the network connection (e.g. by fetching a post or new headers), it fails. Although the box in the bottom left indicates pan has established a connection (it displays 1 @ <speed>), hovering my mouse over it displays "-1 idle, 0 active" (the minus isn't a typo) and the action never seems to complete.

I have 2 news server profiles, one for my ISP and one for EasyNews. My ISP's server doesn't require authentication whereas EasyNews does. My ISP's server is set to primary and EasyNews to fallback.

I'm using pan 0.110.

Steps to reproduce:
1. Start pan.
2. Use it for a while.
3. Leave it running idle for an extended period of time.


Actual results:


Expected results:


Does this happen every time?


Other information:
Comment 1 Simon Morgan 2006-08-30 18:39:51 UTC 
0.109 does not seem to have this problem.
Comment 2 Kenneth Haley 2006-08-31 09:25:14 UTC 
I've jsut seen a simialr problem with .110. When the connection was lost during xover pan reported -1 idle & 1 active connections.
Comment 3 Kenneth Haley 2006-09-06 06:35:12 UTC 
I've just found what looks like the cause of the -1 idle, 1 active problem.  NNTPPool does not decrement the active counter when a socket is closed with an error.

nntp-pool.cc: 
NNTP_Pool::check_in
line 96
should be
    --_active_count;
    if (is_ok) {
Comment 4 Charles Kerr 2006-09-06 19:26:00 UTC 
Great catch.  Thanks!
Comment 5 Charles Kerr 2006-09-07 15:46:30 UTC 
*** Bug 354779 has been marked as a duplicate of this bug. ***
Comment 6 Charles Kerr 2006-09-10 06:01:46 UTC 
*** Bug 355142 has been marked as a duplicate of this bug. ***