restricted driver downloader ignore proxy settings

[Nikolay Kasatkin]

$ lsb_release -rd
Description: Ubuntu 9.04
Release: 9.04

$ apt-cache policy jockey-common
jockey-common:
  Installed: 0.5-0ubuntu10
  Candidate: 0.5-0ubuntu10
  Version table:
 *** 0.5-0ubuntu10 0
        500 http://ru.archive.ubuntu.com jaunty/main Packages
        100 /var/lib/dpkg/status

$ env |grep proxy
http_proxy=http://rain.ctd.loc:3128/
no_proxy=localhost,127.0.0.0/8,*.local,*.ctd.loc,192.168.10.0/24

Same proxy settings in Synaptic (Settings - Options - Network).

Expected installed proprietary nvidia drivers.

What happened:
After start jockey-gtk list available drivers. But after pressing 'activate' and entering password progress bar stay at 0%, 'netstat' show:

tcp 0 1 192.168.10.50:49114 77.88.19.73:80 SYN_SENT 16337/http

and after a while error message displayed with 'ubuntu-bug jockey-common'.

ProblemType: Bug
Architecture: i386
DistroRelease: Ubuntu 9.04
Lsusb:
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
 Bus 002 Device 002: ID 051d:0002 American Power Conversion Uninterruptible Power Supply
 Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
MachineType: K-Systems C51GM03
Package: jockey-common 0.5-0ubuntu10
PackageArchitecture: all
ProcCmdLine: root=UUID=248860e9-21ac-4bd4-a5bf-6cba57ad11ad ro quiet splash
ProcEnviron:
 LANG=ru_RU.UTF-8
 SHELL=/bin/bash
ProcVersionSignature: Ubuntu 2.6.28-11.42-generic
SourcePackage: jockey

[Chris674 (xxbrokensoulxx666)]

i have the same prob

[Dan Halbert (dhalbert)]

I believe this is an actual bug. Running jockey-gtk from System->Administration->Hardware Drivers ignores any proxy setup specified in synaptic, and there is no visible mechanism for setting a proxy in the jockey UI.

A workaround is to have proxy setups in environment variables: (http_proxy, etc.), and then run "sudo jockey-gtk" from the command line.

[Dan Halbert (dhalbert)]

To explicate #3: Someone converted this bug to a question. I have converted it back to a bug.

[Denis Rut'kov (dendron2000)]

I have this bug, too.

[Jay (jayb)]

This also affects Karmic (9.10) however the workaround posted above no longer works!

[Jay (jayb)]

It does however appear to read the /etc/apt/apt.conf file.
Adding the authentication details there appears to have fixed this issue for me.
Jay

[Ryan Stuart (ryanstuart)]

Can confirm this bug on 9.10 amd64 Desktop.

[tuharsky (tuharsky)]

Confirming 9.10 i386. Apt settings don't help for me.

[tigmoid (timmelw)]

WORKAROUND:

I'm on 9.10_amd64. I used synaptic to select the packages needed for the nvidia driver version I wanted. When I click the Apply button I select the download only option. Once the files are downloaded, quit synaptic (clicking through the warning about unapplied changes) and then run the restricted hardware installer. It will find the files that were just downloaded and install the packages...

[Michael Mueller (mmueller12345)]

Still valid for 10.04, Lucid Lynx.

[demoez walker (demoez)]

tigmoid's workaround works. Confirmed 9.04_amd64.

[Uli Tillich (utillich)]

It worked for me in Lucid.
Possibly because I ran the command "no_proxy=$(echo $no_proxy | sed 's/,$//')" as specified in Bug#554068.
Can someone confirm if this fixes the problem?

[Launchpad Janitor (janitor)]

This bug was fixed in the package jockey - 0.8-0ubuntu5

---------------
jockey (0.8-0ubuntu5) natty; urgency=low

  * data/handlers/nvidia.py: Fix typo.
  * backend/com.ubuntu.DeviceDriver.service: Export {http,https,ftp}_proxy
    variables from /etc/environment into the backend. (LP: #373795)
 -- Martin Pitt <email address hidden> Mon, 31 Jan 2011 11:31:56 +0100