Installer crashes at 'Prepare mount points' (gtk.main_quit)

Bug #55919 reported by lpd
4
Affects Status Importance Assigned to Milestone
ubiquity (Ubuntu)
Invalid
Undecided
Unassigned

Bug Description

Ubuntu 6.06 distribution. I had pre-partitioned the disk, and installed Ubuntu 5.10 on it by mistake (mislabeled CD). Partitions are:

1 NTFS
2 /
3 swap
(4 extended)
5 /usr
6 /tmp
7 /var
8 /home

The installer finds all of these correctly, although it doesn't seem to have access to their labels (assigned with PartitionMagic).

/var/log/installer/version says "ubiquity 1.0.12". /var/log/installer/syslog is too large to copy by hand, and since the network hasn't been configured yet, I can't FTP it to another machine. The last few lines are:

Fri, 11 Aug 2006 11:33:43 INFO Step_after = stepPartAdvanced
Error reading inode 20037
Error reading inode 31688
dumpe2fs 1.38 (30-Jun-2005)
dumpe2fs 1.38 (30-Jun-2005)
dumpe2fs 1.38 (30-Jun-2005)
dumpe2fs 1.38 (30-Jun-2005)
dumpe2fs 1.38 (30-Jun-2005)
Warning: Unable to open /dev/hdc read-write (Read-only file system). /dev/hdc has been opened as read-only.
Error: Unable to open /dev/hdc - unrecognised disk label.
Fri, 11 Aug 2006 11:47:58 INFO Step_before = stepPartAdvanced
Fri, 11 Aug 2006 11:48:10 INFO switched to page stepPartMountpoints
Fri, 11 Aug 2006 11:48:11 INFO Step_after = stepPartMountpoints
Exception in GTK frontend (invoking crash handler):
<<traceback as below>>

Here's the contents of the error window:

Traceback (most recent call last):

  File "/usr/lib/python2.4/site-packages/ubiquity/frontend/gtkui.py", line 696, in on_next_clicked
      gtk.main_quit()
RuntimeError: called outside of a mainloop

The "Installer crashed" window overlays most of a window labeled "Prepare mount points", and what I can see of it seems to suggest that the installer was close to asking me how to map the partitions to mount points.

I've run the install process 3 times, with the same result each time.

Since 5.10 doesn't have a driver that works with the Radeon RS480, if I can't get 6.06 installed, my brand-new laptop is a boat anchor. Please treat this as serious. Thanks.

Revision history for this message
John Vivirito (gnomefreak) wrote :

Could you please attach /var/log/installer/syslog, /var/log/syslog, and /var/log/partman to this bug, using the "Add Attachment" link on the bug's web page? Thanks in advance.

Changed in ubiquity:
status: Unconfirmed → Needs Info
Revision history for this message
lpd (lpd-major2nd) wrote : Re: [Bug 55919] Re: Installer crashes at 'Prepare mount points'

> Could you please attach /var/log/installer/syslog, /var/log/syslog, and
> /var/log/partman to this bug, using the "Add Attachment" link on the bug's
> web page? Thanks in advance.

Um.. you'll have to tell me how to configure the network manually so that I
can scp them off the machine (pelican) on which I was trying to install.
The machine is on a firewalled Ethernet that uses manually assigned 10.0.0.x
addresses: there are other machines on the net that I can reach with scp,
but I'll have to use a terminal window on pelican to get it to talk to them
somehow.

I used route(8) to tell pelican that it can reach 10.0.0.0 netmask
255.255.255.0 through eth0, but that didn't do the trick, and I'm at the
limit of my understanding of this stuff.

Thanks -

L. Peter Deutsch
<email address hidden>

Revision history for this message
lpd (lpd-major2nd) wrote :

> Could you please attach /var/log/installer/syslog, /var/log/syslog, and
> /var/log/partman to this bug, using the "Add Attachment" link on the bug's
> web page? Thanks in advance.

Please tell me how to use a terminal window to configure the network so that
I can scp these files to another machine, or alternatively get out to the
Internet. The machine's address is 10.0.0.10, the Internet gateway address
is 10.0.0.200, and the netmask is 255.255.255.0.

Thanks -

L. Peter Deutsch
<email address hidden>

Revision history for this message
Colin Watson (cjwatson) wrote :

Sorry, I didn't see your question earlier. The easiest way is to edit /etc/network/interfaces, add a static iface stanza (see 'man interfaces' for an example), and type 'sudo ifup eth0 down; sudo ifup eth0 up'.

Anyway, it's sort of irrelevant in this case, as I'm going to treat this as a duplicate of bug 54163, which I'll soon have fixed in Edgy. I believe that the workaround is to avoid hitting the back and/or next buttons more than once in quick succession.

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

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

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.