ubiquity crashed with EOFError in /usr/lib/python3.2/pickle.py: EOF read where not expected

[Joel Pickett]

Booting off the 20120911 daily desktop image. As soon as the desktop shows, this error displays.

ProblemType: Crash
DistroRelease: Ubuntu 12.10
Package: ubiquity 2.11.31
ProcVersionSignature: Ubuntu 3.5.0-14.15-generic 3.5.3
Uname: Linux 3.5.0-14-generic x86_64
ApportVersion: 2.5.1-0ubuntu7
Architecture: amd64
CasperVersion: 1.322
Date: Wed Sep 12 17:37:10 2012
ExecutablePath: /usr/bin/ubiquity
InstallCmdLine: initrd=/ubninit file=/cdrom/preseed/ubuntu.seed boot=casper quiet splash -- BOOT_IMAGE=/ubnkern
InterpreterPath: /usr/bin/python3.2mu
LiveMediaBuild: Ubuntu 12.10 "Quantal Quetzal" - Alpha amd64 (20120911)
ProcCmdline: /usr/bin/python3 /usr/bin/ubiquity gtk_ui
ProcEnviron:
 PATH=(custom, no user)
 LANG=en_US.UTF-8
 SHELL=/bin/bash
 TERM=unknown
PythonArgs: ['/usr/bin/ubiquity', 'gtk_ui']
SourcePackage: ubiquity
Title: ubiquity crashed with EOFError in /usr/lib/python3.2/pickle.py: EOF read where not expected
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups:

[Brian Murray (brian-murray)]

Thank you for taking the time to report this bug and helping to make Ubuntu better. This particular bug has already been reported and is a duplicate of bug 1058884, so it 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.