Installer crashed

Bug #189193 reported by Graham
14
This bug affects 2 people
Affects Status Importance Assigned to Milestone
ubiquity (Ubuntu)
Invalid
Undecided
Unassigned

Bug Description

Binary package hint: ubiquity

Traceback (most recent call last):
  File "/usr/lib/ubiquity/bin/ubiquity", line 212, in <module>
    main()
  File "/usr/lib/ubiquity/bin/ubiquity", line 209, in main
    install()
  File "/usr/lib/ubiquity/bin/ubiquity", line 65, in install
    ret = wizard.run()
  File "/usr/lib/ubiquity/ubiquity/frontend/gtk_ui.py", line 425, in run
    self.progress_loop()
  File "/usr/lib/ubiquity/ubiquity/frontend/gtk_ui.py", line 776, in progress_loop
    (ret, realtb))
RuntimeError: Install failed with exit code 1
Traceback (most recent call last):
  File "/usr/share/ubiquity/install.py", line 1768, in <module>
    install.run()
  File "/usr/share/ubiquity/install.py", line 342, in run
    self.configure_locales()
  File "/usr/share/ubiquity/install.py", line 800, in configure_locales
    raise InstallStepError("LanguageApply failed with code %d" % ret)
InstallStepError: LanguageApply failed with code 2

------

Revision history for this message
Graham (ubuntu-grahams) wrote :
Revision history for this message
Graham (ubuntu-grahams) wrote :

All logs

Revision history for this message
Graham (ubuntu-grahams) wrote :

I was dong an install in VirtualBox to a physical hard drive

Host OS: WinXP (sp2+virus stuff)
Guest OS: Kubuntu 7.10

This was running a pre-installed Kubuntu

In WinXP I deleted a partition in the WinXP disk management tool to leave the partition from which I was currently running WinXP.
I attached the real HDD to the Kubuntu VM as a primary slave.
Booted Kubuntu VM in VirtualBox
I installed ubiquity package
then ran it up and preceded to install on to the real disc creating a root and swap in the space.

Installer ran OK and created the partitions (I think), but then crashed.

Not a standard install, yes, but I wonder if this is just highlighting a problem with the installer or is it because I am doing a back flip with the installer :-)

Hey Ho.

Revision history for this message
TerryG (tgalati4) wrote :

Definitely edge case. Log files show that Locale directory could not be created, so language settings couldn't be set--ubiquity crashed hard as a result. It could be as simple as a disk permissions problem, but in a Virtual Machine environment with Windows as the Host anything is possible.

I presume that this behavior is repeatable. This edge case should be added to installer documentation as a Known Issue.

Changed in ubiquity:
status: New → Incomplete
Revision history for this message
TerryG (tgalati4) wrote :

Marked as Confirmed to preserve edge use case.

Changed in ubiquity:
status: Incomplete → Confirmed
Revision history for this message
Claes Wallin (clacke) wrote :

I experienced this exact problem, and can shine some light on what's happening.

The bug is: Ubiquity gives an unclear error message. Instead of something cryptic about the internals of the process, it should say "cloop image not found. Please run Ubiquity from the install CD or mount the cloop image on /var/lib/ubiquity/source" or preferable something even less cryptical.

----

I made a temporary install with debootstrap, then installed ubiquity to make the real install, the same staged approach as Original Poster here tried. This because the target computer lacks a CD drive.

The problem is this: Ubiquity expects to be run from the install CD. After formatting partitions it expects to find /cdrom/casper/filesystem.squashfs or equivalent, to mount on /var/lib/ubiquity/source. The next step is to copy the contents of said directory to /target.

If Ubiquity cannot find the CD cloop image in any of the expected locations, it happily continues with an empty /var/lib/ubiquity/source, copies all its non-existing contents to /target, then goes on to customize the copied filesystem. The first thing it does is set the language, by writing /etc/default/locale. Since /etc/default does not exist, the application breaks down at this point, with the error message noted in the bug report.

So, workaround: Don't run ubiquity except from the CD. Or first mount the cloop image on /var/lib/ubiquity/sources. I did the latter, and successfully installed my system. Hopefully by noting this here, the next person to try this will be more lucky when searching for a solution.

Adding a feature request that running ubiquity from outside the install CD should work. I have ideas for this. :-)

   /c

tags: added: ubiquity-1.6.8
tags: added: gutsy
Revision history for this message
Brian Murray (brian-murray) wrote : Traceback

Exception during installation:
Feb 5 09:22:28 graham-desktop python: Traceback (most recent call last):
Feb 5 09:22:28 graham-desktop python: File "/usr/share/ubiquity/install.py", line 1768, in <module>
Feb 5 09:22:28 graham-desktop python: install.run()
Feb 5 09:22:28 graham-desktop python: File "/usr/share/ubiquity/install.py", line 342, in run
Feb 5 09:22:28 graham-desktop python: self.configure_locales()
Feb 5 09:22:28 graham-desktop python: File "/usr/share/ubiquity/install.py", line 800, in configure_locales
Feb 5 09:22:28 graham-desktop python: raise InstallStepError("LanguageApply failed with code %d" % ret)
Feb 5 09:22:28 graham-desktop python: InstallStepError: LanguageApply failed with code 2
Feb 5 09:22:28 graham-desktop python:

tags: added: installer-crash
Revision history for this message
Phillip Susi (psusi) wrote :

Ubiquity is meant to be run from the live cd. If you use debootstrap to get started, then there is no reason to use ubiquity, just apt-get install ubuntu-desktop.

Changed in ubiquity (Ubuntu):
status: Confirmed → Invalid
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.