1002064 - Firefox 28.0 fails to use system-configured SOCKS proxy on Ubuntu 12.04

Status: RESOLVED WORKSFORME

(Core :: Networking, defect)

Description

[daemonlior]

Attachment: Ubuntu proxy settings

User Agent: Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:28.0) Gecko/20100101 Firefox/28.0 (Beta/Release)
Build ID: 20140317233623

Steps to reproduce:

I configured my Ubuntu 12.04 system-settings to work with only SOCKS proxy only (no HTTP/HTTPs/FTP).
I also configured Firefox 28.0 to "Use system proxy settings".


Actual results:

Firefox fails to retreive and use the SOCKS proxy I configured in the system-settings.
If I set the same SOCKS proxy settings in Firefox and not in the system, it works just fine.


Expected results:

I am pretty sure the problem caused by the fact that the HTTP text-box is empty. Firefox probably tries to retreive a NULL value and use it to connect.

Comment 1

[daemonlior]

Attachment: However, with these settings the connection succeed

Comment 2

[daemonlior]

Few more notes, those are the proxy settings I took with 'gsettings':
org.gnome.system.proxy autoconfig-url ''
org.gnome.system.proxy ignore-hosts ['localhost', '127.0.0.0/8']
org.gnome.system.proxy mode 'manual'
org.gnome.system.proxy use-same-proxy false
org.gnome.system.proxy.ftp host ''
org.gnome.system.proxy.ftp port 0
org.gnome.system.proxy.http authentication-password ''
org.gnome.system.proxy.http authentication-user ''
org.gnome.system.proxy.http enabled false
org.gnome.system.proxy.http host ''
org.gnome.system.proxy.http port 0
org.gnome.system.proxy.http use-authentication false
org.gnome.system.proxy.https host ''
org.gnome.system.proxy.https port 0
org.gnome.system.proxy.socks host '10.0.65.68'
org.gnome.system.proxy.socks port 9999

Even when I tried all kinds of combinations like setting the SOCKS as HTTP and use turn on the 'use-same-proxy' for example, it still didn't work.
There are settings here that are not accessible from GUI as you can see in the screenshot.

Comment 3

[Gary Chen [:xeonchen]]

I cannot reproduce this on Ubuntu 16.04 and Firefox release channel (v50).
Please feel free to reopen this if it still happens.