KeyError: "filename './etc/apt/sources.list' not found" during precise desktop installation on a system that already had precise installed.

Bug #1119621 reported by Para Siva on 2013-02-08
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
ubiquity (Ubuntu)
High
Unassigned

Bug Description

The following crash occurred during a precise desktop installation on a system that already had precise installed. The crash occurs with VMs and on hardwares with all three desktop images (20130208 i386,amd64 and amd64+mac)

Feb 8 17:33:39 ubuntu ubiquity: Traceback (most recent call last):
Feb 8 17:33:39 ubuntu ubiquity: File "/usr/bin/apt-clone", line 117, in <module>
Feb 8 17:33:39 ubuntu ubiquity: args.source, args.destination, args.new_distro_codename, protect_installed)
Feb 8 17:33:39 ubuntu ubiquity: File "/usr/lib/python2.7/dist-packages/apt_clone.py", line 327, in restore_state
Feb 8 17:33:39 ubuntu ubiquity: self._restore_sources_list(statefile, targetdir)
Feb 8 17:33:39 ubuntu ubiquity: File "/usr/lib/python2.7/dist-packages/apt_clone.py", line 366, in _restore_sources_list
Feb 8 17:33:39 ubuntu ubiquity: tar.extract(self.TARPREFIX+"etc/apt/sources.list", targetdir)
Feb 8 17:33:39 ubuntu ubiquity: File "/usr/lib/python2.7/tarfile.py", line 2076, in extract
Feb 8 17:33:39 ubuntu ubiquity: tarinfo = self.getmember(member)
Feb 8 17:33:39 ubuntu ubiquity: File "/usr/lib/python2.7/tarfile.py", line 1796, in getmember
Feb 8 17:33:39 ubuntu ubiquity: raise KeyError("filename %r not found" % name)

The steps to reproduce:
(The same as comment #9 on bug 1066347)

1. Install precise (select 'Erase disk and install ubuntu' on the 'Installation type' screen)
2. Finish the installation, reboot and login
3. Do another installation on the same device with NO NETWORK (select 'Something else' on the 'Installation type' screen)
4. 'Change' the existing ext-4 partition to be the root partition of the new installation and leave the others (swap) untouched. Do not format the chaned partition.
5. Continue the installation entering the same username/password used for the previous installation
6. The crash can be observed at the end of the installation.

The logs are attached.

Para Siva (psivaa) wrote :
Para Siva (psivaa) wrote :
Para Siva (psivaa) wrote :
Para Siva (psivaa) wrote :
tags: added: ubiquity-2.10.24
Brian Murray (brian-murray) wrote :

The line numbers in the Traceback correspond to the source code found in apt-clone version 0.2.2ubuntu2 which is the one from -updates not -proposed.

Changed in ubiquity (Ubuntu):
status: New → Incomplete
importance: Undecided → Low
Para Siva (psivaa) wrote :

This bug was reported with no proposed enabled packages. The log with 0.2.2ubuntu3 was attached to bug 1066347 during its precise-proposed verification process. Reattaching the same here for it being of interest.

Changed in ubiquity (Ubuntu):
status: Incomplete → New
Brian Murray (brian-murray) wrote :

Ah, I wonder if this provides a clue:

Feb 8 17:33:39 debconf (filter): <-- ['./VAR/LIB/APT-CLONE/UNAME', './var/lib/apt-clone/installed.pkgs', './var/lib/apt-clone/extended_states', './tmp/tmp.9tvj87PaGa/etc/apt/sources.list', './etc/apt/preferences.d', './etc/apt/trusted.gpg', './etc/apt/trusted.gpg.d', './var/lib/apt-clone/debs']

The file:

'/target/ubiquity-apt-clone/apt-clone-state-ubuntu.tar.gz'

From a system that failed to install / upgrade this way would be helpful.

Launchpad Janitor (janitor) wrote :

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in ubiquity (Ubuntu):
status: New → Confirmed
Changed in ubiquity (Ubuntu):
importance: Low → High
Brian Murray (brian-murray) wrote :

Seems to have occurred as early as ubiquity 2.12.5 and apt-clone version 0.2.3~ubuntu2 see further bug 1065154.

To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers