Installation hangs after pressing "forward" button on "Preparing installation" page

Bug #694041 reported by thebravoman
22
This bug affects 3 people
Affects Status Importance Assigned to Milestone
ubiquity (Ubuntu)
Expired
Undecided
Unassigned

Bug Description

Binary package hint: ubiquity

I have a new Dell Studio XPS with windows 7 installed.
I have downloaded ubuntu 10.10 and burned on a DVD. Then reboot and starting the installation process.
I choose the language.
Then on the "Preparing installation" page when I press forward the installation hangs.
The problem is repeatable. I have tried in for 4-5 times.

ProblemType: Bug
DistroRelease: Ubuntu 10.10
Package: ubiquity 2.4.8
ProcVersionSignature: Ubuntu 2.6.35-22.33-generic 2.6.35.4
Uname: Linux 2.6.35-22-generic x86_64
Architecture: amd64
Date: Fri Dec 24 07:56:47 2010
LiveMediaBuild: Ubuntu 10.10 "Maverick Meerkat" - Release amd64 (20101007)
ProcEnviron:
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SourcePackage: ubiquity

Revision history for this message
thebravoman (thebravoman) wrote :
Revision history for this message
Julian Taylor (jtaylor) wrote :

I have the same problem but I it only occurs if my external hard disk is connected.
When I unplug it, the installer continues to the next screen.

dmesg of disk connection:

[ 402.455619] firewire_core: phy config: card 0, new root=ffc1, gap_count=5
[ 403.003720] scsi10 : SBP-2 IEEE-1394
[ 403.004204] scsi11 : SBP-2 IEEE-1394
[ 403.004335] firewire_core: created device fw1: GUID 0090a90b7648d1b7, S400
[ 403.958545] firewire_sbp2: fw1.0: logged in to LUN 0000 (0 retries)
[ 403.976073] scsi 10:0:0:0: Direct-Access WD My Book 1028 PQ: 0 ANSI: 4
[ 403.976566] sd 10:0:0:0: Attached scsi generic sg7 type 0
[ 403.982943] sd 10:0:0:0: [sdg] 625142448 512-byte logical blocks: (320 GB/298 GiB)
[ 403.986950] sd 10:0:0:0: [sdg] Write Protect is off
[ 403.986960] sd 10:0:0:0: [sdg] Mode Sense: 10 00 00 00
[ 403.990268] sd 10:0:0:0: [sdg] Cache data unavailable
[ 403.990276] sd 10:0:0:0: [sdg] Assuming drive cache: write through
[ 404.019052] sd 10:0:0:0: [sdg] Cache data unavailable
[ 404.019060] sd 10:0:0:0: [sdg] Assuming drive cache: write through
[ 404.093715] sdg: sdg1 sdg2
[ 404.357572] sd 10:0:0:0: [sdg] Cache data unavailable
[ 404.357580] sd 10:0:0:0: [sdg] Assuming drive cache: write through
[ 404.357588] sd 10:0:0:0: [sdg] Attached SCSI disk
[ 407.386605] firewire_sbp2: fw1.1: logged in to LUN 0001 (0 retries)
[ 407.525494] scsi 11:0:0:1: Enclosure WD My Book Device PQ: 0 ANSI: 4

Revision history for this message
Julian Taylor (jtaylor) wrote :
Revision history for this message
Julian Taylor (jtaylor) wrote :

forgot to mention I'm using ubiquity Version: 2.5.22 from the Mar 02:00 AM daily build

Revision history for this message
Eliah Kagan (degeneracypressure) wrote :

@Julian
It looks like two similar bugs (bug 732257 and bug 729870) may no longer be reproducible. Is this bug still reproducible on Natty (with the latest daily-live)? If so, it would be good for you to furnish more information, and add the natty tag. If not, please still reply--it would be good to have it documented that this is (currently) a Maverick-only bug.

Also, please note that, in Natty, you might actually have experienced bug 729394, which has been fixed. Those two bugs mentioned above are probably themselves duplicates of bug 729394.

Revision history for this message
Julian Taylor (jtaylor) wrote :

I failed to notice that this was a maverick report.
my problem was in natty and it was fixed with 729394.

Revision history for this message
Eliah Kagan (degeneracypressure) wrote :

@thebravoman (and anyone else affected by this bug in Maverick)
A recent support request (https://answers.launchpad.net/ubuntu/+source/ubiquity/+question/151136) in which someone suffered from the same symptoms as this bug makes me wonder if this is a bug at all (in Maverick, I mean--the similar bug in Natty certainly was real), or if it's a result of a bad .iso or bad burn. Can you take a look at the question linked-to above, and see if the solution that worked there is effective at eliminating your problem, as well (enabling the installation of Ubuntu 10.10 Maverick)? The instructions there that pertain to the creation and testing of the USB flash drive also pertain to the creation and testing of an installation CD or DVD (and I would add to them, that the installation CD/DVD should be burned as slowly as possible, to reduce the chance of errors).

tags: added: ubiquity-2.4.8
Revision history for this message
Eliah Kagan (degeneracypressure) wrote :

Since no one has responded as to whether or not this is reproducible when the install .iso image is MD5 tested and the burned CD/DVD or written USB flash drive is verified (by pressing Spacebar when the person and keyboard icons appear at the bottom center of the screen during boot, selecting your language, and selecting "Check disc for errors"), there is currently no strong reason to think there is necessarily any bug here at all. Therefore, this is probably not suitable to be worked on by a developer until that information is provided, so I'm changing this bug's status from New to Incomplete.

If anyone affected by this bug can confirm that it still occurs after performing those tests, please post here about that. In that case, the status can be changed from Incomplete back to New. If everyone can report that the problem goes away when using an installation .iso image that passes an MD5 test and verified installation media, then this bug can be marked Invalid. Otherwise, I think this bug can simply be allowed to expire (change status to Expired), as will automatically happen after it is Incomplete for an extended time.

Also, if anybody is experiencing this on Natty or Oneiric, and think that this bug report better describes it than other bug reports you have found, please post about that.

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

Related questions

Remote bug watches

Bug watches keep track of this bug in other bug trackers.