Ubuntu
ubuntu-release-upgrader package

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

Bug #1611256 reported by Victor gonzalez
60
This bug affects 12 people
Affects Status Importance Assigned to Milestone
gconf2 (Ubuntu)
Invalid
Critical
Dimitri John Ledkov
ubuntu-release-upgrader (Ubuntu)
Invalid
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:

See original description
Revision history for this message
Victor gonzalez (victor-gonzalez-0) wrote :
description: updated
Revision history for this message
Victor gonzalez (victor-gonzalez-0) wrote :

@jibel here it is

Revision history for this message
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
Revision history for this message
Max Brustkern (nuclearbob) wrote :

Here are logs from an automated upgrade test.

Revision history for this message
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.

Revision history for this message
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.
Brian Murray (brian-murray)
tags: added: rls-y-incoming
Revision history for this message
Launchpad Janitor (janitor) wrote :

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

Changed in gconf2 (Ubuntu):
status: New → Confirmed
Dimitri John Ledkov (xnox)
Changed in gconf2 (Ubuntu):
importance: Undecided → Critical
assignee: nobody → Dimitri John Ledkov (xnox)
Ubuntu Foundations Team Bug Bot (crichton)
tags: added: xenial2yakkety
Revision history for this message
Emilio Jesús Gallego Arias (e+launchpad) wrote :

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

Revision history for this message
pullasuti (pullasuti) wrote :

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

Mathieu Trudel-Lapierre (cyphermox)
tags: added: rls-bb-incoming
removed: rls-y-incoming
Revision history for this message
Brian Murray (brian-murray) wrote :

I tested an upgrade from Ubuntu 16.04 to Ubuntu 18.04 today with the packages gconf2, gparted, preload among others installed. The upgrade completed successfully and there were no issues with triggers looping. I believe this is the result of a new version of dpkg which is available in Ubuntu 16.04.

dpkg (1.18.4ubuntu1.6) xenial; urgency=medium

  * Cherry-pick upstream fixes for trigger loops (LP: #1828639)
    - dpkg: Negate tortoise_not_in_hare() function name and return value
    - dpkg: Initialize trigcyclenode's next member once
    - dpkg: Factor trigproc_new_cyclenode() out from check_trigger_cycle()
    - dpkg: Mark the package we are giving up on a trigger cycle as istobe normal
    - dpkg: Switch dependtry from an int to an enum
    - dpkg: Reset progress_bytrigproc once we have injected into the current iteration
    - dpkg: Split trigger processing types into required, try-queued and try-deferred
    - dpkg: Convert one trigger processing required type into the new try-queued
    - dpkg: Move trigproc cycle reset inside try-deferred conditional
    - dpkg: Introduce a new dependency try level for trigger processing
    - dpkg: Introduce a new dependency try level for trigger cycle checks

 -- Julian Andres Klode <email address hidden> Tue, 16 Jul 2019 14:57:11 +0200

Revision history for this message
Steve Langasek (vorlon) wrote :

This is believed fixed with the current dpkg.

Changed in ubuntu-release-upgrader (Ubuntu):
status: Confirmed → Invalid
Changed in gconf2 (Ubuntu):
status: Confirmed → Invalid
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Duplicates of this bug

Subscribing...

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.