Incorrect UpgradeStatus field value in saved crash file

Bug #1786125 reported by Mike Vastola on 2018-08-08
This bug affects 1 person
Affects Status Importance Assigned to Milestone
apport (Ubuntu)

Bug Description

For whatever reason, when I run apport-bug or apport-cli, the crash file that is generated/submitted contains the line:
UpgradeStatus: Upgraded to bionic on 2014-12-03 (1344 days ago)

Obviously this is wildly incorrect, and I'm not even sure how this value was obtained. (I imagine the last modified date on some file?)

Happy to help debug if there's any other info I can provide.

Expected value is the correct one (about a month ago).

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: apport 2.20.9-0ubuntu7.2
ProcVersionSignature: Ubuntu 4.15.0-29.31-generic 4.15.18
Uname: Linux 4.15.0-29-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.20.9-0ubuntu7.2
Architecture: amd64
CrashReports: 640:0:176:18730739:2018-08-03 16:06:47.263502851 -0400:2018-08-03 16:06:24.015502521 -0400:/var/crash/_usr_lib_virtualbox_VirtualBox.0.crash
CurrentDesktop: KDE
Date: Wed Aug 8 17:27:42 2018
InstallationDate: Installed on 2012-01-06 (2406 days ago)
InstallationMedia: Kubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111011)
PackageArchitecture: all
SourcePackage: apport
UpgradeStatus: Upgraded to bionic on 2014-12-03 (1344 days ago)

Mike Vastola (michael-vastola) wrote :
Brian Murray (brian-murray) wrote :

Could you add the contents of /var/log/dist-upgrade/main.log to this bug report? Thanks in advance. I suspect this is a duplicate of bug 1315559.

Mike Vastola (michael-vastola) wrote :

Ahh.. That's what it checks. No need. My problem then is I haven't been using do-release-upgrade to do updates for a long time.

I have a ton of complicated dependencies that always seem to fail on upgrade, so I've been manually replacing the codename in /etc/apt/sources.list for each upgrade.

So this isn't strictly a duplicate, but it might be for all intents and purposes though if a decision is made to use a different means of obtaining this information. I can understand if this is a wontfix though.

If this is to be corrected, the obvious way that occurs to me though is to pull the files specifying the OS version information (i.e. /etc/debian_version /etc/lsb-release /usr/lib/os-release) into their own package and change it once per release and use the install date of that package.

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

Other bug subscribers