ubiquity crashed with TypeError in partman_edit_dialog()

Bug #495105 reported by Koen Verweij
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
ubiquity (Ubuntu)
New
Undecided
Unassigned

Bug Description

Binary package hint: ubiquity

I just tried a daily-live image of Lucid of yesterday (9 December). When I try to manually set the partitions it just gets stuck and when I close it this crash report appeared.

ProblemType: Crash
Architecture: amd64
Date: Thu Dec 10 17:03:55 2009
DistroRelease: Ubuntu 10.04
ExecutablePath: /usr/lib/ubiquity/bin/ubiquity
InterpreterPath: /usr/bin/python2.6
LiveMediaBuild: Ubuntu 10.04 "Lucid Lynx" - Alpha amd64 (20091209)
Package: ubiquity 2.1.4
ProcCmdline: /usr/bin/python /usr/lib/ubiquity/bin/ubiquity --only
ProcEnviron: Error: [Errno 13] Permission denied: '/proc/2849/environ'
ProcVersionSignature: Ubuntu 2.6.32-7.10-generic
PythonArgs: ['/usr/lib/ubiquity/bin/ubiquity', '--only']
SourcePackage: ubiquity
Tags: lucid
Title: ubiquity crashed with TypeError in partman_edit_dialog()
Uname: Linux 2.6.32-7-generic x86_64
UserGroups:

Revision history for this message
Koen Verweij (kfverweij) wrote :
Revision history for this message
Apport retracing service (apport) wrote : This bug is a duplicate

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 #494608, 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.

tags: removed: need-duplicate-check
visibility: private → public
Revision history for this message
Koen Verweij (kfverweij) wrote :

Well great, but that other bug report is set to private:
"Sorry, you don't have permission to access this page."

Revision history for this message
Erick Brunzell (lbsolost) wrote :

I don't know why that was set as private. I changed it to public.

Thanks for letting me know.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.