Installer crashes on 13.04. 12.10 works just fine.

Bug #1180538 reported by David Rule
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
ubiquity (Ubuntu)
Expired
Undecided
Unassigned

Bug Description

Installer crashes on 13.04. 12.10 works just fine.

ProblemType: Bug
DistroRelease: Ubuntu 13.04
Package: ubiquity 2.14.6
ProcVersionSignature: Ubuntu 3.8.0-19.29-generic 3.8.8
Uname: Linux 3.8.0-19-generic x86_64
ApportVersion: 2.9.2-0ubuntu8
Architecture: amd64
CasperVersion: 1.331
Date: Wed May 15 16:16:42 2013
InstallCmdLine: file=/cdrom/preseed/ubuntu.seed boot=casper initrd=/casper/initrd.lz quiet splash -- maybe-ubiquity
LiveMediaBuild: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424)
MarkForUpload: True
ProcEnviron:
 TERM=linux
 PATH=(custom, no user)
 LANG=en_US.UTF-8
SourcePackage: ubiquity
UpgradeStatus: No upgrade log present (probably fresh install)

Revision history for this message
David Rule (david-rule) wrote :
Revision history for this message
Ubuntu Foundations Team Bug Bot (crichton) wrote : Traceback

Exception during installation:
May 15 20:10:05 ubuntu /plugininstall.py: Traceback (most recent call last):
May 15 20:10:05 ubuntu /plugininstall.py: File "/usr/share/ubiquity/plugininstall.py", line 1775, in <module>
May 15 20:10:05 ubuntu /plugininstall.py: install.run()
May 15 20:10:05 ubuntu /plugininstall.py: File "/usr/share/ubiquity/plugininstall.py", line 78, in wrapper
May 15 20:10:05 ubuntu /plugininstall.py: func(self)
May 15 20:10:05 ubuntu /plugininstall.py: File "/usr/share/ubiquity/plugininstall.py", line 202, in run
May 15 20:10:05 ubuntu /plugininstall.py: self.configure_apt()
May 15 20:10:05 ubuntu /plugininstall.py: File "/usr/share/ubiquity/plugininstall.py", line 660, in configure_apt
May 15 20:10:05 ubuntu /plugininstall.py: "AptSetup failed with code %d" % ret)
May 15 20:10:05 ubuntu /plugininstall.py: ubiquity.install_misc.InstallStepError: AptSetup failed with code 1
May 15 20:10:05 ubuntu /plugininstall.py:

tags: added: installer-crash
Revision history for this message
Brian Murray (brian-murray) wrote :

May 15 20:10:05 ubuntu ubiquity: open: Input/output error
May 15 20:10:05 ubuntu kernel: [ 2312.404321] EXT4-fs error (device sda1) in ext4_new_inode:946: IO failure
May 15 20:10:05 ubuntu kernel: [ 2312.404431] Aborting journal on device sda1-8.
May 15 20:10:05 ubuntu kernel: [ 2312.404532] EXT4-fs (sda1): Remounting filesystem read-only
May 15 20:10:05 ubuntu kernel: [ 2312.404543] EXT4-fs error (device sda1) in ext4_create:2279: IO failure

That looks like a possible hardware issue.

Revision history for this message
Simon Quigley (tsimonq2) wrote :

Thank you for taking the time to report this bug and helping to make Ubuntu better. We are sorry that we do not always have the capacity to look at all reported bugs in a timely manner. There have been many changes in Ubuntu since that time you reported the bug and your problem may have been fixed with some of the updates. It would help us a lot if you could test it on a currently supported Ubuntu version. If you test it and it is still an issue, kindly upload the updated logs by running only once:
apport-collect 1180538

and any other logs that are relevant for this particular issue.

Changed in ubiquity (Ubuntu):
status: New → Incomplete
Revision history for this message
Launchpad Janitor (janitor) wrote :

[Expired for ubiquity (Ubuntu) because there has been no activity for 60 days.]

Changed in ubiquity (Ubuntu):
status: Incomplete → Expired
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.