Failed upgrade from 22.04.4 LTS to 24.04.1 LTS due to gconf2 "dependency problems".

Bug #2080541 reported by Chase Simmons
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
dpkg (Ubuntu)
New
Undecided
Unassigned
ubuntu-release-upgrader (Ubuntu)
New
Undecided
Unassigned

Bug Description

During the upgrade from 22.04.4 LTS to 24.04.1 LTS the upgrade failed to install gconf2 due to "dependency problems". A full summary of the issue is available on stack exchange at the URL https://askubuntu.com/questions/1525185/failed-upgrade-from-22-04-4-lts-to-24-04-1-lts-with-the-error-message-could-not.

This is the second time I have tried upgrading my system. I prepared my system by using the commands sudo apt update and sudo apt upgrade as well as ppa-purge to remove extra PPA's that may have been causing the issue.

ProblemType: Bug
DistroRelease: Ubuntu 24.04
Package: ubuntu-release-upgrader-core 1:24.04.23
ProcVersionSignature: Ubuntu 6.8.0-40.40~22.04.3-generic 6.8.12
Uname: Linux 6.8.0-40-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia razermouse
ApportVersion: 2.28.1-0ubuntu3.1
Architecture: amd64
CasperMD5CheckResult: unknown
CrashDB: ubuntu
CrashReports: 600:0:124:1205157:2024-09-12 11:02:52.456699313 -0400:2024-09-12 11:02:52.544699941 -0400:/var/crash/gconf2.0.crash
CurrentDesktop: ubuntu:GNOME
Date: Thu Sep 12 11:05:56 2024
InstallationDate: Installed on 2023-06-10 (460 days ago)
InstallationMedia: Ubuntu 22.04.2 LTS "Jammy Jellyfish" - Release amd64 (20230223)
PackageArchitecture: all
ProcEnviron:
 LANG=en_US.UTF-8
 PATH=(custom, no user)
 SHELL=/bin/bash
 TERM=xterm-256color
 XDG_RUNTIME_DIR=<set>
RebootRequiredPkgs: Error: path contained symlinks.
SourcePackage: ubuntu-release-upgrader
Symptom: release-upgrade
UpgradeStatus: Upgraded to noble on 2024-09-12 (0 days ago)
VarLogDistupgradeAptclonesystemstate.tar.gz: Error: command ['pkexec', 'cat', '/var/log/dist-upgrade/apt-clone_system_state.tar.gz'] failed with exit code 127: pkexec must be setuid root
VarLogDistupgradeTermlog:

modified.conffile..etc.apport.report-ignore.README.denylist: [deleted]

Revision history for this message
Chase Simmons (chase9734) wrote :
summary: - Durng the upgrade from 22.04.4 LTS to 24.04.1 LTS the upgrade failed to
- install gconf2 due to "dependancy problems". A full summary of the issue
- is available on stack exchange at the URL
- https://askubuntu.com/questions/1525185/failed-update-from-22-04-4-lts-
- to-24-04-1-lts-with-the-error-message-could-not
+ Failed upgrade from 22.04.4 LTS to 24.04.1 LTS due to gconf2 "dependency
+ problems".
affects: ubuntu → ubuntu-release-upgrader (Ubuntu)
Revision history for this message
Chase Simmons (chase9734) wrote :

Fair warning, I'm not great with programming. That being said, by reviewing the bug notes it looks like the update failed due to a 127 error caused by a permission error, broken symlinks, and the infamous gconf2 error. I found the error message in the main log.

2024-09-12 11:02:59,017 ERROR got an error from dpkg for pkg: 'gconf2': 'dependency problems - leaving triggers unprocessed'
2024-09-12 11:02:59,018 DEBUG running apport_pkgfailure() gconf2: dependency problems - leaving triggers unprocessed

Revision history for this message
Chase Simmons (chase9734) wrote (last edit ):

I also noticed that in the JournalErrors.txt it shows that UFW was blocking some actions. Would this cause any of the issues?

Revision history for this message
Julian Andres Klode (juliank) wrote (last edit ):

We have unpacked a new psmisc, but then as part of gir1.2-nma4-1.0:amd64 configuration, the gconf2 triggers are being run, and gconf2 depends on psmisc, but psmisc has not been configured yet.

This may be an internal ordering bug in dpkg, but also gconf2 should have been removed, not kept installed.

Revision history for this message
Chase Simmons (chase9734) wrote :

That's odd should I attempt deleting gconf2 before running the updater? I'm probably going to do a fresh install and attempt to copy over my current configuration if it doesn't work.

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

Other bug subscribers

Remote bug watches

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