X to Y upgrade fails with gconf2 depends on python3:any; however: Package python3 is not configured yet.

Bug #1611256 reported by Victor gonzalez on 2016-08-09
60
This bug affects 12 people
Affects Status Importance Assigned to Milestone
gconf2 (Ubuntu)
Critical
Dimitri John Ledkov
ubuntu-release-upgrader (Ubuntu)
Critical
Unassigned

Bug Description

Enviroment: Ubuntu 16.04 Xenial http://cdimage.ubuntu.com/daily-live/current/

HW: Toshiba portege Z30-A12T | Intel i5+intel graphics | SSD hd

Preconditions: Xenial xerus updated, internet connection, some packages installed(gparted,preload)

Steps to reproduce:

1º Open terminal and run update-manager -cd
2º Then packages start to fail and report the user that X package can't be installed and it could be not functional, however the upgrading process continues

Current result: Many packages fail during upgrading process from xenial to yakketty

Expected result: No package failures during installation

Add info: screenshot attached as example of package failure

ProblemType: Bug
DistroRelease: Ubuntu 16.10
Package: ubuntu-release-upgrader-core 1:16.10.3
ProcVersionSignature: Ubuntu 4.4.0-34.53-generic 4.4.15
Uname: Linux 4.4.0-34-generic x86_64
ApportVersion: 2.20.3-0ubuntu5
Architecture: amd64
CrashDB: ubuntu
CurrentDesktop: Unity
Date: Tue Aug 9 09:40:07 2016
InstallationDate: Installed on 2016-08-09 (0 days ago)
InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Beta amd64 (20160806)
PackageArchitecture: all
SourcePackage: ubuntu-release-upgrader
Symptom: ubuntu-release-upgrader
UpgradeStatus: Upgraded to yakkety on 2016-08-09 (0 days ago)
VarLogDistupgradeTermlog:

description: updated

@jibel here it is

Jean-Baptiste Lallement (jibel) wrote :

Thanks, unfortunately the file is truncated and doesn't contain the error with gconf2.

Changed in ubuntu-release-upgrader (Ubuntu):
status: New → Incomplete
Max Brustkern (nuclearbob) wrote :

Here are logs from an automated upgrade test.

Jean-Baptiste Lallement (jibel) wrote :

@Max, thanks for the logs. term.log is truncated again and from main.log it's another failure. I'm afraid we'll have to reproduce manually and investigate a live system.

Jean-Baptiste Lallement (jibel) wrote :

From the duplicate the error is an issue with the order of upgrade of the dependencies of gconf2:

dpkg: dependency problems prevent processing triggers for gconf2:
 gconf2 depends on python3:any; however:
  Package python3 is not configured yet.

dpkg: error processing package gconf2 (--configure):
 dependency problems - leaving triggers unprocessed

Changed in ubuntu-release-upgrader (Ubuntu):
importance: Undecided → Critical
status: Incomplete → Confirmed
summary: - yakkety upgrade from xenial causes many package failures
+ X to Y upgrade fails with gconf2 depends on python3:any; however:
+ Package python3 is not configured yet.
tags: added: rls-y-incoming
Launchpad Janitor (janitor) wrote :

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

Changed in gconf2 (Ubuntu):
status: New → Confirmed
Changed in gconf2 (Ubuntu):
importance: Undecided → Critical
assignee: nobody → Dimitri John Ledkov (xnox)
tags: added: xenial2yakkety

This bug badly botched a few upgrades of mine...

pullasuti (pullasuti) wrote :

Yup, just broke my system too. Any way to bypass this mess without a reinstall?

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

Duplicates of this bug

Other bug subscribers