Auto-resize install fails to mount drive

Bug #199129 reported by Henrik Nilsen Omma
6
Affects Status Importance Assigned to Milestone
ubiquity (Ubuntu)
Fix Released
Undecided
Unassigned

Bug Description

Binary package hint: ubiquity

Looks like this is caused by the new PolicyKit setup.

Steps to reproduce:

* Install a copy of Ubuntu, using the whole disk, no LVM
* Install again from the Live CD, and use the auto-resize option

Result:
* You are asked for the admin password to mount the partition (which is confusing if you don't know the password is blank
* On entering the blank password a 'Cannot mount volume' error appears.
* Clicking OK resumes the process though - The resizing progress bar sits for a long time at 50% but does complete. The system then installs successfully

Tags: iso-testing

Related branches

Revision history for this message
Henrik Nilsen Omma (henrik) wrote :
Revision history for this message
Henrik Nilsen Omma (henrik) wrote :
Revision history for this message
Henrik Nilsen Omma (henrik) wrote :
Revision history for this message
Henrik Nilsen Omma (henrik) wrote :
Revision history for this message
Henrik Nilsen Omma (henrik) wrote :
Steve Langasek (vorlon)
Changed in ubiquity:
milestone: none → ubuntu-8.04-beta
Revision history for this message
Colin Watson (cjwatson) wrote :

It shouldn't be trying to mount this at all. GNOME keeps changing this around and breaking ubiquity ...

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

I think hal is doing this (via hal-storage-mount). My conjecture is that hal-disable-polling needs to be called on each drive to turn it off.

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

Could you try running ubiquity as follows:

  hal-lock --interface org.freedesktop.Hal.Device.Storage --exclusive --run ubiquity

... and see if it behaves the same way?

Revision history for this message
Martin Pitt (pitti) wrote :

Something like "sudo hal-lock --interface org.freedesktop.Hal.Device.Storage --exclusive --run /usr/sbin/ubiquity" should help, if we can put that into the desktop file?

Revision history for this message
Martin Pitt (pitti) wrote :

With blocking mounts at the hal level, we can also drop the various nautilus/g-v-m/KIO configuration tweaks.

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

If so, something like this attachment would do the job.

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

It installs fine now, but on completion it does open a nautilus window at /lib/var/OS-prober on the Live file system (other disks are not mounted).

I then tried running ubiquity with

hal-lock --interface org.freedesktop.Hal.Device.Storage --exclusive --run ubiquity

and that works fine as well.

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

This bug was fixed in the package ubiquity - 1.8.0

---------------
ubiquity (1.8.0) hardy; urgency=low

  * Disable the intro message in preparation for Ubuntu 8.04 beta.
  * Run ubiquity under hal-lock if possible (LP: #199129).

 -- Colin Watson <email address hidden> Wed, 19 Mar 2008 15:49:26 +0000

Changed in ubiquity:
status: New → Fix Released
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.