| 2023-02-23 09:13:58 |
FM33 |
bug |
|
|
added bug |
| 2023-02-24 19:10:53 |
Launchpad Janitor |
update-notifier (Ubuntu): status |
New |
Confirmed |
|
| 2023-02-24 22:02:24 |
Steve Langasek |
tags |
amd64 apport-bug focal third-party-packages |
amd64 apport-bug focal regression-update third-party-packages |
|
| 2023-02-24 22:03:52 |
Steve Langasek |
update-notifier (Ubuntu): assignee |
|
Renan Rodrigo (renanrodrigo) |
|
| 2023-02-26 08:50:11 |
Michael Leetz |
bug |
|
|
added subscriber Michael Leetz |
| 2023-02-27 15:09:07 |
Renan Rodrigo |
update-notifier (Ubuntu): status |
Confirmed |
In Progress |
|
| 2023-02-28 04:22:49 |
Renan Rodrigo |
description |
Dialog "System is up to date" keeps popping up several times per session, even when there is no updates available and no reboot is required. Started a few weeks ago.
ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: update-notifier 3.192.30.16
ProcVersionSignature: Ubuntu 5.15.0-60.66~20.04.1-generic 5.15.78
Uname: Linux 5.15.0-60-generic x86_64
ApportVersion: 2.20.11-0ubuntu27.25
Architecture: amd64
CasperMD5CheckResult: skip
CurrentDesktop: ubuntu:GNOME
Date: Thu Feb 23 10:09:59 2023
InstallationDate: Installed on 2020-10-24 (851 days ago)
InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
ProcEnviron:
PATH=(custom, no user)
XDG_RUNTIME_DIR=<set>
LANG=fr_FR.UTF-8
SHELL=/bin/bash
SourcePackage: update-notifier
UpgradeStatus: No upgrade log present (probably fresh install) |
[ Impact ]
Update-notifier will trigger unnecessarily on systems where phased updates are considered in the Update Manager GUI but not considered in apt itself (for LTSs, Focal or earlier). If only the phased updates are available to a system, the dialog box will pop up, but it says that the system is up to date.
This happens because a recent SRU unintentionally broke the logic that treated this situations in the code. To avoid showing those packages, update-notifier needs access to the system apt Cache, but global side-effects of the apt + apt_pkg module interaction ended up providing the wrong Cache to verify phasing.
The fix for this is to isolate the esm Cache creation, restoring the default apt_pkg configuration after the instance is created, guaranteeing that any other Cache calls have access to the system data.
[ Test Plan ]
Besides testing the bugfix, it is important to test the functionality which changed this code in the first place, which was implemented to keep visibility to esm updates.
To reproduce the bug:
- Start a Focal machine
- Run `apt update`, verify which packages are phased using `apt show`
- Install universe packages which have a esm-apps update (ansible is a good candidate)
- Run `/usr/lib/update-notifier/apt-check --human-readable` and see the esm-apps update(s) listed.
- Run `/usr/lib/update-notifier/apt-check -p` and see the phased packages are listed.
To verify the fix:
- Install a version which contains this patch
- Run `/usr/lib/update-notifier/apt-check -p` and see the phased packages are not listed.
- Run `/usr/lib/update-notifier/apt-check --human-readable` and see the esm-apps update(s) listed.
[ Where problems could occur ]
If the function implemented for the fix has any flaw, then esm-apps updates will not show anymore, as they depend on the esm Cache. It is important to verify the esm-apps updates are exactly the same after the fix is applied, as described in the test plan above.
Any other call to any apt Cache functionality outside of this specific function should use the system defaults, which are restored by erasing the configuration and letting apt_pkg initialize it again, assuming safety.
The only known caveat is that the new function should be the only way to access the esm-cache; future instances should only be creating using the function, and never directly.
[ Original Description ]
Dialog "System is up to date" keeps popping up several times per session, even when there is no updates available and no reboot is required. Started a few weeks ago.
ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: update-notifier 3.192.30.16
ProcVersionSignature: Ubuntu 5.15.0-60.66~20.04.1-generic 5.15.78
Uname: Linux 5.15.0-60-generic x86_64
ApportVersion: 2.20.11-0ubuntu27.25
Architecture: amd64
CasperMD5CheckResult: skip
CurrentDesktop: ubuntu:GNOME
Date: Thu Feb 23 10:09:59 2023
InstallationDate: Installed on 2020-10-24 (851 days ago)
InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
ProcEnviron:
PATH=(custom, no user)
XDG_RUNTIME_DIR=<set>
LANG=fr_FR.UTF-8
SHELL=/bin/bash
SourcePackage: update-notifier
UpgradeStatus: No upgrade log present (probably fresh install) |
|
| 2023-02-28 04:25:35 |
Renan Rodrigo |
description |
[ Impact ]
Update-notifier will trigger unnecessarily on systems where phased updates are considered in the Update Manager GUI but not considered in apt itself (for LTSs, Focal or earlier). If only the phased updates are available to a system, the dialog box will pop up, but it says that the system is up to date.
This happens because a recent SRU unintentionally broke the logic that treated this situations in the code. To avoid showing those packages, update-notifier needs access to the system apt Cache, but global side-effects of the apt + apt_pkg module interaction ended up providing the wrong Cache to verify phasing.
The fix for this is to isolate the esm Cache creation, restoring the default apt_pkg configuration after the instance is created, guaranteeing that any other Cache calls have access to the system data.
[ Test Plan ]
Besides testing the bugfix, it is important to test the functionality which changed this code in the first place, which was implemented to keep visibility to esm updates.
To reproduce the bug:
- Start a Focal machine
- Run `apt update`, verify which packages are phased using `apt show`
- Install universe packages which have a esm-apps update (ansible is a good candidate)
- Run `/usr/lib/update-notifier/apt-check --human-readable` and see the esm-apps update(s) listed.
- Run `/usr/lib/update-notifier/apt-check -p` and see the phased packages are listed.
To verify the fix:
- Install a version which contains this patch
- Run `/usr/lib/update-notifier/apt-check -p` and see the phased packages are not listed.
- Run `/usr/lib/update-notifier/apt-check --human-readable` and see the esm-apps update(s) listed.
[ Where problems could occur ]
If the function implemented for the fix has any flaw, then esm-apps updates will not show anymore, as they depend on the esm Cache. It is important to verify the esm-apps updates are exactly the same after the fix is applied, as described in the test plan above.
Any other call to any apt Cache functionality outside of this specific function should use the system defaults, which are restored by erasing the configuration and letting apt_pkg initialize it again, assuming safety.
The only known caveat is that the new function should be the only way to access the esm-cache; future instances should only be creating using the function, and never directly.
[ Original Description ]
Dialog "System is up to date" keeps popping up several times per session, even when there is no updates available and no reboot is required. Started a few weeks ago.
ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: update-notifier 3.192.30.16
ProcVersionSignature: Ubuntu 5.15.0-60.66~20.04.1-generic 5.15.78
Uname: Linux 5.15.0-60-generic x86_64
ApportVersion: 2.20.11-0ubuntu27.25
Architecture: amd64
CasperMD5CheckResult: skip
CurrentDesktop: ubuntu:GNOME
Date: Thu Feb 23 10:09:59 2023
InstallationDate: Installed on 2020-10-24 (851 days ago)
InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
ProcEnviron:
PATH=(custom, no user)
XDG_RUNTIME_DIR=<set>
LANG=fr_FR.UTF-8
SHELL=/bin/bash
SourcePackage: update-notifier
UpgradeStatus: No upgrade log present (probably fresh install) |
[ Impact ]
Update-notifier will trigger unnecessarily on systems where phased updates are considered in the Update Manager GUI but not considered in apt itself (for LTSs, Focal or earlier). If only the phased updates are available to a system, the dialog box will pop up, but it says that the system is up to date.
This happens because a recent SRU unintentionally broke the logic that treated this situations in the code. To avoid showing those packages, update-notifier needs access to the system apt Cache, but global side-effects of the apt + apt_pkg module interaction ended up providing the wrong Cache to verify phasing.
The fix for this is to isolate the esm Cache creation, restoring the default apt_pkg configuration after the instance is created, guaranteeing that any other Cache calls have access to the system data.
[ Test Plan ]
Besides testing the bugfix, it is important to test the functionality which changed this code in the first place, which was implemented to keep visibility to esm updates.
To reproduce the bug:
- Start a Focal machine
- Run `apt update`, verify which packages are phased using `apt show`
- Install universe packages which have a esm-apps update (ansible is a good candidate)
- Run `/usr/lib/update-notifier/apt-check --human-readable` and see the esm-apps update(s) listed.
- Run `/usr/lib/update-notifier/apt-check -p` and see the phased packages are listed.
To verify the fix:
- Install a version which contains this patch
- Run `/usr/lib/update-notifier/apt-check -p` and see the phased packages are not listed.
- Run `/usr/lib/update-notifier/apt-check --human-readable` and see the esm-apps update(s) listed.
[ Where problems could occur ]
If the function implemented for the fix has any flaw, then esm-apps updates will not show anymore, as they depend on the esm Cache. It is important to verify the esm-apps updates are exactly the same after the fix is applied, as described in the test plan above.
Any other call to any apt Cache functionality outside of this specific function should use the system defaults, which are restored by erasing the configuration and letting apt_pkg initialize it again, assuming safety.
The only known caveat is that the new function should be the only way to access the esm-cache; future instances should only be creating using the function, and never directly.
[ Original Description ]
Dialog "System is up to date" keeps popping up several times per session, even when there is no updates available and no reboot is required. Started a few weeks ago.
ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: update-notifier 3.192.30.16
ProcVersionSignature: Ubuntu 5.15.0-60.66~20.04.1-generic 5.15.78
Uname: Linux 5.15.0-60-generic x86_64
ApportVersion: 2.20.11-0ubuntu27.25
Architecture: amd64
CasperMD5CheckResult: skip
CurrentDesktop: ubuntu:GNOME
Date: Thu Feb 23 10:09:59 2023
InstallationDate: Installed on 2020-10-24 (851 days ago)
InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
ProcEnviron:
PATH=(custom, no user)
XDG_RUNTIME_DIR=<set>
LANG=fr_FR.UTF-8
SHELL=/bin/bash
SourcePackage: update-notifier
UpgradeStatus: No upgrade log present (probably fresh install) |
|
| 2023-02-28 10:33:15 |
Renan Rodrigo |
nominated for series |
|
Ubuntu Bionic |
|
| 2023-02-28 10:33:15 |
Renan Rodrigo |
bug task added |
|
update-notifier (Ubuntu Bionic) |
|
| 2023-02-28 10:33:15 |
Renan Rodrigo |
nominated for series |
|
Ubuntu Jammy |
|
| 2023-02-28 10:33:15 |
Renan Rodrigo |
bug task added |
|
update-notifier (Ubuntu Jammy) |
|
| 2023-02-28 10:33:15 |
Renan Rodrigo |
nominated for series |
|
Ubuntu Focal |
|
| 2023-02-28 10:33:15 |
Renan Rodrigo |
bug task added |
|
update-notifier (Ubuntu Focal) |
|
| 2023-02-28 10:33:15 |
Renan Rodrigo |
nominated for series |
|
Ubuntu Xenial |
|
| 2023-02-28 10:33:15 |
Renan Rodrigo |
bug task added |
|
update-notifier (Ubuntu Xenial) |
|
| 2023-02-28 12:45:37 |
Launchpad Janitor |
merge proposal linked |
|
https://code.launchpad.net/~renanrodrigo/update-notifier/+git/update-notifier/+merge/438009 |
|
| 2023-02-28 13:00:29 |
Launchpad Janitor |
merge proposal linked |
|
https://code.launchpad.net/~renanrodrigo/update-notifier/+git/update-notifier/+merge/438010 |
|
| 2023-02-28 13:00:47 |
Launchpad Janitor |
merge proposal linked |
|
https://code.launchpad.net/~renanrodrigo/update-notifier/+git/update-notifier/+merge/438011 |
|
| 2023-02-28 13:00:57 |
Launchpad Janitor |
merge proposal linked |
|
https://code.launchpad.net/~renanrodrigo/update-notifier/+git/update-notifier/+merge/438012 |
|
| 2023-02-28 13:11:37 |
Launchpad Janitor |
merge proposal linked |
|
https://code.launchpad.net/~renanrodrigo/ubuntu/+source/update-notifier/+git/update-notifier/+merge/438015 |
|
| 2023-03-01 13:22:01 |
Renan Rodrigo |
description |
[ Impact ]
Update-notifier will trigger unnecessarily on systems where phased updates are considered in the Update Manager GUI but not considered in apt itself (for LTSs, Focal or earlier). If only the phased updates are available to a system, the dialog box will pop up, but it says that the system is up to date.
This happens because a recent SRU unintentionally broke the logic that treated this situations in the code. To avoid showing those packages, update-notifier needs access to the system apt Cache, but global side-effects of the apt + apt_pkg module interaction ended up providing the wrong Cache to verify phasing.
The fix for this is to isolate the esm Cache creation, restoring the default apt_pkg configuration after the instance is created, guaranteeing that any other Cache calls have access to the system data.
[ Test Plan ]
Besides testing the bugfix, it is important to test the functionality which changed this code in the first place, which was implemented to keep visibility to esm updates.
To reproduce the bug:
- Start a Focal machine
- Run `apt update`, verify which packages are phased using `apt show`
- Install universe packages which have a esm-apps update (ansible is a good candidate)
- Run `/usr/lib/update-notifier/apt-check --human-readable` and see the esm-apps update(s) listed.
- Run `/usr/lib/update-notifier/apt-check -p` and see the phased packages are listed.
To verify the fix:
- Install a version which contains this patch
- Run `/usr/lib/update-notifier/apt-check -p` and see the phased packages are not listed.
- Run `/usr/lib/update-notifier/apt-check --human-readable` and see the esm-apps update(s) listed.
[ Where problems could occur ]
If the function implemented for the fix has any flaw, then esm-apps updates will not show anymore, as they depend on the esm Cache. It is important to verify the esm-apps updates are exactly the same after the fix is applied, as described in the test plan above.
Any other call to any apt Cache functionality outside of this specific function should use the system defaults, which are restored by erasing the configuration and letting apt_pkg initialize it again, assuming safety.
The only known caveat is that the new function should be the only way to access the esm-cache; future instances should only be creating using the function, and never directly.
[ Original Description ]
Dialog "System is up to date" keeps popping up several times per session, even when there is no updates available and no reboot is required. Started a few weeks ago.
ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: update-notifier 3.192.30.16
ProcVersionSignature: Ubuntu 5.15.0-60.66~20.04.1-generic 5.15.78
Uname: Linux 5.15.0-60-generic x86_64
ApportVersion: 2.20.11-0ubuntu27.25
Architecture: amd64
CasperMD5CheckResult: skip
CurrentDesktop: ubuntu:GNOME
Date: Thu Feb 23 10:09:59 2023
InstallationDate: Installed on 2020-10-24 (851 days ago)
InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
ProcEnviron:
PATH=(custom, no user)
XDG_RUNTIME_DIR=<set>
LANG=fr_FR.UTF-8
SHELL=/bin/bash
SourcePackage: update-notifier
UpgradeStatus: No upgrade log present (probably fresh install) |
[ Impact ]
Update-notifier will trigger unnecessarily on systems where phased updates are considered in the Update Manager GUI but not considered in apt itself (for LTSs, Focal or earlier). If only the phased updates are available to a system, the dialog box will pop up, but it says that the system is up to date.
This happens because a recent SRU unintentionally broke the logic that treated this situations in the code. To avoid showing those packages, update-notifier needs access to the system apt Cache, but global side-effects of the apt + apt_pkg module interaction ended up providing the wrong Cache to verify phasing.
The fix for this is to isolate the esm Cache creation, restoring the default apt_pkg configuration after the instance is created, guaranteeing that any other Cache calls have access to the system data.
[ Test Plan ]
Besides testing the bugfix, it is important to test the functionality which changed this code in the first place, which was implemented to keep visibility to esm updates.
To reproduce the bug:
- Start a Focal machine
- Run `apt update`, verify which packages updates are phased (using apt show, for instance, will show a Phased-Update-Percentage metadata key)
- If there is no phased update happening, downgrade a package and fake phasing by editing the /var/lib/apt/lists file
- Install universe packages which have a esm-apps update (ansible is a good candidate)
- Run `/usr/lib/update-notifier/apt-check --human-readable` and see the esm-apps update(s) listed.
- Run `/usr/lib/update-notifier/apt-check -p` and see the phased packages are listed.
To verify the fix:
- Install a version which contains this patch
- Run `/usr/lib/update-notifier/apt-check --human-readable` and see the esm-apps update(s) listed.
- Run `/usr/lib/update-notifier/apt-check -p` and see the phased packages are not listed.
[ Where problems could occur ]
If the function implemented for the fix has any flaw, then esm-apps updates will not show anymore, as they depend on the esm Cache. It is important to verify the esm-apps updates are exactly the same after the fix is applied, as described in the test plan above.
Any other call to any apt Cache functionality outside of this specific function should use the system defaults, which are restored by erasing the configuration and letting apt_pkg initialize it again, assuming safety.
The only known caveat is that the new function should be the only way to access the esm-cache; future instances should only be creating using the function, and never directly.
[ Original Description ]
Dialog "System is up to date" keeps popping up several times per session, even when there is no updates available and no reboot is required. Started a few weeks ago.
ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: update-notifier 3.192.30.16
ProcVersionSignature: Ubuntu 5.15.0-60.66~20.04.1-generic 5.15.78
Uname: Linux 5.15.0-60-generic x86_64
ApportVersion: 2.20.11-0ubuntu27.25
Architecture: amd64
CasperMD5CheckResult: skip
CurrentDesktop: ubuntu:GNOME
Date: Thu Feb 23 10:09:59 2023
InstallationDate: Installed on 2020-10-24 (851 days ago)
InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
ProcEnviron:
PATH=(custom, no user)
XDG_RUNTIME_DIR=<set>
LANG=fr_FR.UTF-8
SHELL=/bin/bash
SourcePackage: update-notifier
UpgradeStatus: No upgrade log present (probably fresh install) |
|
| 2023-03-03 01:36:20 |
Renan Rodrigo |
bug |
|
|
added subscriber Ubuntu Stable Release Updates Team |
| 2023-03-04 03:59:11 |
Launchpad Janitor |
update-notifier (Ubuntu): status |
In Progress |
Fix Released |
|
| 2023-03-06 21:07:48 |
Kodiak Firesmith |
bug |
|
|
added subscriber Kodiak Firesmith |
| 2023-03-07 15:17:25 |
Launchpad Janitor |
update-notifier (Ubuntu Xenial): status |
New |
Confirmed |
|
| 2023-03-07 15:17:25 |
Launchpad Janitor |
update-notifier (Ubuntu Bionic): status |
New |
Confirmed |
|
| 2023-03-07 15:17:25 |
Launchpad Janitor |
update-notifier (Ubuntu Focal): status |
New |
Confirmed |
|
| 2023-03-07 15:17:25 |
Launchpad Janitor |
update-notifier (Ubuntu Jammy): status |
New |
Confirmed |
|
| 2023-03-09 18:37:07 |
Andreas Hasenack |
update-notifier (Ubuntu Jammy): status |
Confirmed |
Fix Committed |
|
| 2023-03-09 18:37:10 |
Andreas Hasenack |
bug |
|
|
added subscriber SRU Verification |
| 2023-03-09 18:37:13 |
Andreas Hasenack |
tags |
amd64 apport-bug focal regression-update third-party-packages |
amd64 apport-bug focal regression-update third-party-packages verification-needed verification-needed-jammy |
|
| 2023-03-09 18:38:42 |
Andreas Hasenack |
update-notifier (Ubuntu Focal): status |
Confirmed |
Fix Committed |
|
| 2023-03-09 18:38:49 |
Andreas Hasenack |
tags |
amd64 apport-bug focal regression-update third-party-packages verification-needed verification-needed-jammy |
amd64 apport-bug focal regression-update third-party-packages verification-needed verification-needed-focal verification-needed-jammy |
|
| 2023-03-09 18:39:56 |
Andreas Hasenack |
update-notifier (Ubuntu Bionic): status |
Confirmed |
Fix Committed |
|
| 2023-03-09 18:40:03 |
Andreas Hasenack |
tags |
amd64 apport-bug focal regression-update third-party-packages verification-needed verification-needed-focal verification-needed-jammy |
amd64 apport-bug focal regression-update third-party-packages verification-needed verification-needed-bionic verification-needed-focal verification-needed-jammy |
|
| 2023-03-09 18:40:43 |
Andreas Hasenack |
update-notifier (Ubuntu Xenial): status |
Confirmed |
Fix Committed |
|
| 2023-03-09 18:40:51 |
Andreas Hasenack |
tags |
amd64 apport-bug focal regression-update third-party-packages verification-needed verification-needed-bionic verification-needed-focal verification-needed-jammy |
amd64 apport-bug focal regression-update third-party-packages verification-needed verification-needed-bionic verification-needed-focal verification-needed-jammy verification-needed-xenial |
|
| 2023-03-14 09:23:35 |
Dariusz Gadomski |
bug |
|
|
added subscriber Dariusz Gadomski |
| 2023-03-14 09:59:04 |
Dariusz Gadomski |
tags |
amd64 apport-bug focal regression-update third-party-packages verification-needed verification-needed-bionic verification-needed-focal verification-needed-jammy verification-needed-xenial |
amd64 apport-bug focal regression-update third-party-packages verification-done-focal verification-needed verification-needed-bionic verification-needed-jammy verification-needed-xenial |
|
| 2023-03-14 12:01:43 |
Renan Rodrigo |
tags |
amd64 apport-bug focal regression-update third-party-packages verification-done-focal verification-needed verification-needed-bionic verification-needed-jammy verification-needed-xenial |
amd64 apport-bug focal regression-update third-party-packages verification-done-focal verification-done-xenial verification-needed verification-needed-bionic verification-needed-jammy |
|
| 2023-03-14 14:27:07 |
Renan Rodrigo |
tags |
amd64 apport-bug focal regression-update third-party-packages verification-done-focal verification-done-xenial verification-needed verification-needed-bionic verification-needed-jammy |
amd64 apport-bug focal regression-update third-party-packages verification-done-bionic verification-done-focal verification-done-xenial verification-needed verification-needed-jammy |
|
| 2023-03-14 19:47:18 |
Renan Rodrigo |
tags |
amd64 apport-bug focal regression-update third-party-packages verification-done-bionic verification-done-focal verification-done-xenial verification-needed verification-needed-jammy |
amd64 apport-bug focal regression-update third-party-packages verification-done verification-done-bionic verification-done-focal verification-done-jammy verification-done-xenial |
|
| 2023-03-21 21:58:39 |
Launchpad Janitor |
update-notifier (Ubuntu Jammy): status |
Fix Committed |
Fix Released |
|
| 2023-03-21 21:58:43 |
Brian Murray |
removed subscriber Ubuntu Stable Release Updates Team |
|
|
|
| 2023-03-22 15:14:03 |
Launchpad Janitor |
update-notifier (Ubuntu Focal): status |
Fix Committed |
Fix Released |
|
| 2023-03-22 15:15:38 |
Launchpad Janitor |
update-notifier (Ubuntu Bionic): status |
Fix Committed |
Fix Released |
|
| 2023-03-22 15:16:56 |
Launchpad Janitor |
update-notifier (Ubuntu Xenial): status |
Fix Committed |
Fix Released |
|
| 2023-03-27 21:08:07 |
Ivan Kurnosov |
bug |
|
|
added subscriber Ivan Kurnosov |
