Ubuntu
jockey package

jockey-gtk crashed with KeyError in __getitem__(): 'package'

Bug #836714 reported by Maarten Kossen
22
This bug affects 4 people
Affects Status Importance Assigned to Milestone
jockey (Ubuntu)
Confirmed
Undecided
Unassigned

Bug Description

Trying to run jockey-gtk with --no-dbus option.

ProblemType: Crash
DistroRelease: Ubuntu 11.10
Package: jockey-gtk 0.9.4-0ubuntu2
ProcVersionSignature: Ubuntu 3.0.0-9.14-generic 3.0.3
Uname: Linux 3.0.0-9-generic x86_64
.var.log.jockey.log:

Architecture: amd64
Date: Mon Aug 29 15:46:22 2011
ExecutablePath: /usr/bin/jockey-gtk
InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Alpha amd64 (20110803.1)
InterpreterPath: /usr/bin/python2.7
MachineType: CLEVO CO. W150HRM
PackageArchitecture: all
ProcCmdline: /usr/bin/python /usr/bin/jockey-gtk --no-dbus
ProcEnviron:
 PATH=(custom, no user)
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.0.0-9-generic root=UUID=d2765750-c01d-4006-9224-70d896dcf19f ro quiet splash vt.handoff=7
PythonArgs: ['/usr/bin/jockey-gtk', '--no-dbus']
SourcePackage: jockey
Title: jockey-gtk crashed with KeyError in __getitem__(): 'package'
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups:

dmi.bios.date: 04/08/2011
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 4.6.4
dmi.board.asset.tag: To be filled by O.E.M.
dmi.board.name: W150HRM
dmi.board.vendor: CLEVO CO.
dmi.board.version: N/A
dmi.chassis.asset.tag: To Be Filled By O.E.M.
dmi.chassis.type: 9
dmi.chassis.vendor: CLEVO CO.
dmi.chassis.version: N/A
dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr4.6.4:bd04/08/2011:svnCLEVOCO.:pnW150HRM:pvrN/A:rvnCLEVOCO.:rnW150HRM:rvrN/A:cvnCLEVOCO.:ct9:cvrN/A:
dmi.product.name: W150HRM
dmi.product.version: N/A
dmi.sys.vendor: CLEVO CO.

Revision history for this message
Maarten Kossen (mpkossen) wrote :
visibility: private → public
Apport retracing service (apport)
tags: removed: need-duplicate-check
Launchpad Janitor (janitor)
Changed in jockey (Ubuntu):
status: New → Confirmed
Revision history for this message
Xavier Bassery (xaba) wrote :

This bug also affects me.
The first time I ran jockey that way it did work though.
Jockey has told me then that there was a restricted driver available (fglrx) and I have activated it.
There were no other devices displayed.
Since then, I get this bug.
I have reported a duplicate bug (marked as such) in order to give details about my system and help the resolution.

Revision history for this message
djr013 (djr013) wrote :

I do not currently have the restricted drivers installed when hitting this bug, though I have had them installed before.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.
Subscribing...

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.