Install of 12.04 LTS over previous 12.04 LTS installer crashed

Bug #1193891 reported by William Thomas
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
ubiquity (Ubuntu)
New
High
Unassigned

Bug Description

After having trouble with GRUB 2 not booting anything after installing 12.04, I decided to re-install 12.04.
The installer said it had crashed and I should report a bug.
One of the symptoms was that GRUB RESCUE was reporting an unrecognised filesystem that had booted fine just before the installation (I had checked that it booted my previous 8.04 system so that I knew I had a functioning backout if the 12.04 install should go wrong!).

Make what you will of it, but I wouldn't waste too much time on it - I've already wasted plenty.

How am I supposed to attach the requested files?
Since you already know where they are, why can't you pick them up yourself?

1) The release of Ubuntu you are using, via 'lsb_release -rd' or System -> About Ubuntu - 12.04 LTS
2) The version of the package you are using, via 'apt-cache policy pkgname' or by checking in Software Center - Live DVD
3) What you expected to happen - correct, functioning install
4) What happened instead - installer crashed.

ProblemType: Bug
DistroRelease: Ubuntu 12.04
Package: ubiquity 2.10.16
ProcVersionSignature: Ubuntu 3.2.0-23.36-generic 3.2.14
Uname: Linux 3.2.0-23-generic x86_64
ApportVersion: 2.0.1-0ubuntu5
Architecture: amd64
CasperVersion: 1.315
Date: Sun Jun 23 18:46:28 2013
InstallCmdLine: file=/cdrom/preseed/ubuntu.seed boot=casper initrd=/casper/initrd.lz quiet splash -- maybe-ubiquity
LiveMediaBuild: Ubuntu 12.04 LTS "Precise Pangolin" - Release amd64 (20120425)
ProcEnviron:
 LANGUAGE=en_GB.UTF-8
 TERM=unknown
 PATH=(custom, no user)
 LANG=en_GB.UTF-8
 SHELL=/bin/bash
SourcePackage: ubiquity
UpgradeStatus: No upgrade log present (probably fresh install)

Revision history for this message
William Thomas (william-thomas) wrote :
Revision history for this message
William Thomas (william-thomas) wrote :

Per your request.

Revision history for this message
William Thomas (william-thomas) wrote :

per your request.

Revision history for this message
Ubuntu Foundations Team Bug Bot (crichton) wrote : Traceback

Exception during installation:
Jun 23 17:45:43 ubuntu plugininstall.py: Traceback (most recent call last):
Jun 23 17:45:43 ubuntu plugininstall.py: File "/usr/share/ubiquity/plugininstall.py", line 1735, in <module>
Jun 23 17:45:43 ubuntu plugininstall.py: install.run()
Jun 23 17:45:43 ubuntu plugininstall.py: File "/usr/share/ubiquity/plugininstall.py", line 55, in wrapper
Jun 23 17:45:43 ubuntu plugininstall.py: func(self)
Jun 23 17:45:43 ubuntu plugininstall.py: File "/usr/share/ubiquity/plugininstall.py", line 265, in run
Jun 23 17:45:43 ubuntu plugininstall.py: self.db.progress('SET', self.count)
Jun 23 17:45:43 ubuntu plugininstall.py: File "/usr/lib/python2.7/dist-packages/debconf.py", line 60, in <lambda>
Jun 23 17:45:43 ubuntu plugininstall.py: lambda *args, **kw: self.command(command, *args, **kw))
Jun 23 17:45:43 ubuntu plugininstall.py: File "/usr/lib/python2.7/dist-packages/debconf.py", line 81, in command
Jun 23 17:45:43 ubuntu plugininstall.py: status = int(status)
Jun 23 17:45:43 ubuntu plugininstall.py: ValueError: invalid literal for int() with base 10: ''
Jun 23 17:45:43 ubuntu plugininstall.py:

tags: added: installer-crash
Changed in ubiquity (Ubuntu):
importance: Undecided → High
Revision history for this message
Brian Murray (brian-murray) 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 1152399, 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.

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.