Bug 694821

Summary: Thunderbird doesn't pick up GNOME proxy settings
Product: [Fedora] Fedora Reporter: Theodore Lee <theo148>
Component: thunderbirdAssignee: Jan Horak <jhorak>
Status: CLOSED DUPLICATE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 15CC: andy_longworth, gecko-bugs-nobody, mcepl, ricardo.arguello
Target Milestone: ---Keywords: Triaged
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2012-03-26 14:19:56 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:

Description Theodore Lee 2011-04-08 14:21:20 UTC 
Description of problem:
On Fedora 15, setting a proxy using the GNOME network settings has no effect on Thunderbird.

Version-Release number of selected component (if applicable):
thunderbird-3.1.9-6.fc15.x86_64

How reproducible:
This seems to be always reproducible when trying to set a SOCKS proxy to use.
Setting other proxy types doesn't seem to work either, although I haven't tried
those thoroughly.

Steps to Reproduce (generic):
1. Click on the NetworkManager icon and click 'Network Settings'.
2. Go to the 'Network proxy' settings.
3. Set the proxy method to 'Manual'.
4. Type the hostname and port of your proxy in the appropriate field.
5. Start Thunderbird (set to use system proxy settings under the advanced network preferences).

Actual results:
Thunderbird tries to connect to the internet without using a proxy.

Expected results:
Thunderbird should connect through the proxy specified in the network settings.

Additional info:
It seems that this issue is affecting a number of applications, which still attempt to fetch proxy settings from gconf instead of the new dconf backend.
Comment 1 Matěj Cepl 2011-04-08 17:42:04 UTC 
More details in bug 691627
Comment 2 Jan Horak 2012-03-26 14:19:56 UTC 
This should be fixed in Thunderbird 11. Please reopen if problem reoccurs.

*** This bug has been marked as a duplicate of bug 691627 ***