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 348741 - connect() to news server blocks UI until time-out
connect() to news server blocks UI until time-out
Status: RESOLVED DUPLICATE of bug 347632
Product: Pan
Classification: Other
Component: general
pre-1.0 betas
Other All
: Normal major
: ---
Assigned To: Charles Kerr
Pan QA Team
Depends on:
Blocks:
 
 
Reported: 2006-07-26 07:17 UTC by freggy1
Modified: 2006-07-26 17:07 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description freggy1 2006-07-26 07:17:01 UTC
Please describe the problem:
When a news server is not responding for example it's down or you don't have access to it, this completely blocks the pan UI until it time-outs when selecting a group to view its messages. strace shows it is hanging on this:
connect(6, {sa_family=AF_INET, sin_port=htons(119), sin_addr=inet_addr("81.171.66.10")}, 16


Steps to reproduce:
1. Add 81.171.66.10 as your news server
2. Start pan and click on one of your subscribed groups (accessible via another news server you have configured)


Actual results:
The pan UI completely hangs until the connect() time-outs, even when the group is available on the other news server so no connecto() to this news server would even be necessary.

Expected results:
Being able to immediately continue to use pan, view all cached articles, and view all new articles on the still available news servers.

Does this happen every time?


Other information:
Comment 1 Christophe Lambin 2006-07-26 16:59:50 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 348445 ***
Comment 2 Christophe Lambin 2006-07-26 17:07:01 UTC
Oops: closed this against the wrong bugreport.


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