jockey-backend crashed with MemoryError in run_dbus_service()

Bug #832039 reported by Lars Noodén
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
jockey (Ubuntu)
New
Undecided
Unassigned

Bug Description

jockey crashed all on its own.

ProblemType: Crash
DistroRelease: Ubuntu 11.10
Package: jockey-common 0.9.4-0ubuntu2
ProcVersionSignature: Ubuntu 3.0.0-9.12-generic 3.0.3
Uname: Linux 3.0.0-9-generic i686
.var.log.jockey.log:

Architecture: i386
Date: Tue Aug 23 20:11:57 2011
ExecutablePath: /usr/share/jockey/jockey-backend
InstallationMedia: Lubuntu 11.04 "Natty Narwhal" - i386 (20101203)
InterpreterPath: /usr/bin/python2.7
Lsusb: Error: command ['lsusb'] failed with exit code 1: unable to initialize libusb: -99
PackageArchitecture: all
ProcCmdline: /usr/bin/python /usr/share/jockey/jockey-backend --debug -l /var/log/jockey.log
ProcEnviron:

ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.0.0-9-generic root=UUID=31df5c1b-1fb0-4837-a43a-75e6fbb285cf ro quiet splash vt.handoff=7
PythonArgs: ['/usr/share/jockey/jockey-backend', '--debug', '-l', '/var/log/jockey.log']
SourcePackage: jockey
Title: jockey-backend crashed with MemoryError in run_dbus_service()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups:

Revision history for this message
Lars Noodén (larsnooden) 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 #831754, 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.