Installer Crashed During Fresh Install of 14.04.1

Bug #1366416 reported by Nick W
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
ubiquity (Ubuntu)
Invalid
Undecided
Unassigned

Bug Description

Conducting a fresh dual boot install under guidance of @Kansasnoob.

Back story and details in Ubuntu Forums here:

http://ubuntuforums.org/showthread.php?t=2242245&page=6

ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: ubiquity 2.18.8
ProcVersionSignature: Ubuntu 3.13.0-32.57-generic 3.13.11.4
Uname: Linux 3.13.0-32-generic i686
NonfreeKernelModules: wl
ApportVersion: 2.14.1-0ubuntu3.2
Architecture: i386
CasperVersion: 1.340
Date: Sat Sep 6 22:38:46 2014
InstallCmdLine: file=/cdrom/preseed/ubuntu.seed boot=casper initrd=/casper/initrd.lz quiet splash -- maybe-ubiquity
LiveMediaBuild: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release i386 (20140722.2)
ProcEnviron:
 LANGUAGE=en_GB.UTF-8
 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
Nick W (wattjnick) wrote :
Revision history for this message
Erick Brunzell (lbsolost) wrote :

Looks similar to bug #1044904 but that was in Precise.

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

Possible upstream bug?

https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=726055

But since that was fixed may we have a regression????

Revision history for this message
Phillip Susi (psusi) wrote :

Please run the check disc and memory test options from the boot menu. Let the memory test run for at least 15 minutes ( it will keep testing until you stop it ). Let us know if either find a problem.

Changed in ubiquity (Ubuntu):
status: New → Incomplete
Revision history for this message
Paul White (paulw2u) wrote :

This issue has sat with a status of 'Incomplete' for over eight years without any response from the reporter so it is being closed as 'Invalid'.

Please feel free to re-open this bug report if this is still an issue when using a currently supported release of Ubuntu and tell us in which release you still experience this issue.

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