Ubuntu
ubiquity package

Installer crashed

Bug #53876 reported by Maarten Vis
16
This bug affects 3 people
Affects Status Importance Assigned to Milestone
ubiquity (Ubuntu)
Invalid
Undecided
Unassigned

Bug Description

I am installing Ubuntu 6.06 on my laptop.
The laptop has a builtin harddisk and a
Western Digital external USB2 harddisk.
I am trying to create a 30000 MB partition on
the WD USB harddisk.

During the process of applying the changes, the
system reports it is trying to do something on a
"busy" disk and cannot continue.

Eventually I get an "installer crashed" message and
are requested to send you some files. This I cannot,
That laptop is not yet on the net.

Here follows the Traceback (most recent call last)
  File: "usr/lib/python2.4/site-packages/ubiquity/gtkui.py, line 696, in on_next_clicked
     gtk.main_quit()
RuntimeError: called outside of mainloop

I get the suggestion to reboot the laptop, which I will.
Thanks,
Maarten Vis
Leidschendam, The Netherlands

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
Maarten Vis (maarten-vis) wrote : Re: [Bug 53876] Re: Installer crashed

Hi,
I cannot attach anything yet as the system is:
a. not installed, due to the installer crash, and
b. is therefore not on the network.

I have advanced some, but Ubuntu does not want to
be installed. My HW is an IBM Thinkpad R50e. It has
an external Western Digital HD attached (USB2).

Initially I tried to install on that drive, but that gave me
the installer crash. The installer did however create
partitions on that external HD!!

I then decided maybe it was the external HD that Ubuntu
did not like, but I have also heard that for these drives
one should modify the system BIOS for some USB2 options.
Wish I knew which ones and what for.

I then created some room on the internal PC harddrive and
created a EXT3 partition. Started an Ubuntu re-install. The
installer now gave me hell as I had not told it where to
put a SWAP partition. So added that an reinstalled. I can specify
where to install but the installer invariably ends with the
message: unable to install file system.

Something in Windows (XP-SP2) may well interfere with things,
but I have installed other distro's before (Mandrake and Suse 9)
and never had any problems installing on a system with Windows XP
on it.

I am giving up on Ubuntu, I think......
Regards,
Maarten Vis

John Vivirito schreef:
> 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 (Ubuntu)
> Status: Unconfirmed => Needs Info
>
>

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

Dont give up on a distro just because of a single bug. If you want to install ubuntu please download and burn the alternative cd and install from that. Im going to close this bug due to lack of info to diagnose this issue you are having. Please feel free to reopen it if you have more information. You can obtain the Alternative cd from http://www.ubuntu.com/download.

Changed in ubiquity:
status: Needs Info → Rejected
Revision history for this message
Dennis Kaarsemaker (dennis) wrote : Re: [Bug 53876] Installer crashed

From https://wiki.ubuntu.com/DapperReleaseNotes/UbiquityKnownIssues

[fixed in Edgy Knot 1] Crash with certain kinds of disk attached:

Disks with non-ASCII (and non-UTF-8) model names cause the installer to
crash while initialising the automatic partitioner. This seems to be
particularly common with USB drives; removing them during the
installation may work around this problem.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.
Subscribing...

Other bug subscribers

Remote bug watches

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