Unable to install due to Ubiquity Bug

[tgimmel]

Ubiquity will crash if trying to use multiple partitions and some partitions are not re formatted. It is especially insidious because it fails with no warning and if you try to reboot of course it will not. The system is in a "half installed" state.
This is Ubuntu Bug ID 188976. The Mint developers would be good to fix this before Ubuntu, since it has not been assigned to anyone.

Install log output:

Code: Select all


Crash log from /var/log/installer/debug:
  File "/usr/share/ubiquity/install.py", line 2566, in <module>
    install.run()
  File "/usr/share/ubiquity/install.py", line 353, in run
    self.copy_all()
  File "/usr/share/ubiquity/install.py", line 741, in copy_all
    os.unlink(targetpath)
OSError: [Errno 21] Is a directory: '/target/usr/local/man'

Traceback (most recent call last):
  File "/usr/lib/ubiquity/bin/ubiquity", line 524, in <module>
    main(oem_config)
  File "/usr/lib/ubiquity/bin/ubiquity", line 509, in main
    install(args[0], query=options.query)
  File "/usr/lib/ubiquity/bin/ubiquity", line 242, in install
    ret = wizard.run()
  File "/usr/lib/ubiquity/ubiquity/frontend/gtk_ui.py", line 513, in run
    self.process_step()
  File "/usr/lib/ubiquity/ubiquity/frontend/gtk_ui.py", line 1179, in process_step
    self.progress_loop()
  File "/usr/lib/ubiquity/ubiquity/frontend/gtk_ui.py", line 1062, in progress_l:


Tim

[vincent]

Unfortunately, I don't think the Mint developers take part in the development of Ubiquity. I understand your frustration, but this is not the right place to report a bug about Ubiquity, nor get people to fix it (upstream issues are for the most part, out of our reach), which is why Launchpad exists.

[pbmuk]

I've reported it via Launchpad. So have a lot of people I think. It affects all the Ubuntu derivatives I think:

Public bug reported:

Binary package hint: ubiquity

Crashed installing Linux Mint 9 (Isadora) Gnome 32bit main edition.

Ubiquity crash line 524 main(oem_config)
assert os.path.exists(fs_size), missing filesystem.size assertion error

I was attempting to install Linux Mint 9 as the sole OS onto a system
which was dual boot XP and Mint 8, so I was changing the partition
table. Three attempts with different partition schemes all resulted in
this crash. I cannot attach /var/log/syslog or /var/log/partman as when
I attempted to log on to launchpad immediately after the last crash
Firefox also crashed with no errors reported.

I eventually managed to install Mint 9 by installing Mint 8 with the
partitions I wanted and then replacing Mint 8 with Mint 9 onto the
partition scheme I had already set up.

** Affects: ubiquity (Ubuntu)
Importance: Undecided
Status: New

--
Ubiquity crashes copying system to drive
https://bugs.launchpad.net/bugs/587785

[the_sane_one]

I found out a work around and was about to post it to launchpad, but launchpad is down ATM. So I am posting this here.

I can't upload .py or .txt files So please apply the diff manually.
------------------------------------------------------------------------------------------------------------------------------------------------------------------------


It looks like a straight up bug in /usr/share/ubiquity/install.py, around here --

Code: Select all

        fs_size = os.path.join(self.casper_path, 'filesystem.size')
        assert os.path.exists(fs_size), "Missing filesystem.size."
        with open(fs_size) as total_size_fp:
            total_size = int(total_size_fp.readline())

So what I did was to revert these lines back to older version(see attached file). After that, I was able to proceed with the install. You can replace /usr/share/ubiquity/install.py with the attached version and you can proceed as well(you would need to sudo).

I don't understand why this overcompensation of a fix was necessary with out even basic testing to a crucial functionality(Installing the damn OS!). I would take a slightly longer delay in the installer to a broken installer, thank you very much.


Here is the diff in case any one is interested:

Code: Select all

 681,683d680
<         files = []
<         total_size = 0
<
687,697c684,687
<         walklen = 0
<         for entry in os.walk(self.source):
<             walklen += 1
<         walkpos = 0
<         walkprogress = 0
<
<         for dirpath, dirnames, filenames in os.walk(self.source):
<             walkpos += 1
<             if int(float(walkpos) / walklen * 10) != walkprogress:
<                 walkprogress = int(float(walkpos) / walklen * 10)
<                 self.db.progress('SET', walkprogress)
---
>         fs_size = os.path.join(self.casper_path, 'filesystem.size')
>         assert os.path.exists(fs_size), "Missing filesystem.size."
>         with open(fs_size) as total_size_fp:
>             total_size = int(total_size_fp.readline())
699,709d688
<             sourcepath = dirpath[len(self.source) + 1:]
<
<             for name in dirnames + filenames:
<                 relpath = os.path.join(sourcepath, name)
<                 fqpath = os.path.join(self.source, dirpath, name)
<
<                 total_size += os.lstat(fqpath).st_size
<                 files.append(relpath)
<
<         self.db.progress('SET', 10)
<         self.db.progress('INFO', 'ubiquity/install/copying')

[ravidhingra89]

I'm unable to understand how to apply this diff. Please explain what needs to be done to apply this diff ?? unable to understand which lines to delete and which to add and where exactly in install.py file.

[viking777]

ravidhingra89,

I applaud you wholeheartedly for searching the forum before posting I really wish more people would do so, but in this case adding to a thread that is over 3 years old is not a productive way to proceed.

The chances are that anyone who posted in this thread is no longer active on the forum and that the patch itself would only be relevant to the version of Ubiquity that existed 3 years ago and if applied could actually make things worse instead of better.

Please start your own thread detailing the problems you are having and perhaps someone will be able to help.

The relevant forum rule is this:

Do not resurrect support topics older than 6 months, outdated information can cause issues with newer releases.

In the meantime I will lock this thread.