jockey-backend crashed with MemoryError in run_dbus_service()

[Marcin]

while "sudo apt-get update" jockey-backend crashed

ProblemType: Crash
DistroRelease: Ubuntu 11.10
Package: jockey-common 0.9.4-0ubuntu2
ProcVersionSignature: Ubuntu 3.0.0-9.14-generic 3.0.3
Uname: Linux 3.0.0-9-generic x86_64
NonfreeKernelModules: fglrx
.var.log.jockey.log:

Architecture: amd64
Date: Fri Aug 26 22:58:57 2011
ExecutablePath: /usr/share/jockey/jockey-backend
InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Alpha amd64 (20110803.1)
InterpreterPath: /usr/bin/python2.7
MachineType: FUJITSU SIEMENS ESPRIMO Mobile V5545
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=9da8bee2-23ac-4650-81c1-cd1fedb18c85 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-12 (14 days ago)
UserGroups:

dmi.bios.date: 09/20/2007
dmi.bios.vendor: Phoenix Technologies LTD
dmi.bios.version: R01-A0U
dmi.board.name: ESPRIMO Mobile V5545
dmi.board.vendor: FUJITSU SIEMENS
dmi.board.version: Not Applicable
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: FUJITSU SIEMENS
dmi.chassis.version: A2040
dmi.modalias: dmi:bvnPhoenixTechnologiesLTD:bvrR01-A0U:bd09/20/2007:svnFUJITSUSIEMENS:pnESPRIMOMobileV5545:pvr20:rvnFUJITSUSIEMENS:rnESPRIMOMobileV5545:rvrNotApplicable:cvnFUJITSUSIEMENS:ct10:cvrA2040:
dmi.product.name: ESPRIMO Mobile V5545
dmi.product.version: 20
dmi.sys.vendor: FUJITSU SIEMENS

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