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
during installation of restricted drivers
ProblemType: Crash
DistroRelease: Ubuntu 11.04
Package: jockey-gtk 0.9-0ubuntu2
ProcVersionSign
Uname: Linux 2.6.38-3-generic i686
Architecture: i386
BootDmesg: (Nothing has been logged yet.)
Date: Wed Feb 16 21:52:41 2011
ExecutablePath: /usr/bin/jockey-gtk
InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Alpha i386 (20110215)
InterpreterPath: /usr/bin/python2.7
Lsusb:
Bus 002 Device 002: ID 04f3:0230 Elan Microelectronics Corp.
Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 001 Device 003: ID 046d:080f Logitech, Inc. Webcam C120
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
MachineType: System manufacturer System Product Name
PackageArchitec
ProcCmdline: /usr/bin/python /usr/bin/jockey-gtk --check
ProcEnviron:
LANGUAGE=en_US:en
LANG=en_US.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: adm admin cdrom dialout lpadmin plugdev sambashare
dmi.bios.date: 10/29/2008
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 0602
dmi.board.
dmi.board.name: M2N-MX SE Plus
dmi.board.vendor: ASUSTeK Computer INC.
dmi.board.version: Rev x.xx
dmi.chassis.
dmi.chassis.type: 3
dmi.chassis.vendor: Chassis Manufacture
dmi.chassis.
dmi.modalias: dmi:bvnAmerican
dmi.product.name: System Product Name
dmi.product.
dmi.sys.vendor: System manufacturer
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 #719523, 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.