1. Start an upgrade.
2. Cancel it after reading some information about the upgrade.
3. Next time, when a user wants to report a bug to Launchpad, the date of the upgrade of the user's current Ubuntu version that will be passed to Launchpad will be the date he activated steps 1 and 2 instead of the actual upgrade date which was much earlier.
It looks like the date of an upgrade needs to be set when a user ends the procedure and not when he starts it.
Steps to reproduce:
1. Start an upgrade.
2. Cancel it after reading some information about the upgrade.
3. Next time, when a user wants to report a bug to Launchpad, the date of the upgrade of the user's current Ubuntu version that will be passed to Launchpad will be the date he activated steps 1 and 2 instead of the actual upgrade date which was much earlier.
It looks like the date of an upgrade needs to be set when a user ends the procedure and not when he starts it.
ProblemType: Bug ature: Ubuntu 4.4.0-137. 163-generic 4.4.144
DistroRelease: Ubuntu 16.04
Package: update-manager 1:16.04.14
ProcVersionSign
Uname: Linux 4.4.0-137-generic i686
ApportVersion: 2.20.1-0ubuntu2.18
Aptdaemon:
Architecture: i386 ubuntu. update- manager' b'show-details' b'true' ubuntu. update- manager' b'window-height' b'741' ubuntu. update- manager' b'first-run' b'false' ubuntu. update- manager' b'window-width' b'1366' ubuntu. update- manager' b'launch-time' b'int64 1540045540' ture: all
CurrentDesktop: LXDE
Date: Sun Oct 21 13:21:25 2018
GsettingsChanges:
b'com.
b'com.
b'com.
b'com.
b'com.
InstallationDate: Installed on 2015-01-06 (1383 days ago)
InstallationMedia: Lubuntu 14.10 "Utopic Unicorn" - Release i386 (20141022.1)
PackageArchitec
SourcePackage: update-manager
UpgradeStatus: Upgraded to xenial on 2018-08-28 (54 days ago)