FS#24626 - [chromium] 12 intermittent proxy connection problems

Attached to Project: Arch Linux
Opened by Olivier (litemotiv) - Wednesday, 08 June 2011, 14:53 GMT
Last edited by Ionut Biru (wonder) - Saturday, 18 June 2011, 16:24 GMT
Task Type Bug Report
Category Packages: Extra
Status Closed
Assigned To Evangelos Foutras (foutrelis)
Architecture All
Severity Medium
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

Chromium 12.0.742.91-1, started with /usr/bin/chromium --proxy-server=127.0.0.1:8118, has intermittent problems connecting to privoxy ("cannot connect to proxy"). The only solution is to manually restart privoxy, after which chromium resumes working temporarily. After a certain time, sometimes after opening a new tab, the connection problem reoccurs, and privoxy needs to be restarted again.

Steps tried to fix:

- Remove chromium profile/settings/cache directories
- Reinstall chromium
This task depends upon

Closed by  Ionut Biru (wonder)
Saturday, 18 June 2011, 16:24 GMT
Reason for closing:  Fixed
Comment by Evangelos Foutras (foutrelis) - Sunday, 12 June 2011, 20:18 GMT
Can other browsers connect to Privoxy when this happens?
Comment by Olivier (litemotiv) - Monday, 13 June 2011, 08:58 GMT
I will install Firefox and do some more testing. I haven't noticed a clear pattern yet on when this occurs, but it has been happening right after Chromium was updated to 12.0.742.91. I agree that it's likely not an Arch packaging issue, i also created this ticket for other users to be aware of the problem and follow progress. If you prefer this doesn't take place on Flyspray but rather on the forums, you may close the ticket.

The upgrade log, shows only three packages updated when this started:

[2011-06-08 11:33] upgraded avahi (0.6.30-2 -> 0.6.30-3)
[2011-06-08 11:33] upgraded chromium (11.0.696.77-1 -> 12.0.742.91-1)
[2011-06-08 11:33] upgraded nvidia (270.41.19-2 -> 270.41.19-3)

Privoxy was last updated on 05-11:

[2011-05-11 10:44] upgraded privoxy (3.0.17-1 -> 3.0.17-2)

So that shouldn't be the cause.
Comment by Olivier (litemotiv) - Wednesday, 15 June 2011, 13:35 GMT
I am sorry/happy to say, that since the last chromium update to 12.0.742.100-1, i haven't seen this issue occurring. I could wait for another 24 hours and see if anything happens, then report back here. If you feel however that this is enough reason already to close it right now, i'm fine with that too.
Comment by Evangelos Foutras (foutrelis) - Wednesday, 15 June 2011, 16:58 GMT
Let's wait a day or two before closing this bug, so we can be certain that the issue is solved.

Loading...