till valid in Ubuntu 16.04.1 and Firefox 49.0+build4-0ubuntu0.16.04.1
How to reproduce (set some invalid host and port
gsettings set org.gnome.system.proxy mode 'manual'
gsettings set org.gnome.system.proxy.http host 'nonexistinghost'
gsettings set org.gnome.system.proxy.http port
gsettings
(In reply to Henrik Skupin (:whimboo) from comment #25)
>
> So would this be doable as a browser chrome test?
you can probably write an xpcshell test that sets some http proxy
address along with a PROXYCONFIG_MANUAL setting and then test the
results of a nsIProtocolProxyService.asyncResolve invoca
*** Bug 886973 has been marked as a duplicate of this bug. ***
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to firefox in Ubuntu.
https://bugs.launchpad.net/bugs/1194841
Title:
Firefox 22 uses stale manual proxy settings when configure
** Changed in: firefox (Ubuntu)
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to firefox in Ubuntu.
https://bugs.launchpad.net/bugs/1194841
Title:
Firefox 22 uses stale manual proxy settings
This bug was fixed in the package firefox - 22.0+build2-0ubuntu0.13.04.2
---
firefox (22.0+build2-0ubuntu0.13.04.2) raring-security; urgency=low
* Fix LP: #1194841 - Firefox 22 uses stale manual proxy settings when
configured to use system proxy settings, and system proxy settin
This bug was fixed in the package firefox - 22.0+build2-0ubuntu0.12.04.2
---
firefox (22.0+build2-0ubuntu0.12.04.2) precise-security; urgency=low
* Fix LP: #1194841 - Firefox 22 uses stale manual proxy settings when
configured to use system proxy settings, and system proxy setti
This bug was fixed in the package firefox - 22.0+build2-0ubuntu0.12.10.2
---
firefox (22.0+build2-0ubuntu0.12.10.2) quantal-security; urgency=low
* Fix LP: #1194841 - Firefox 22 uses stale manual proxy settings when
configured to use system proxy settings, and system proxy setti
*** Bug 888626 has been marked as a duplicate of this bug. ***
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to firefox in Ubuntu.
https://bugs.launchpad.net/bugs/1194841
Title:
Firefox 22 uses stale manual proxy settings when configure
(In reply to Gary Houston from comment #36)
> One thing puzzles me: why does google.com still work when a broken
> manual proxy is configured?
probly using ssl and that either takes a slightly different code path or
your old stale proxy config didn't cover that.
--
You received this bug notifica
Patrick, need-info is still valid. You didn't answer my question from
comment 35. I hope you will do it at some point! Thanks.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to firefox in Ubuntu.
https://bugs.launchpad.net/bugs/1194841
Tit
Yeah, ssl, and my proxy was http only. Thanks.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to firefox in Ubuntu.
https://bugs.launchpad.net/bugs/1194841
Title:
Firefox 22 uses stale manual proxy settings when configured to use
syste
(In reply to Mamoru TASAKA from comment #40)
> Step to reproduce:
>
> * Launch with firefox -ProfileManager , create new profile, and launch
> firefox with that (new) profile
> * Go Preferences -> Advanced -> Network -> Connection -> Settings
> * Once choose "Manual proxy configuration", set ran
Step to reproduce:
* Launch with firefox -ProfileManager , create new profile, and launch
firefox with that (new) profile
* Go Preferences -> Advanced -> Network -> Connection -> Settings
* Once choose "Manual proxy configuration", set random http proxy, change port
(like HTTP Proxy: aa Po
*** Bug 888475 has been marked as a duplicate of this bug. ***
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to firefox in Ubuntu.
https://bugs.launchpad.net/bugs/1194841
Title:
Firefox 22 uses stale manual proxy settings when configure
This is a nasty bug, since Firefox just fails without any error message
after upgrading to version 22. I was affected myself and it took a while
to diagnose. One thing puzzles me: why does google.com still work when a
broken manual proxy is configured?
--
You received this bug notification becaus
Perhaps this bug also affects my problem: after upgraded to Firefox 22
(through the standard Ubuntu update info dialog), my auto proxy config
whitelist.pac file is simply ignored! This is highly critical as my
children are now able to browse to any website on the internet!
Thankfully, I noticed thi
This breaks "the internet" for many technical illiterate users. A fix is
required ASAP.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to firefox in Ubuntu.
https://bugs.launchpad.net/bugs/1194841
Title:
Firefox 22 uses stale manual prox
A fix for this is building in the security PPA, and should be available
for people to test soon.
https://launchpad.net/~ubuntu-mozilla-security/+archive/ppa
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to firefox in Ubuntu.
https://bugs.
** Branch linked: lp:~mozillateam/firefox/firefox.precise
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to firefox in Ubuntu.
https://bugs.launchpad.net/bugs/1194841
Title:
Firefox 22 uses stale manual proxy settings when configured to
** Branch linked: lp:firefox/stable
** Branch linked: lp:~mozillateam/firefox/firefox.quantal
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to firefox in Ubuntu.
https://bugs.launchpad.net/bugs/1194841
Title:
Firefox 22 uses stale manu
Launchpad has imported 36 comments from the remote bug at
https://bugzilla.mozilla.org/show_bug.cgi?id=817533.
If you reply to an imported comment from within Launchpad, your comment
will be sent to the remote bug automatically. Read more about
Launchpad's inter-bugtracker facilities at
https://he
23.0 beta is already in saucy-proposed, which has the fix
** Changed in: firefox (Ubuntu)
Status: Triaged => Fix Committed
** Summary changed:
- Upgrade to ff22 enters proxy-settings
+ Firefox 22 uses stale manual proxy settings when configured to use system
proxy, and system proxy setti
** Description changed:
+ *** WORKAROUND ***
+
+ This only applies if you have Firefox configured to use the system proxy
+ settings (which is the default) and have used the manual settings at
+ some point in the past.
+
+ 1) Open the proxy configuration dialog
+- Edit -> Preferences from th
no "http_proxy" or "all_proxy" in my env.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to firefox in Ubuntu.
https://bugs.launchpad.net/bugs/1194841
Title:
Upgrade to ff22 enters proxy-settings
Status in The Mozilla Firefox Browser:
Oh, sorry, I missed the reference to
https://bugzilla.mozilla.org/show_bug.cgi?id=817533, thanks.
I was just looking at that. Yes, it looks like a likely culprit
** Also affects: firefox via
https://bugzilla.mozilla.org/show_bug.cgi?id=817533
Importance: Unknown
Status: Unknown
** C
** Also affects: firefox (Ubuntu Precise)
Importance: Undecided
Status: New
** Also affects: firefox (Ubuntu Quantal)
Importance: Undecided
Status: New
** Also affects: firefox (Ubuntu Raring)
Importance: Undecided
Status: New
** Changed in: firefox (Ubuntu Precise)
Looks like this is the same bug already reported in Mozilla bugtracker:
https://bugzilla.mozilla.org/show_bug.cgi?id=817533
** Bug watch added: Mozilla Bugzilla #817533
https://bugzilla.mozilla.org/show_bug.cgi?id=817533
--
You received this bug notification because you are a member of Deskto
Does anyone have "http_proxy" or "all_proxy" set in their environment
(you can check with "env | grep proxy"
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to firefox in Ubuntu.
https://bugs.launchpad.net/bugs/1194841
Title:
Upgrade to f
The bug affect me, too (I noticed a serious slow-down of browsing, after
the upgrade). By going on " Firefox > Edit > Preferences > Advanced >
Settings > Configure Proxies", i noticed that when I set "auto-detect
proxy", everything works ok, while when I set "use system proxy
settings", the setting
I can confirm setting "Use system proxy settings" really uses parameter from
"Manual proxy" setting.
Using "No proxy" option still works.
This was introduced with latest firefox update this morning.
--
You received this bug notification because you are a member of Desktop
Packages, which is subs
When I was upgraded to Firefox 22, pages refused to load with "Firefox
is configured to use a proxy server that is refusing connections."
Firefox > Edit > Preferences > Advanced > Settings > Configure
Proxies... was set to "Use system proxy settings" but in System Settings
> Network > Network prox
The situation is even worse. I'm using ssh SOCKS proxy as well as direct
connection to Internet. I switch between them by choosing "system proxy"
and "manual proxy" variants. However, after upgrade to Firefox 22 the
selection "System proxy" works just like I have "Manual proxy" selection
(which is
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: firefox (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to firefox in Ubuntu.
https://bugs.launchpad.net/bugs/1194
I tried to find out something about the proxy-IP address. It might
belong to a place where I've been working 2 years ago (February 2011),
but only now, with the upgrade to FF22, those settings have been used?
Heiko
--
You received this bug notification because you are a member of Desktop
Package
Public bug reported:
I just received the upgrade to FF22 through the update-center. After
restarting firefox, I wasn't able to connect to any single web-page.
Checking the 'about:config' network settings, I found out that something
had changed the proxy-settings and everything was directed to
'13
35 matches
Mail list logo
