Ubuntu
ubiquity package

installation program crash on step "identify file for deleting"

Bug #815530 reported by Thilo Deist on 2011-07-24

This bug report is a duplicate of: Bug #743359: Installer: LockFailedException: Failed to lock /target/var/cache/apt/archives/lock. Edit Remove

This bug affects 1 person

Affects		Status	Importance	Assigned to	Milestone
	ubiquity (Ubuntu)	Confirmed	Undecided	Unassigned

Bug Description

Installation failed with following exeption (sorry for German only):

"Installationsprogramm abgestürzt

Leider ist die Installation fehlgeschlagen.
Bitte melden Sie diesen Fehler unter https:launchpad.net/ubuntu/+source/ubiquity/+filebug (als einen neuen Fehlerbericht)
und ein Entwicker wird sich so bald wie möglich diesem annehmen.
Zur besseren Fehleranalyse geben Sie bitte folgende Informationen an und fügen die Dateien >>/var/log/syslog<< sowie >>/var/log/partman<< dem Bericht hinzu"

The error accurs when the installation progam tries to identify files which can be deleted.

lsb_release -rd
Description: Ubuntu 11.04
Release: 11.04

apt-cache policy ubiquity
ubiquity:
  Installiert: 2.6.10
  Kandidat: 2.6.10
  Versionstabelle:
*** 2.6.10 0
        500 cdrom://Ubuntu 11.04 _Natty Narwhal_ - Release amd64 (20110427)/ natty/main amd64 Packages
        500 http://archive.ubuntu.com/ubuntu/ natty/main amd64 Packages
        100 /var/lib/dpkg/status

Tags:

Revision history for this message

Thilo Deist (deist) wrote on 2011-07-24:

logs.tar Edit (470.0 KiB, application/x-tar)

Revision history for this message

Thilo Deist (deist) wrote on 2011-07-24:

both graphical installations failed.
Installion using the text based installion works.

Brian Murray (brian-murray) on 2011-07-28

tags:	added: ubiquity-2.6.10
tags:	added: natty

Revision history for this message

Brian Murray (brian-murray) wrote on 2011-08-02: Traceback

Exception during installation:
Jul 24 17:52:07 ubuntu plugininstall.py: Traceback (most recent call last):
Jul 24 17:52:07 ubuntu plugininstall.py: File "/usr/share/ubiquity/plugininstall.py", line 1547, in <module>
Jul 24 17:52:07 ubuntu plugininstall.py: install.run()
Jul 24 17:52:07 ubuntu plugininstall.py: File "/usr/share/ubiquity/plugininstall.py", line 56, in wrapper
Jul 24 17:52:07 ubuntu plugininstall.py: func(self)
Jul 24 17:52:07 ubuntu plugininstall.py: File "/usr/share/ubiquity/plugininstall.py", line 208, in run
Jul 24 17:52:07 ubuntu plugininstall.py: self.remove_extras()
Jul 24 17:52:07 ubuntu plugininstall.py: File "/usr/share/ubiquity/plugininstall.py", line 1303, in remove_extras
Jul 24 17:52:07 ubuntu plugininstall.py: self.do_remove(regular)
Jul 24 17:52:07 ubuntu plugininstall.py: File "/usr/share/ubiquity/plugininstall.py", line 923, in do_remove
Jul 24 17:52:07 ubuntu plugininstall.py: if not cache.commit(fetchprogress, installprogress):
Jul 24 17:52:07 ubuntu plugininstall.py: File "/usr/lib/python2.7/dist-packages/apt/deprecation.py", line 98, in deprecated_function
Jul 24 17:52:07 ubuntu plugininstall.py: return func(*args, **kwds)
Jul 24 17:52:07 ubuntu plugininstall.py: File "/usr/lib/python2.7/dist-packages/apt/cache.py", line 433, in commit
Jul 24 17:52:07 ubuntu plugininstall.py: res = self._fetch_archives(fetcher, pm)
Jul 24 17:52:07 ubuntu plugininstall.py: File "/usr/lib/python2.7/dist-packages/apt/cache.py", line 279, in _fetch_archives
Jul 24 17:52:07 ubuntu plugininstall.py: raise LockFailedException("Failed to lock %s" % lockfile)
Jul 24 17:52:07 ubuntu plugininstall.py: LockFailedException: Failed to lock /target/var/cache/apt/archives/lock
Jul 24 17:52:07 ubuntu plugininstall.py:

tags:

added: installer-crash

Revision history for this message

Brian Murray (brian-murray) wrote on 2011-08-03:

Thank you for taking the time to report this bug and helping to make Ubuntu better. This particular bug has already been reported and is a duplicate of bug 743359, so it is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Please continue to report any other bugs you may find.