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
Crash on startup
ProblemType: Crash
DistroRelease: Ubuntu 11.04
Package: jockey-gtk 0.9-0ubuntu1
ProcVersionSign
Uname: Linux 2.6.38-3-generic i686
Architecture: i386
CurrentDmesg:
[ 18.217036] [drm] nouveau 0000:01:00.0: Setting dpms mode 0 on vga encoder (output 0)
[ 18.217045] [drm] nouveau 0000:01:00.0: Output VGA-1 is running on CRTC 0 using output A
[ 19.356166] EXT4-fs (sda4): re-mounted. Opts: errors=
[ 26.720011] eth1: no IPv6 routers present
[ 26.858091] EXT4-fs (sda4): re-mounted. Opts: errors=
Date: Sun Feb 13 07:13:30 2011
ExecutablePath: /usr/bin/jockey-gtk
InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Alpha i386 (20110210)
InterpreterPath: /usr/bin/python2.7
Lsusb:
Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 002 Device 002: ID 15d9:0a33 Trust International B.V. Optical Mouse
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
PackageArchitec
ProcCmdline: /usr/bin/python /usr/bin/jockey-gtk
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/22/2004
dmi.bios.vendor: Phoenix Technologies, LTD
dmi.bios.version: 6.00 PG
dmi.board.name: i845GEV/PEV-W83627
dmi.chassis.type: 3
dmi.modalias: dmi:bvnPhoenixT
dmi.sys.vendor: EVERCOM NETWORK
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.