You are not logged in.
vcap,
If you wouldn't mind posting your findings here it would be greatly appreciated;
i posted it to https://bugzilla.gnome.org/show_bug.cgi?id=631525 instead. since it seems that the proxy and the non-proxy cases are different problems (mine was without a proxy).
Offline
skottish wrote:vcap,
If you wouldn't mind posting your findings here it would be greatly appreciated;
i posted it to https://bugzilla.gnome.org/show_bug.cgi?id=631525 instead. since it seems that the proxy and the non-proxy cases are different problems (mine was without a proxy).
Thanks for that. It would seem that the newest libsoup suffers from a few regressions. The devs are responsive, so this is all helpful. I'm pleased to see a community growing around getting things in order.
>>..|..<<
As far as what I said before, I can't do anything at the moment with bisecting the git tree. My workstation kicked the bucket and my laptop is suffering from crappy performance with any browser. I don't spend much time with this machine, so that's a different story...
<<..|..>>
libsoup devs:
I very much appreciate the fact that this is important to you. My workstation will be up tomorrow and I intend to help any way that I can. Thank you.
Offline
I have to do a bisect once more when I find the time, bad ones are certainly bad but good ones could be bad because I don't have 100% reliable test case, even though I've tested those cases a dosen times before marking bisect as good/bad.
I have problems with libwebkit (100% cpu usage on font fallback determination) and I'm on to it also, but I have one laptop only and compiling libwebkit takes forever. I got to get myself a quad core workstation ASAP! January sounds like a good time for buying one
Offline
I have to do a bisect once more when I find the time, bad ones are certainly bad but good ones could be bad because I don't have 100% reliable test case, even though I've tested those cases a dosen times before marking bisect as good/bad.
Indeed, if it's anything like what i reported about, the bug won't trigger at will.
Offline
For those of you that are still looking for a solution after nine months of waiting, there's a patch posted on the bug report:
https://bugzilla.gnome.org/show_bug.cgi?id=631368
I have applied it locally just to see if it works and it does. I have no idea if there are any side effects, so I'm not willing to push anything out to the AUR.
Offline
I applied it to see if it fixed a minor issue I have with https sites, and while it doesn't fix my issue, it doesn't seem to break anything else that I've found yet.
Scott
Offline
The fix for the problem that I posted about here has been commited to libsoup's mainline branch. Of that I'm quite grateful for.
firecat53, keep working with them on your issue. There are people paying attention, so a gentle nudge every now and then could go a long way in making things right.
Offline