File "/usr/lib/python2.6/dist-packages/jockey/ui.py", line 448, in run
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
jockey (Ubuntu) |
New
|
Undecided
|
Unassigned |
Bug Description
~$ sudo jockey-gtk
Traceback (most recent call last):
File "/usr/bin/
sys.
File "/usr/lib/
self.
File "/usr/bin/
self.
File "/usr/bin/
for h_id in self.get_
File "/usr/lib/
return self.backend(
File "/usr/lib/
**keywords)
File "/usr/lib/
message, timeout)
dbus.exceptions
File "/usr/lib/
retval = candidate_
File "/usr/lib/
return self.handlers.
AttributeError: 'Backend' object has no attribute 'handlers'
ProblemType: Bug
DistroRelease: Ubuntu 11.04
Package: jockey-gtk 0.6-0ubuntu2
ProcVersionSign
Uname: Linux 2.6.37-6-generic x86_64
NonfreeKernelMo
.var.log.
2010-11-27 22:53:09,946 DEBUG: updating <jockey.
2010-11-27 22:54:35,391 DEBUG: updating <jockey.
Architecture: amd64
Date: Sat Nov 27 22:56:13 2010
InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Alpha amd64 (20100824)
MachineType: To Be Filled By O.E.M. S37S
PackageArchitec
ProcEnviron:
LANGUAGE=en
PATH=(custom, user)
LANG=en_US.utf8
SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=
SourcePackage: jockey
dmi.bios.date: 01/22/2008
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 0801
dmi.board.
dmi.board.name: S37S
dmi.board.vendor: To Be Filled By O.E.M.
dmi.board.version: 1.00
dmi.chassis.
dmi.chassis.type: 10
dmi.chassis.vendor: To Be Filled By O.E.M.
dmi.chassis.
dmi.modalias: dmi:bvnAmerican
dmi.product.name: S37S
dmi.product.
dmi.sys.vendor: To Be Filled By O.E.M.
While the line numbers have changed since this was reported, the stack trace is otherwise identical to the one in bug 946973, so I'm marking it a duplicate of that.
Thank you for taking the time to report this bug and helping to make Ubuntu better. This particular bug has already been reported and is a duplicate of bug 946973, so it is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Feel free to continue to report any other bugs you may find.