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
Network installation Ubuntu Alternate AMD64
TEST CASE:
1. First login after the installation, jockey indicates that restricted drivers are available,
2. Click on the jockey indicator and select 'install drivers'
Result:
this crash
ProblemType: Crash
DistroRelease: Ubuntu 11.04
Package: jockey-gtk 0.9-0ubuntu1
ProcVersionSign
Uname: Linux 2.6.38-3-generic x86_64
Architecture: amd64
CurrentDmesg:
[ 17.880064] eth0: no IPv6 routers present
[ 21.436949] hda-intel: IRQ timing workaround is activated for card #1. Suggest a bigger bdl_pos_adj.
[ 76.260141] usb 4-5: new low speed USB device using ohci_hcd and address 2
[ 76.463409] input: ARROW STRONG USB Mouse as /devices/
[ 76.463690] generic-usb 0003:0AB0:
Date: Sun Feb 13 16:29:39 2011
ExecutablePath: /usr/bin/jockey-gtk
InterpreterPath: /usr/bin/python2.7
MachineType: Gigabyte Technology Co., Ltd. GA-890GPA-UD3H
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: 07/23/2010
dmi.bios.vendor: Award Software International, Inc.
dmi.bios.version: FD
dmi.board.name: GA-890GPA-UD3H
dmi.board.vendor: Gigabyte Technology Co., Ltd.
dmi.board.version: x.x
dmi.chassis.type: 3
dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
dmi.modalias: dmi:bvnAwardSof
dmi.product.name: GA-890GPA-UD3H
dmi.sys.vendor: Gigabyte Technology Co., Ltd.
tags: | added: testcase |
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 #715925, 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.