[Webkit-unassigned] [Bug 120833] New: [GTK] Desktop proxy settings are ignored inside the jhbuild

[bugzilla-daemon at webkit.org]

https://bugs.webkit.org/show_bug.cgi?id=120833

           Summary: [GTK] Desktop proxy settings are ignored inside the
                    jhbuild
           Product: WebKit
           Version: 528+ (Nightly build)
          Platform: Unspecified
        OS/Version: Unspecified
            Status: NEW
          Keywords: Gtk
          Severity: Normal
          Priority: P2
         Component: Tools / Tests
        AssignedTo: webkit-unassigned at lists.webkit.org
        ReportedBy: mario at webkit.org
                CC: gns at gnome.org, zandobersek at gmail.com,
                    cgarcia at igalia.com


Currently, regardless of which proxy configuration you have defined in your desktop settings (none, auto or manual), tools run inside the WebKitGTK+'s internal jhbuild environment (e.g. GtkLauncher, MiniBrowser...) will always ignore them and assume 'none', making it impossible to run those tools easily in certain environment (e.g. restricted corporate networks).

For instance, if I try to run GtkLauncher like this from here:

  $ Tools/Scripts/run-launcher --gtk http://www.asdf.com


All I get is GtkLauncher trying to load that web site forever, since it should use the proxy settings I've defined in my system and that I can check from command line through gsettings:

  $ gsettings get 'org.gnome.system.proxy' 'mode'
  'auto'

  $ gsettings get 'org.gnome.system.proxy' 'autoconfig-url'
  'http://<super-secret-IP>:<super-secret-PORT>/proxy.pac'


However, if I run the same commands inside the jhbuild shell (run with Tools/jhbuild/jhbuild-wrapper --gtk shell), all I get is this:

  $ gsettings get 'org.gnome.system.proxy' 'mode'
  'none'

  $ gsettings get 'org.gnome.system.proxy' 'autoconfig-url'
  ''

So the problem seems to be that we are using the GSettings memory backend instead the dconf one, and we are not getting any warning such as "GLib-GIO-Message: Using the 'memory' GSettings backend." because we are explicitly setting the memory backend in our jhbuild environment. As from Tools/gtk/jhbuildrc file:

  [...]
  # We often end up using the memory backend anyway, so explicitly choosing
  # it will prevent the warning message.
  os.environ['GSETTINGS_BACKEND'] = 'memory'
  [...]


So, IMHO the solution to this issue would be to make sure we build the dconf module inside the internal jhbuild (so we can use the gsettings dconf backend) and make it the default backend in jhbuildrc. That way we will not only be able to use our tools properly behind a proxy, but we also will be able to access any other configuration options from gsettings in case we need them (and potentially uncover other issues we might be having because of that).

I'll be providing a patch soon for that.

-- 
Configure bugmail: https://bugs.webkit.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.