jockey-gtk crashed with TypeError in _cleanup(): an integer is required

Bug #730551 reported by Markus Jonskog
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
jockey (Ubuntu)
New
Undecided
Unassigned

Bug Description

Fresh install of natty daily build 2011-03-07. Then tried to start Additional drivers.

ProblemType: Crash
DistroRelease: Ubuntu 11.04
Package: jockey-gtk 0.9.1-0ubuntu5
ProcVersionSignature: Ubuntu 2.6.38-5.32-generic 2.6.38-rc6
Uname: Linux 2.6.38-5-generic x86_64
.var.log.jockey.log:
 2011-03-07 12:37:19,384 DEBUG: Updating repository indexes...
 2011-03-07 11:44:23,498 DEBUG: Updating repository indexes...
Architecture: amd64
Date: Mon Mar 7 11:44:33 2011
ExecutablePath: /usr/bin/jockey-gtk
InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Alpha amd64 (20110307)
InterpreterPath: /usr/bin/python2.7
MachineType: Dell Inc. Latitude E4200
PackageArchitecture: all
ProcCmdline: /usr/bin/python /usr/bin/jockey-gtk
ProcEnviron:
 LANGUAGE=en_US:en
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.38-5-generic root=UUID=62fda727-03db-4f3a-a6f9-b176b0bacf7c ro quiet splash vt.handoff=7
PythonArgs: ['/usr/bin/jockey-gtk']
SourcePackage: jockey
Title: jockey-gtk crashed with TypeError in _cleanup(): an integer is required
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare
dmi.bios.date: 08/03/2009
dmi.bios.vendor: Dell Inc.
dmi.bios.version: A08
dmi.board.name: 0D271H
dmi.board.vendor: Dell Inc.
dmi.chassis.type: 8
dmi.chassis.vendor: Dell Inc.
dmi.modalias: dmi:bvnDellInc.:bvrA08:bd08/03/2009:svnDellInc.:pnLatitudeE4200:pvr:rvnDellInc.:rn0D271H:rvr:cvnDellInc.:ct8:cvr:
dmi.product.name: Latitude E4200
dmi.sys.vendor: Dell Inc.

Revision history for this message
Markus Jonskog (omljud) 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 #711225, 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.