Decided upbrading ubuntu after somewhat succesfull fix of wifi adapter

Bug #2059777 reported by Daniel Martinek
This bug affects 1 person
Affects Status Importance Assigned to Milestone
ubuntu-release-upgrader (Ubuntu)

Bug Description

I am on Ubuntu 22.04.
I have no idea what package is do-release-upgrade in. Cannot find the version I am using.
OS would have been updated
It gave me error without any tips to resolve it

Reading state information... Done

Calculating the changes

Calculating the changes

Could not calculate the upgrade

An unresolvable problem occurred while calculating the upgrade.

If none of this applies, then please report this bug using the
command 'ubuntu-bug ubuntu-release-upgrader-core' in a terminal. If
you want to investigate this yourself the log files in
'/var/log/dist-upgrade' will contain details about the upgrade.
Specifically, look at 'main.log' and 'apt.log'.

Restoring original system state

logs tell something about broken package. I had to shutdown to turn off secure boot which I thought is off when fixing WIFI I fixed packages after....

ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: ubuntu-release-upgrader-core 1:22.04.19
ProcVersionSignature: Ubuntu 6.5.0-26.26~22.04.1-generic 6.5.13
Uname: Linux 6.5.0-26-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.20.11-0ubuntu82.5
Architecture: amd64
CasperMD5CheckResult: pass
CrashDB: ubuntu
CrashReports: 644:0:124:4199:2024-03-29 14:01:19.054233063 +0100:2024-03-29 14:01:19.074235232 +0100:/var/crash/backport-iwlwifi-dkms.0.crash
CurrentDesktop: ubuntu:GNOME
Date: Fri Mar 29 14:24:05 2024
InstallationDate: Installed on 2023-12-15 (104 days ago)
InstallationMedia: Ubuntu 22.04.3 LTS "Jammy Jellyfish" - Release amd64 (20230807.2)
PackageArchitecture: all
SourcePackage: ubuntu-release-upgrader
UpgradeStatus: Upgraded to jammy on 2024-03-29 (0 days ago)
mtime.conffile..etc.update-manager.release-upgrades: 2024-03-29T14:03:13.172395

Revision history for this message
Daniel Martinek (mcdandy) wrote :
Revision history for this message
Daniel Martinek (mcdandy) wrote :
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.