I think we have two different bugs discussed here. The original problem of immediate silent failure occurs on a stock intrepid desktop CD with an nVidia quadro board with a recommended nvidia-177 driver (nothing to do with the legacy driver issue from bug 288662). After using update manager to do a check for updates (but not installing any of them) jockey-gtk -e xorg:nvidia-177 runs for about 10 seconds then returns the following dbus error:
Traceback (most recent call last):
File "/usr/bin/jockey-gtk", line 377, in <module>
sys.exit(u.run())
File "/usr/lib/python2.5/site-packages/jockey/ui.py", line 395, in run
self.argv_options.confirm, False):
File "/usr/lib/python2.5/site-packages/jockey/ui.py", line 594, in set_handler_enable
polkit_auth_wrapper(self.backend().set_enabled, handler_id, enable)
File "/usr/lib/python2.5/site-packages/jockey/backend.py", line 104, in polkit_auth_wrapper
return fn(*args, **kwargs)
File "/var/lib/python-support/python2.5/dbus/proxies.py", line 140, in __call__
**keywords)
File "/var/lib/python-support/python2.5/dbus/connection.py", line 607, in call_blocking
message, timeout)
dbus.exceptions.DBusException: org.freedesktop.DBus.Error.NoReply: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.
nwadmin@nwadmin-laptop:~$ jockey-gtk -l
xorg:nvidia-173 - NVIDIA accelerated graphics driver (version 173) (Proprietary, Disabled, Not in use)
kmod:wl - Broadcom STA wireless driver (Proprietary, Enabled, In use)
xorg:nvidia-177 - NVIDIA accelerated graphics driver (version 177) (Proprietary, Enabled, Not in use)
I had jockey-backend running in a separate window as suggested above and about 30 seconds after jockey-gtk crashed the backend kicked to life and apparently installed the driver successfully.
It seems to me that the silent failure is related to a repository/package problem on the CD. The dbus failure might be a download timeout.
I think we have two different bugs discussed here. The original problem of immediate silent failure occurs on a stock intrepid desktop CD with an nVidia quadro board with a recommended nvidia-177 driver (nothing to do with the legacy driver issue from bug 288662). After using update manager to do a check for updates (but not installing any of them) jockey-gtk -e xorg:nvidia-177 runs for about 10 seconds then returns the following dbus error:
Traceback (most recent call last): jockey- gtk", line 377, in <module> exit(u. run()) python2. 5/site- packages/ jockey/ ui.py", line 395, in run argv_options. confirm, False): python2. 5/site- packages/ jockey/ ui.py", line 594, in set_handler_enable auth_wrapper( self.backend( ).set_enabled, handler_id, enable) python2. 5/site- packages/ jockey/ backend. py", line 104, in polkit_auth_wrapper python- support/ python2. 5/dbus/ proxies. py", line 140, in __call__ python- support/ python2. 5/dbus/ connection. py", line 607, in call_blocking .DBusException: org.freedesktop .DBus.Error. NoReply: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken. nwadmin- laptop: ~$ jockey-gtk -l
File "/usr/bin/
sys.
File "/usr/lib/
self.
File "/usr/lib/
polkit_
File "/usr/lib/
return fn(*args, **kwargs)
File "/var/lib/
**keywords)
File "/var/lib/
message, timeout)
dbus.exceptions
nwadmin@
xorg:nvidia-173 - NVIDIA accelerated graphics driver (version 173) (Proprietary, Disabled, Not in use)
kmod:wl - Broadcom STA wireless driver (Proprietary, Enabled, In use)
xorg:nvidia-177 - NVIDIA accelerated graphics driver (version 177) (Proprietary, Enabled, Not in use)
I had jockey-backend running in a separate window as suggested above and about 30 seconds after jockey-gtk crashed the backend kicked to life and apparently installed the driver successfully.
It seems to me that the silent failure is related to a repository/package problem on the CD. The dbus failure might be a download timeout.