ubiquity crashed with ValueError in command(): invalid literal for int() with base 10: ''

Bug #1012906 reported by Angel Navas on 2012-06-13
This bug report is a duplicate of:  Edit Remove
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
ubiquity (Ubuntu)
Undecided
Unassigned

Bug Description

Estaba instalando en un equipo con pentium 4 y con una instalación de XP pro, cuando me ha dado el error.

ProblemType: Crash
DistroRelease: Ubuntu 12.04
Package: ubiquity 2.10.4
ProcVersionSignature: Ubuntu 3.2.0-20.33-generic-pae 3.2.12
Uname: Linux 3.2.0-20-generic-pae i686
ApportVersion: 1.95-0ubuntu1
Architecture: i386
CasperVersion: 1.312
Date: Wed Jun 13 23:15:48 2012
ExecutablePath: /usr/lib/ubiquity/bin/ubiquity
InstallCmdLine: BOOT_IMAGE=/ubuntu/install/boot/vmlinuz debian-installer/custom-installation=/ubuntu/install/custom-installation iso-scan/filename=/ubuntu/install/installation.iso automatic-ubiquity noprompt quiet splash boot=casper ro debian-installer/locale=es_ES.UTF-8 keyboard-configuration/layoutcode=es keyboard-configuration/variantcode= -- rootflags=sync
InterpreterPath: /usr/bin/python2.7
LiveMediaBuild: Ubuntu 12.04 LTS "Precise Pangolin" - Beta i386 (20120328)
ProcCmdline: /usr/bin/python /usr/lib/ubiquity/bin/ubiquity --automatic --only
ProcEnviron: Error: [Errno 13] Permiso denegado: '/proc/4371/environ'
PythonArgs: ['/usr/lib/ubiquity/bin/ubiquity', '--automatic', '--only']
SourcePackage: ubiquity
Title: ubiquity crashed with ValueError in command(): invalid literal for int() with base 10: ''
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups:

Angel Navas (garay-n-a) wrote :
tags: removed: need-duplicate-check
Robert Roth (evfool) wrote :

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 #661347, 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. Feel free to continue to report any other bugs you may find.

C de-Avillez (hggdh2) on 2012-07-21
visibility: private → public
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers