jockey-backend crashed with MemoryError in run_dbus_service()

[Konstantin Molchanov]

The error occured while I was NOT doing anything with jockey-backend at all. Seems like it failed to start automatically trying to find additional drivers

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
Architecture: i386
Date: Mon Aug 22 16:53:40 2011
ExecutablePath: /usr/share/jockey/jockey-backend
InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Alpha i386 (20110803.1)
InterpreterPath: /usr/bin/python2.7
Lsusb:
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
 Bus 002 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 192f:0416 Avago Technologies, Pte.
MachineType: eMachines eMachines E627
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=ee29bfd8-f86d-41fa-9e7e-a0d705e50634 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: Upgraded to oneiric on 2011-08-22 (0 days ago)
UserGroups:

dmi.bios.date: 10/20/2009
dmi.bios.vendor: eMachines
dmi.bios.version: V1.08
dmi.board.name: eMachines E627
dmi.board.vendor: eMachines
dmi.board.version: V1.08
dmi.chassis.type: 10
dmi.chassis.vendor: eMachines
dmi.chassis.version: V1.08
dmi.modalias: dmi:bvneMachines:bvrV1.08:bd10/20/2009:svneMachines:pneMachinesE627:pvrV1.08:rvneMachines:rneMachinesE627:rvrV1.08:cvneMachines:ct10:cvrV1.08:
dmi.product.name: eMachines E627
dmi.product.version: V1.08
dmi.sys.vendor: eMachines

[Apport retracing service (apport)]

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.