Bug 694821 - Thunderbird doesn't pick up GNOME proxy settings
Summary: Thunderbird doesn't pick up GNOME proxy settings
Keywords:
Status: CLOSED DUPLICATE of bug 691627
Alias: None
Product: Fedora
Classification: Fedora
Component: thunderbird
Version: 15
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Jan Horak
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-04-08 14:21 UTC by Theodore Lee
Modified: 2018-04-11 10:35 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2012-03-26 14:19:56 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)

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 ***


Note You need to log in before you can comment on or make changes to this bug.