jockey-backend crashed with MemoryError in run_dbus_service()

[Rocky]

I was just trying to Syncronize my iPod, just testing the abilties of the operating system.

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 x86_64
.var.log.jockey.log:

Architecture: amd64
Date: Mon Aug 22 11:10:56 2011
ExecutablePath: /usr/share/jockey/jockey-backend
InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Alpha amd64 (20110803.1)
InterpreterPath: /usr/bin/python2.7
MachineType: ASUSTeK Computer Inc. G50VT
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=d6da6823-e478-48c2-981f-2a8d39d11b3d 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:

dmi.bios.date: 04/21/2009
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 213
dmi.board.asset.tag: ATN12345678901234567
dmi.board.name: G50VT
dmi.board.vendor: ASUSTeK Computer Inc.
dmi.board.version: 1.0
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: ASUSTeK Computer Inc.
dmi.chassis.version: 1.0
dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr213:bd04/21/2009:svnASUSTeKComputerInc.:pnG50VT:pvr1.0:rvnASUSTeKComputerInc.:rnG50VT:rvr1.0:cvnASUSTeKComputerInc.:ct10:cvr1.0:
dmi.product.name: G50VT
dmi.product.version: 1.0
dmi.sys.vendor: ASUSTeK Computer Inc.

[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.