jockey-gtk crashed with GError in function(): Icon 'jockey-disabled' not present in theme
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
jockey (Ubuntu) |
New
|
Undecided
|
Unassigned |
Bug Description
Occurred when Additional drivers is selected from the Administrative menu
ProblemType: Crash
DistroRelease: Ubuntu 11.04
Package: jockey-gtk 0.9-0ubuntu1
ProcVersionSign
Uname: Linux 2.6.38-2-generic x86_64
Architecture: amd64
CurrentDmesg: Error: command ['sh', '-c', 'dmesg | comm -13 --nocheck-order /var/log/dmesg -'] failed with exit code 1: comm: /var/log/dmesg: Permission denied
Date: Wed Feb 9 21:17:14 2011
ExecutablePath: /usr/bin/jockey-gtk
InterpreterPath: /usr/bin/python2.7
Lsusb:
Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
MachineType: Hewlett-Packard Presario R3200 (PF162UA#ABL)
PackageArchitec
PccardctlIdent:
Socket 0:
no product info available
Socket 1:
no product info available
PccardctlStatus:
Socket 0:
no card
Socket 1:
no card
ProcCmdline: /usr/bin/python /usr/bin/jockey-gtk
ProcEnviron:
LANGUAGE=en_CA:en
LANG=en_CA.UTF-8
LC_MESSAGES=
SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=
PythonArgs: ['/usr/
SourcePackage: jockey
Title: jockey-gtk crashed with GError in function(): Icon 'jockey-disabled' not present in theme
UserGroups:
dmi.bios.date: 04/28/2005
dmi.bios.vendor: Hewlett-Packard
dmi.bios.version: F.35
dmi.board.name: 08A0
dmi.board.vendor: Compal
dmi.board.version: 32.42
dmi.chassis.type: 10
dmi.chassis.vendor: Compal
dmi.modalias: dmi:bvnHewlett-
dmi.product.name: Presario R3200 (PF162UA#ABL)
dmi.product.
dmi.sys.vendor: Hewlett-Packard
Thank you for taking the time to report this crash and helping to make Ubuntu better. This particular crash has already been reported and is a duplicate of bug #715753, so 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. Please continue to report any other bugs you may find.