ubiquity crashed with ValueError in command()

Bug #617646 reported by Kenny Strawn
This bug report is a duplicate of:  Bug #617729: ubi-partman failed with exit code 141. Edit Remove
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
ubiquity (Ubuntu)
New
Undecided
Unassigned

Bug Description

Binary package hint: ubiquity

This bug was in the Maverick Meerkat, not Lucid, Karmic, Feisty, Intrepid, or any of the other versions this bug showed up in.

Oh, and just to let you know: I can duplicate this bug by pressing Alt+F2 and typing 'gksu ubiquity'.

ProblemType: Crash
DistroRelease: Ubuntu 10.10
Package: ubiquity 2.3.5 [modified: lib/partman/automatically_partition/question]
ProcVersionSignature: Ubuntu 2.6.35-14.20-generic 2.6.35
Uname: Linux 2.6.35-14-generic i686
Architecture: i386
Date: Fri Aug 13 16:00:06 2010
ExecutablePath: /usr/lib/ubiquity/bin/ubiquity
InterpreterPath: /usr/bin/python2.6
LiveMediaBuild: Ubuntu 10.10 "Maverick Meerkat" - Alpha i386 (20100812)
ProcCmdline: /usr/bin/python /usr/lib/ubiquity/bin/ubiquity
ProcEnviron: Error: [Errno 13] Permission denied: '/proc/6008/environ'
PythonArgs: ['/usr/lib/ubiquity/bin/ubiquity']
SourcePackage: ubiquity
Title: ubiquity crashed with ValueError in command()
UserGroups:

Revision history for this message
Kenny Strawn (realkstrawn93) wrote :
visibility: private → public
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.