Ubiquity crashed when "Starting up the partitioner"

I can confirm I have had the same problem.
Motherboard MS 6390
Chipset VIA KM266 and VT8233A/8235

I have installed the beta on one computer with no problems,
but this one, to be dual boot, I have had problems with Gparted, wanting to auto mount the partitions when I select them to delete or format them. It crashes Gparted when I unmount the partitions.
The drive has been partitioned, I am not sure if it has been formatted yet.
All further attempts crash on final install confirmation.

Also noted in the forum thread here http://ubuntuforums.org/showthread.php?t=1281194

About what david said about problems with a dual boot, I can confirm
that the beta installed fine on my laptop with three partitions (/,
swap, /home), but on my desktop I have a dual boot with four
partitions (ext3 with no mount point set, /, swap, /home), and it only
crashed on the desktop machine.

On Sat, Oct 3, 2009 at 9:59 PM, Philip Muskovac <email address hidden> wrote:
> ** Changed in: ubiquity (Ubuntu)
>       Status: New => Confirmed
>
> --
> Ubiquity crashed when "Starting up the partitioner"
> https://bugs.launchpad.net/bugs/441709
> You received this bug notification because you are a direct subscriber
> of the bug.
>

I have this issue on a soltek sl-75kav motherboard. I had chosen to overwrite the entire disk which had Windows only on it. Applied latest motherboard bios and same problem occurred.

Unmarking for retracing for now, broken Dependencies.txt (see last line). Apport should get more robust against this, though, adding apport task.

Can anyone experiencing this bug try the following and report back:

Remove the ubiquity-slideshow-ubuntu package, then attempt an install.

If the install is successful, please boot the live CD a second time so you get the slideshow package back. Go into Preferences -> Software Sources -> Other Software and add "ppa:evand/ppa", then let it reload your configuration. Install libwebkit-1.0-2, then make sure you have the correct version from my ppa. The output of `dpkg -s libwebkit-1.0-2 | grep Version` should be 1.1.15.2-1~evand. Try an install again.

Please let me know via this bug report whether removing the slideshow package fixed the bug, and if so, whether adding the version of webkit from my ppa also fixed the bug.

Thanks!

Removing the slideshow package fixed the bug for me. Couldn't try the webkit upgrade solution, as the version I get with those instructions is not the one mentioned.

Apologies, that should say webkit version 1.1.15.2-1~evand or later. Testing with the latest daily-live CD (http://cdimage.ubuntu.com/daily-live) will have the correct version of webkit.

Removing the slideshow is the faster workaround for this bug.

The release candidate installed without problems so it would appear to be fixed.
Many thanks

Apport retracer crash fixed in trunk r1670.

This bug was fixed in the package apport - 1.10-0ubuntu1

---------------
apport (1.10-0ubuntu1) lucid; urgency=low

  * New upstream release:
    - Add a mode for updating an existing problem report to ui.py
      (-u/--update). This is similar to the Ubuntu specific "apport-collect"
      tool, but implemented the right way now: In particular, this has access
      to the UI and thus can use interactive hooks (LP: #385811) and show you
      what is being sent for confirmation/cancelling (LP: #371827)

    - apport-bug: If invoked as "apport-collect" or "apport-update-bug" (i. e.
      through a symlink), run apport in update mode (-u <number>). This
      provides a convenient no-options command line program. Please note that
      setup.py does not currently install such a symlink. Update the
      apport-bug manpage accordingly.

    - launchpad.py: Use new login_with() to clean up code, and specify allowed
      access levels (WRITE_PRIVATE is the only sensible one anyway).
      (LP: #410205)

    - New hookutils functions:
      + xsession_errors (match lines from ~/.xsession-errors)
      + shared_libraries (determine which libraries a binary links with)
      + links_with_shared_library (test if a binary links with a particular
        library)

    - New CrashDatabase API: get_affected_packages(), can_update(), is_reporter()

    - Rename CrashDatabase.update() to update_traces().

    - Add CrashDatabase.update() for adding all new fields of a report. This is
      primarily useful for collecting local standard and package hook data for an
      already existing bug report which was not filed through Apport. This checks
      can_update()/is_reporter() if the user is eligible for updating that
      particular bug. (LP: #485880)

    - Ignore SIGXCPU and SIGXFSZ; thanks to Kees Cook. (LP: #498074)

    - launchpad.py: Do not mark non-Ubuntu bugs as needs-retrace, since there is
      no retracer right now. (LP: #489794)

    - packaging-apt-dpkg.py, install_retracing_packages(): Do not crash on
      malformed Dependencies.txt lines. (LP: #441709)

    - use-local: Fix for new source tree location of "apport" binary.

  * Drop debian/local/apport-collect{,.1} and install symlinks for apport-bug
    instead.
  * data/general-hooks/ubuntu.py: Do not report "corrupted filesystem tarfile"
    package errors. (LP: #320743)
  * data/general-hooks/ubuntu.py: Report "package ... is already installed and
    configured" errors against dpkg, not the package that failed. (LP: #467688)
 -- Martin Pitt <email address hidden> Sat, 19 Dec 2009 16:48:48 +0100

This bug report is being closed due to the comments regarding this being fixed with an update. For future reference you can manage the status of your own bugs by clicking on the current status in the yellow line and then choosing a new status in the revealed drop down box. You can learn more about bug statuses at https://wiki.ubuntu.com/Bugs/Status . Thank you again for taking the time to report this bug and helping to make Ubuntu better. Please submit any future bugs you may find.