[Lucid] jockey-gtk crashes after upgrade

[Federico Vera]

After the upgrading from Karmic to Lucid (with todays alternate built) jockey failed to start, and the proprietary driver wasn't correctly loaded.

I've been doing this procedure since week one of the testing program [1] and never had a problem with the upgrade test, but I wanted to point out that when installing today (for the other tests) I encounter bug #562226, and this one might be related in some way.

[1] http://testcases.qa.ubuntu.com/Hardware/X/ProprietaryDrivers#Upgrade%20Testing

ProblemType: Crash
DistroRelease: Ubuntu 10.04
Package: jockey-gtk 0.5.8-0ubuntu7
ProcVersionSignature: Ubuntu 2.6.32-20.30-generic 2.6.32.11+drm33.2
Uname: Linux 2.6.32-20-generic i686
Architecture: i386
Date: Tue Apr 13 11:19:56 2010
ExecutablePath: /usr/bin/jockey-gtk
InstallationMedia: Ubuntu 9.10 "Karmic Koala" - Release i386 (20091028.5)
InterpreterPath: /usr/bin/python2.6
MachineType: MICRO-STAR INTERNATIONAL CO., LTD MS-7142
PackageArchitecture: all
ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.32-20-generic root=UUID=fee9ae0a-c8ca-4664-95cf-d3991f492094 ro quiet splash
ProcCmdline: /usr/bin/python /usr/bin/jockey-gtk
ProcEnviron:
 LANG=en_US.utf8
 SHELL=/bin/bash
PythonArgs: ['/usr/bin/jockey-gtk']
SourcePackage: jockey
Title: jockey-gtk crashed with AttributeError in has_repositories()
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare
dmi.bios.date: 06/27/2006
dmi.bios.vendor: Phoenix Technologies, LTD
dmi.bios.version: 6.00 PG
dmi.board.name: MS-7142
dmi.board.vendor: MICRO-STAR INTERNATIONAL CO., LTD
dmi.board.version: 1.00
dmi.chassis.type: 3
dmi.modalias: dmi:bvnPhoenixTechnologies,LTD:bvr6.00PG:bd06/27/2006:svnMICRO-STARINTERNATIONALCO.,LTD:pnMS-7142:pvr1.00:rvnMICRO-STARINTERNATIONALCO.,LTD:rnMS-7142:rvr1.00:cvn:ct3:cvr:
dmi.product.name: MS-7142
dmi.product.version: 1.00
dmi.sys.vendor: MICRO-STAR INTERNATIONAL CO., LTD

[Federico Vera (fedevera)]

I re tested and this time bug #562226 wasn't present during installation, and jockey still crashes

[Alberto Milone (albertomilone)]

Can you attach the new /var/log/jockey.log after reproducing the error, please?

[Federico Vera (fedevera)]

I did a new upgrade test today (with yesterday's daily build) and same error, here's the jockey log file.
If it helps, I filled another bug report (bug #568041) because the nVidia driver was removed after the xpr-007 test case[1] (I'm beginning to think that they are the same bug).

[1] http://testcases.qa.ubuntu.com/Hardware/X/ProprietaryDrivers#Upgrade%20Testing

[Narcis Garcia (narcisgarcia)]

I booted Ubuntu 10.04 Live-USB (desktop) on an Acer Aspire One, then I open a console/terminal window and run:
jockey.gtk

This is the result:

ERROR:dbus.proxies:Introspect error on :1.52:/DeviceDriver: 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.
Traceback (most recent call last):
  File "/usr/bin/jockey-gtk", line 417, in <module>
    sys.exit(u.run())
  File "/usr/lib/python2.6/dist-packages/jockey/ui.py", line 428, in run
    self.ui_show_main()
  File "/usr/bin/jockey-gtk", line 101, in ui_show_main
    self.update_tree_model()
  File "/usr/bin/jockey-gtk", line 277, in update_tree_model
    for h_id in self.get_displayed_handlers():
  File "/usr/lib/python2.6/dist-packages/jockey/ui.py", line 772, in get_displayed_handlers
    return self.backend().available(self.argv_options.mode)
  File "/usr/lib/python2.6/dist-packages/jockey/ui.py", line 110, in backend
    self._check_repositories()
  File "/usr/lib/python2.6/dist-packages/jockey/ui.py", line 795, in _check_repositories
    if self._dbus_iface.has_repositories():
  File "/usr/lib/pymodules/python2.6/dbus/proxies.py", line 68, in __call__
    return self._proxy_method(*args, **keywords)
  File "/usr/lib/pymodules/python2.6/dbus/proxies.py", line 140, in __call__
    **keywords)
  File "/usr/lib/pymodules/python2.6/dbus/connection.py", line 620, 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.

[dino99 (9d9)]

eol reached https://wiki.ubuntu.com/Releases