Red Hat Bugzilla – Bug 173645
Gaim UI freeze while connecting to MSN via a non-responsive http proxy.
Last modified: 2008-02-12 20:00:49 EST
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.8b5) Gecko/20051021 Flock/0.4 Firefox/1.0+
Description of problem:
When using this proxy: 220.127.116.11:3128 as MSN proxy via HTTP method, Gaim UI freeze. However, CTRL-C in console make it quit normally.
Setting up localhost:25000 as proxy, makes gaim behave normally, with no service running on that port.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. Set up this proxy on msn options: 18.104.22.168:3128, HTTP method.
2. Try to connect to msn.
Actual Results: Gaim UI Freezes without connecting.
Expected Results: Connecting progress window should appear.
I managed to reproduce this every time.
strace output follows, note that the line
write(13, "POST http://gateway.messenger.ho"..., 374) = -1 EAGAIN (Resource temporarily unavailable)
repeats million times, I edited them out.
Ethereal capture follows up. Filter "host 22.214.171.124"
Created attachment 121245 [details]
strace -o log -ff gaim -n -d
Output edited, line
write(13, "POST http://gateway.messenger.ho"..., 374) = -1 EAGAIN (Resource
was repeated million times.
Created attachment 121247 [details]
strace -o log -ff gaim -n -d (fork trace)
Created attachment 121248 [details]
strace -o log -ff gaim -n -d (second fork trace)
Created attachment 121250 [details]
ethereal capture file
Created attachment 121251 [details]
ethereal capture file
(In reply to comment #0)
> Setting up localhost:25000 as proxy, makes gaim behave normally, with no
service running on that port.
ie.: gaim fails to connect. ;)
I'm going to bet that the non-blocking stuff we have for 2.0.0 (some of it is in
beta3) will help significantly with this bug.
Don't try beta3 though, because the same non-blocking changes also broke MSN's
http method, so it still won't work.
Fedora Core 3 is now maintained by the Fedora Legacy project for security
updates only. If this problem is a security issue, please reopen and
reassign to the Fedora Legacy product. If it is not a security issue and
hasn't been resolved in the current FC5 updates or in the FC6 test
release, reopen and change the version to match.
Fedora Core 3 is not maintained anymore.
Setting status to "INSUFFICIENT_DATA". If you can reproduce this bug in the
current Fedora release, please reopen this bug and assign it to the
corresponding Fedora version.