> The way to use it is by setting the `HTTPS_PROXY` environment variable. This
> is done for you by GNOME proxy settings capplet.
... But it won't work for dbus-autostarted applications (checked in Maverick).
Here's why:
dbus-launch --exit-with-session gnome-session
gnome-session sets up HTTP proxy environment variables properly but syncdaemon is started by dbus which is not yet aware of these environment variables, therefore it won't see proxy configuration and will fail during connection.
It will work if the user launches /usr/lib/ubuntuone-client/ubuntuone-syncdaemon from the terminal but that is rather uncommon way of launching ubuntuone.
Are any other dbus-autostarted applications use network the way we do? How do they work then?
> The way to use it is by setting the `HTTPS_PROXY` environment variable. This
> is done for you by GNOME proxy settings capplet.
... But it won't work for dbus-autostarted applications (checked in Maverick).
Here's why: ubuntuone- client/ ubuntuone- syncdaemon from the terminal but that is rather uncommon way of launching ubuntuone.
dbus-launch --exit-with-session gnome-session
gnome-session sets up HTTP proxy environment variables properly but syncdaemon is started by dbus which is not yet aware of these environment variables, therefore it won't see proxy configuration and will fail during connection.
It will work if the user launches /usr/lib/
Are any other dbus-autostarted applications use network the way we do? How do they work then?