ubiquity crashed with TypeError in changed(): value is of wrong type for this column

[Ronald McCollam]

Binary package hint: ubiquity

(This may be a duplicate of bug 702898 but I thought it better to file it just in case.)

Ubiquity crashes repeatably when installing Xubuntu amd64 in VirtualBox. A crash is detected apparently during or around the drive formatting step, but ubiquity continues to appear to work until after asking for a username during install, at which point it vanishes.

This happens when installing from the live session. I will try the non-live install and see if the same thing happens and add that info to this bug.

ProblemType: Crash
DistroRelease: Ubuntu 11.04
Package: ubiquity 2.5.13
ProcVersionSignature: Ubuntu 2.6.38-1.28-generic 2.6.38-rc2
Uname: Linux 2.6.38-1-generic x86_64
Architecture: amd64
Date: Tue Feb 1 22:55:17 2011
ExecutablePath: /usr/lib/ubiquity/bin/ubiquity
InterpreterPath: /usr/bin/python2.7
LiveMediaBuild: Xubuntu 11.04 "Natty Narwhal" - Alpha amd64 (20110201)
ProcCmdline: /usr/bin/python /usr/lib/ubiquity/bin/ubiquity gtk_ui
ProcEnviron: Error: [Errno 13] Permission denied: '/proc/3305/environ'
PythonArgs: ['/usr/lib/ubiquity/bin/ubiquity', 'gtk_ui']
SourcePackage: ubiquity
Title: ubiquity crashed with TypeError in changed(): value is of wrong type for this column
Traceback:
 Traceback (most recent call last):
   File "/usr/lib/ubiquity/plugins/ubi-timezone.py", line 130, in changed
     loc.latitude, loc.longitude])
 TypeError: value is of wrong type for this column
UserGroups:

[Ronald McCollam (fader)]

This behavior also occurs in non-live mode.

[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 #702898, 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.