Ubiquity got stuck at 'Identifying file system...'

After writing the bug report, I tried to shut down the installer window. Then it responded with:

'The installation has finished...'. That info window was a little hard to shut down, but finally it went away. And then there was a good (normal) shutdown sequence. But no system was installed.

This bug has been reported on the Ubuntu ISO testing tracker.

A list of all reports related to this bug can be found here:
http://iso.qa.ubuntu.com/qatracker/reports/bugs/1373365

Trying again, this time directly from Syslinux via 'Install Lubuntu', and formatting the (same) partition: It reached 'Restart' seeming to work well, but it ended at a black screen and I had to press the Enter key to make it restart. Not only was something installed, it was a working Lubuntu Utopic system :-)

So my conclusion so far is that either there are problems installing from the live session, or the installer was not happy with the file system made by gparted.

3rd test:

Trying again, this time again from a live session , and using another partition formatted by gparted: This time it created a working Lubuntu Utopic system :-)

So my conclusion so far is that either there are problems installing from the live session when several other programs has been run (testing that the live session works), or that first particular file system made by gparted was bad. The Ubiquity installer has been very sensitive during several versions, and installation should be done at once, not after running several other programs, particularly with low RAM.

With 4 GB RAM (in this test), there should not be a problem with too low RAM, but maybe zRAM was crowded and caused problems (zRAM is used in Lubuntu's live session).

4th test:

Tried again, this time without swap and zRAM, but running some programs before starting Ubiquity and setting up the root partition for re-formatting. The same thing happened as the first time (or very similar). Stuck at 'Identifying file system...'.

I had htop on, and it showed RAM usage approx 300 MB (of a total of 4 GB) so the computer was not running out of memory.

Just after leaving the partitioning screen the system complained that it could not shut off the swap. But I had already done it manually (including zRAM).

It seems that Ubiquity is happy only when it is allowed to run first (not after other programs have been running).

I can turn swap on and off manually (in the same live session after the install failure in the 4th test). And I can mount and unmount the target device for the root file system (manually with mount and umount).

But for some reason Ubiquity has problems.

I was asked to change the severity from a red bug to a grey bug (and did so) because far nobody else has been affected by this bug.

5th test

http://www.toshiba.se/laptops/satellite-pro/c850/satellite-pro-c850-19w/

6th test

http://www.asus.com/Motherboards/M2NVM_DVI/

I found the problem:

A program tested before ubiquity left cruft in /etc/mtab, which was not seen by df, and not affecting terminal window commands (umount and swapoff), but it was affecting ubiquity. This is a very special case.

Running various programs, and checking that /etc/mtab is clean (matching the output of df), makes it possible to install into this same computer (as in tests #1-4) with a USB 3 HDD, as well as installing into another computer's internal HDD.

So we can give this bug very low priority.

Thank you for taking the time to report this bug and helping to make Ubuntu better. We are sorry that we do not always have the capacity to look at all reported bugs in a timely manner. There have been many changes in Ubuntu since that time you reported the bug and your problem may have been fixed with some of the updates. It would help us a lot if you could test it on a currently supported Ubuntu version. If you test it and it is still an issue, kindly upload the updated logs by running only once:
apport-collect https://api.launchpad.net/1.0/bugs/1373365

and any other logs that are relevant for this particular issue.

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