[Edgy] Desktop CD stalls/hangs when "Install to Disk" is double-clicked

Bug #60897 reported by Aaron Whitehouse
4
Affects Status Importance Assigned to Milestone
ubiquity (Ubuntu)
Invalid
Undecided
Unassigned

Bug Description

I did my best to find this issue already, but there are a lot of bugs with unhelpful descriptions!

I just pulled down the desktop CD for Edgy Knot 3 and tried to install it. It starts up fine, but on double clicking the "Install to Disk" icon, the CD drive spins up and goes mad for about 15 minutes before the system hangs/stalls and I can't even move the mouse.

The installer doesn't start. All that I get is the "Granting Rights" in the bottom toolbar and lots of CD activity - nothing else appears on the screen.

I have a Dell Inspiron 510m (I maintain the page [can't give you the uri because the wiki is down] so you can see my hardware specs there).

I am keen to help you sort this but I won't be able to give you any logs because, once it freezes, I have to power-off and lose all Desktop-CD-related stuff.

I am downloading the alternate CD at the moment and will try that.

Revision history for this message
Aaron Whitehouse (aaron-whitehouse) wrote :

Just for your info, I did try burning the CD again but that did one not work either.

Revision history for this message
Daniel Robitaille (robitaille) wrote :

I have the same problem with my canonical-supplied laptop with Knot-3.. In my case it is a Dell Latitude 110l with 256mb of ram. From what I can see here is that a live session of Edgy on that small amount of ram is really a problem. I gave up on the live-installer after 20 minutes of continous swapping to disk. The only thing visible for me was a blank window which should have become the installer window one day...

And that seems to be the case for other applications as well. It took me over 15 minutes of waiting (and also continous disk swapping) to start firefox and a gnome-terminal in a live session.

Revision history for this message
Aaron Whitehouse (aaron-whitehouse) wrote :

Thanks for your input Daniel. I'm not convinced that it is just a RAM issue (although that is no doubt a factor) because the 6.06.1 Desktop CD works exactly as expected - a little slow but perfectly usable.

Revision history for this message
Aaron Whitehouse (aaron-whitehouse) wrote :

I just downloaded Edgy Beta and the exact same thing happens. It would be great if we could get some kind of fix in before the RC so that I can test it for you. It is not the best look...

Revision history for this message
Aaron Whitehouse (aaron-whitehouse) wrote :

I just tried installing with the Desktop and Alternate CDs for Edgy Release Candidate. It is still the same; the Alternate works but the Desktop just stalls on a double-click.

I reported this early so that I could help test a solution by the final release...

Revision history for this message
Aaron Whitehouse (aaron-whitehouse) wrote :

I just tried installing with the Desktop and Alternate CDs for Edgy Final. It is still the same; the Alternate works but the Desktop just stalls on a double-click.

Revision history for this message
Henrik Nilsen Omma (henrik) wrote :

Hi. Could you try starting ubiquity from the command line and paste in the output here?

sudo ubiquity

How badly does it crash? Can you jump to another virtual terminal and get logs?

Changed in ubiquity:
status: Unconfirmed → Needs Info
Revision history for this message
Aaron Whitehouse (aaron-whitehouse) wrote : Re: [Bug 60897] Re: [Edgy] Desktop CD stalls/hangs when "Install to Disk" is double-clicked

Sorry, I am away on an OE for 7 months so will not be able to do this
until late June. Apologies.

Revision history for this message
Henrik Nilsen Omma (henrik) wrote :

Daniel, are you still seeing this with Edgy final or Feisty?

Revision history for this message
Daniel Robitaille (robitaille) wrote :

Henrik: I currently don't have a Edgy Live CD to test this. But I was going to try to install Feisty Herd 2 using the Live CD once it is out, which I understand will be very soon.

But yesterday I finally upgraded the ram in this laptop from 256mb to 768mb, so I'm hopeful this problem will go away due to the extra ram.

Revision history for this message
Daniel Robitaille (robitaille) wrote :

I tested the installation using the Live CD with Feisty Herd 2, and it worked fine on my laptop. But like I wrote the other day, this laptop now has 768mb of ram instead of 256mb, which may have an effect on this problem.

Revision history for this message
Aaron Whitehouse (aaron-whitehouse) wrote :

Can you please test with Edgy Final (or whatever the last one that
failed with 256MB) and see if it fails with 756MB?

I would imagine that would be a great help in identifying whether the
problem has been fixed or merely avoided. I, unfortunately, can't test
it on 256MB myself as I still am a long way from my machine.

Revision history for this message
Daniel Robitaille (robitaille) wrote :

I tried a Edgy Live instal tonight and it started properly (I didn't complete the installation since I didn't want to reinstall my OS tonight). So going from 256mb to 768mb of ram on this laptop solved the problem in Edgy that I had with both the Live Installer and Firefox.

So in my case all signs seem to point toward the fact that 256mb of ram is not enough to have a LiveCD session that works correctly and let you install from it.

Revision history for this message
Aaron Whitehouse (aaron-whitehouse) wrote :

Okay, so it seems that, between Dapper and Edgy, the RAM requirement
has increased. If this is a general rule then the system requirements
on the download page should probably be increased. If this is just for
our machines then it would be nice to know why...

Revision history for this message
Launchpad Janitor (janitor) wrote :

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

Revision history for this message
Aaron Whitehouse (aaron-whitehouse) wrote :

This works in the Feisty Desktop CD. I will try Gutsy Beta, once it is available.

Revision history for this message
Aaron Whitehouse (aaron-whitehouse) wrote :

It is worth noting that I have two Swap partitions on my testing machine. I understand that Ubiquity uses these if they are available. If that is the case, it is quite possible that Ubiquity wouldn't work on a machine that had only the system requirements listed on the Ubuntu website (256MB RAM).

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.