GNOME Bugzilla – Bug 514649
Use Gnome Proxy settings
Last modified: 2018-07-01 09:04:50 UTC
Please describe the problem: When attempting to use conduit behind a proxy server, it fails to connect to thw web Steps to reproduce: 1. create a sync between a local file and box.net 2. start sync. 3. sync times out Actual results: The sync will always time out. Expected results: inbuilt web browser page should open so that you can login Does this happen every time? yes Other information: From the log. gtkui.UI ][DEBUG ] GUI got sync started (UI.py:169) [gtkui.UI ][DEBUG ] Icon got sync started (UI.py:592) [Web ][INFO ] Logging in using browser: gtkmozembed (Web.py:316) [Web ][DEBUG ] LOGIN (thread: -1285649520) (Web.py:281) [Web ][DEBUG ] CREATE PAGE: http://www.box.net/api/1.0/auth/nmzltlpij6s6y9k2sbevo4408frs8itu (thread: -1209001792) (Web.py:217)
Extra info: Running 0.3.6 from getdeb Conduit login window does not show when launched from gnome menu, only from command line
For instructions on setting up the gtkmozembed proxy, see https://develop.participatoryculture.org/trac/democracy/browser/trunk/tv/platform/gtk-x11/miroplatform/mozsetup.py
firefox 3 (and gecko 1.9 I guess), can now use the system proxy. Will have to look into the required config to make this happen in gtkmozembed
The gtkmozembed bit is done. Now we need to propogate the proxy settings to the other libs
*** Bug 540234 has been marked as a duplicate of this bug. ***
*** Bug 532161 has been marked as a duplicate of this bug. ***
Conduit is not under active development anymore, has not seen code changes for eight years, and saw its last tarball release in 2010. Its codebase has been archived: https://gitlab.gnome.org/Archive/conduit/commits/master Closing this report as WONTFIX as part of Bugzilla Housekeeping to reflect reality. Please feel free to reopen this ticket (or rather transfer the project to GNOME Gitlab, as GNOME Bugzilla is deprecated) if anyone takes the responsibility for active development again.