jockey-gtk crashed with GError in function(): L'icône « jockey-disabled » n'est pas présente dans le thème

Bug #718938 reported by Dave Létourneau
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
jockey (Ubuntu)
New
Undecided
Unassigned

Bug Description

Crash when i try to launch the restricted driver manager. From the tray and with the menu. Clean install from 30 min ago. Updates installed.

ProblemType: Crash
DistroRelease: Ubuntu 11.04
Package: jockey-gtk 0.9-0ubuntu1
ProcVersionSignature: Ubuntu 2.6.38-3.30-generic 2.6.38-rc4
Uname: Linux 2.6.38-3-generic x86_64
Architecture: amd64
Date: Mon Feb 14 14:12:25 2011
EcryptfsInUse: Yes
ExecutablePath: /usr/bin/jockey-gtk
InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Alpha amd64 (20110214)
InterpreterPath: /usr/bin/python2.7
PackageArchitecture: all
ProcCmdline: /usr/bin/python /usr/bin/jockey-gtk
ProcEnviron:
 LANGUAGE=fr_CA:en
 LANG=fr_CA.UTF-8
 LC_MESSAGES=fr_CA.utf8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.38-3-generic root=UUID=1dd740e0-3ee5-49ae-a9f7-a56d69d492cb ro quiet splash vt.handoff=7
PythonArgs: ['/usr/bin/jockey-gtk']
SourcePackage: jockey
Title: jockey-gtk crashed with GError in function(): L'icône « jockey-disabled » n'est pas présente dans le thème
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare
dmi.bios.date: 04/10/2009
dmi.bios.vendor: Intel Corp.
dmi.bios.version: LDB4310H.86A.0030.2009.0410.1420
dmi.board.asset.tag: To be filled by O.E.M.
dmi.board.name: DB43LD
dmi.board.vendor: Intel Corporation
dmi.board.version: AAE60577-201
dmi.chassis.type: 3
dmi.modalias: dmi:bvnIntelCorp.:bvrLDB4310H.86A.0030.2009.0410.1420:bd04/10/2009:svn:pn:pvr:rvnIntelCorporation:rnDB43LD:rvrAAE60577-201:cvn:ct3:cvr:

Revision history for this message
Dave Létourneau (daveletourneau) wrote :
Revision history for this message
Apport retracing service (apport) wrote : This bug is a duplicate

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.

tags: removed: need-duplicate-check
visibility: private → public
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

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