[Gutsy] installer crashed twice (LiveCD)

Bug #152737 reported by Pjotr12345
6
Affects Status Importance Assigned to Milestone
ubiquity (Ubuntu)
Expired
Medium
Unassigned

Bug Description

The installler of the Gutsy Gibbon LiveCD (daily build of today, October 14) crashed twice.

Once during the scanning of the partitions, after the Settings Migration screen (I didn't select anything in that screen). The second crash was, after installing all the files on the root partition at sda10: then the installer failed to install Grub and simply quit.

Hardware on my laptop:
Intel Pentium D 1700 Mhz
1 GB DDR
Intel wireless card
Intel video card
100 GB hard drive

Revision history for this message
Pjotr12345 (computertip) wrote :

I should add, that this laptop is eminently fit for Linux. So there is nothing wrong with the hardware. It is multi-boot already: in Grub I can boot Ubuntu 6.06, Ubuntu 7.04, Fedora 7, Mandriva 2008 and OpenSUSE 10.3.

Revision history for this message
Evan (ev) wrote :

Can you please run the installer until it crashes using the --debug option (`ubiquity --debug` in a terminal window) and then attach /var/log/syslog and /var/log/installer/debug to this bug report?

Thanks!

Revision history for this message
Pjotr12345 (computertip) wrote :

Here is /var/log/syslog (see attachment). In the next message, I will attach /var/log/installer/debug (how does one attach more than one file?).

This time, I used the daily build of the LiveCD, of today, October 16. Only one crash this time, right at the end (no Grub installed).

Revision history for this message
Pjotr12345 (computertip) wrote :

And here is /var/log/installer/debug.

Revision history for this message
Pjotr12345 (computertip) wrote :

..... and here is the list of my hardware (see attachment).

Revision history for this message
Pjotr12345 (computertip) wrote :

Installation failed again with the final release version of the LiveCD of Ubuntu 7.10 (desktop CD).
During the last phase of the installation, not only ubiquity but the entire LiveCD-session as well, got stuck when the following component was being installed:
"module 'sbp2' for 'Firewire CDROM support' is being loaded"

I had to do a hard reset with the physical power button. Luckily, afterwards I was able to do the installation succesfully with the Alternate CD.

Revision history for this message
Vincent Dekker (dekker-vincent) wrote :

Installation from live cd final version failed on my desktop too. Almost finished (97 % or so) I got the message
   E:DIrectory '/target/var/log/apt/' missing
I hit enter a couple of times, got the message once more, as well as a message that I should maybe download and burn the live cd again and that maybe the installation would fail
but then the installation proceeded and seemed to end nicely.
I did wonder though why Grub didn't ask me anything about my other OS' ses (Win XP and Feisty).
After removing the LiveCD from the pc I restarted.
I got the bootmenu but it was altered in a strange way. I tddid not show a link to Gutsy. It showed the links tot Feisty and one to Win XP.
But: this menu was from the original menu.lst I got when installing Feisty, Shortly after installing Feisty I modified the menu.lst in such a way that Win XP was mention first and would start automatically after 20 seconds. Second came an link to Gutsy Beta and then came the links to Feisty.
Now I checked the menu.lst from Feisty, and indeed, it had been changed to the old original.
So I changed it back again: put Win XP on top and made a link tot Gutsy as second line.
Then I restarted the pc to start Gutsy. But I immediately got the message that a file was not found and Gutsy did not start at all.
So I went back to Feisty to check what could be wrong with the line I added to the menu.lst. The line was okay, but in Feitsy I could see the partitions for Gutsy. They seemed to be missing all together.
Next I started Gparted. There I saw that there were two partitions for Gutsy and that the biggest one had some 2.5 GB of data in it. So the installation must have succeeded almost entirely.

I now consider to reinstall Gutsy beta from a Alternate CD, which worked fine a week ago, and the updating Gutsy beta to the final version.

Another problem I encountered concerns launching the Live CD. Sometimes I get a screen full of colored lines some 30 seconds after starting the Live CD via the first menu option. The CD keeps spinning for 20 seconds or so more and the stops. The pc doesn't respond to anything and all I can do is reset the pc.
Launching the Live CD in safe graphics mode doesn't have this problem.

Revision history for this message
Vincent Dekker (dekker-vincent) wrote :

Sorry, I typed the above somewhat too fast.
please read:
 Then I restarted the pc. I GOT MY OWN MENU AGAIN AND HIT THE SECOND LINE to start Gutsy. But I immediately got the message that a file was not found and Gutsy did not start at all.
And in the next paragraph I forgot the word NOT
 So I went back to Feisty to check what could be wrong with the line I added to the menu.lst. The line was okay, but in Feisty I could NOT see the partitions for Gutsy. They seemed to be missing all together. ( I can see my Windows partitions in Feisty)

Revision history for this message
Vincent Dekker (dekker-vincent) wrote :

Just tried to install from the Live CD for a second time, but got exactly the same result. Including the old Feisty boot menu.

Changed in ubiquity:
importance: Undecided → Medium
status: New → Confirmed
tags: added: ubiquity-1.6.8
tags: added: gutsy
Revision history for this message
Brian Murray (brian-murray) wrote : Traceback

Exception during installation:
Oct 16 18:47:34 ubuntu python: Traceback (most recent call last):
Oct 16 18:47:34 ubuntu python: File "/usr/share/ubiquity/install.py", line 1768, in <module>
Oct 16 18:47:34 ubuntu python: install.run()
Oct 16 18:47:34 ubuntu python: File "/usr/share/ubiquity/install.py", line 397, in run
Oct 16 18:47:34 ubuntu python: self.configure_hardware()
Oct 16 18:47:34 ubuntu python: File "/usr/share/ubiquity/install.py", line 1082, in configure_hardware
Oct 16 18:47:34 ubuntu python: self.set_debconf('popularity-contest/participate', participate)
Oct 16 18:47:34 ubuntu python: File "/usr/share/ubiquity/install.py", line 1745, in set_debconf
Oct 16 18:47:34 ubuntu python: dc = debconf.Debconf(read=dccomm.stdout, write=dccomm.stdin)
Oct 16 18:47:34 ubuntu python: File "/usr/lib/python2.5/site-packages/debconf.py", line 48, in __init__
Oct 16 18:47:34 ubuntu python: self.setUp(title)
Oct 16 18:47:34 ubuntu python: File "/usr/lib/python2.5/site-packages/debconf.py", line 51, in setUp
Oct 16 18:47:34 ubuntu python: self.version = self.version(2)
Oct 16 18:47:34 ubuntu python: File "/usr/lib/python2.5/site-packages/debconf.py", line 60, in <lambda>
Oct 16 18:47:34 ubuntu python: lambda *args, **kw: self.command(command, *args, **kw))
Oct 16 18:47:34 ubuntu python: File "/usr/lib/python2.5/site-packages/debconf.py", line 81, in command
Oct 16 18:47:34 ubuntu python: status = int(status)
Oct 16 18:47:34 ubuntu python: ValueError: invalid literal for int() with base 10: ''
Oct 16 18:47:34 ubuntu python:

tags: added: installer-crash
Revision history for this message
Thomas Hotz (thotz-deactivatedaccount) wrote :

Can you please retest with a supported Ubuntu version? Thank you!

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