/usr/lib/update-notifier/list-oem-metapackages:apt_pkg.Error:/usr/lib/update-notifier/list-oem-metapackages@43:__init__:open
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
update-notifier (Ubuntu) |
Fix Released
|
Undecided
|
Iain Lane | ||
Focal |
Fix Released
|
Undecided
|
Iain Lane |
Bug Description
[ Description ]
If you have malformed apt lists, list-oem-
[ Fix ]
Catch failures to construct an apt.Cache object and exit.
[ QA ]
1. Edit a list file in /var/lib/apt/lists which is being used - for example that for the Ubuntu archive's 'main' component.
2. Type some gibberish at the top.
3. Run /usr/lib/
4. When using the current version of update-notifier this should crash. After updating it should print an error and exit 0.
5. Now you can `apt update` or revert what you did in step 2 manually.
[ Where problems could occur ]
We're proceeding to run update-manager now when we know that apt is in a bogus state. This was the status quo for a long time before the recent update which introduced list-oem-
[ Original description ]
The Ubuntu Error Tracker has been receiving reports about a problem regarding update-notifier. This problem was most recently seen with package version 3.192.38, the problem page at https:/
If you do not have access to the Ubuntu Error Tracker and are a software developer, you can request it at http://
Traceback (most recent call last):
File "/usr/lib/
cache = apt.Cache()
File "/usr/lib/
self.
File "/usr/lib/
self._cache = apt_pkg.
apt_pkg.Error: E:can not open /var/lib/
description: | updated |
description: | updated |
Changed in update-notifier (Ubuntu): | |
status: | New → In Progress |
assignee: | nobody → Iain Lane (laney) |
Changed in update-notifier (Ubuntu Focal): | |
status: | New → In Progress |
assignee: | nobody → Iain Lane (laney) |
This bug was fixed in the package update-notifier - 3.192.39
---------------
update-notifier (3.192.39) hirsute; urgency=medium
* data/list- oem-metapackage s: notifier continues. A consequence of being in this state is that
+ Run black
+ Drop unused logging import
+ Handle bad apt indexes. apt.Cache() can fail if the apt lists can't be
parsed for whatever reason. Handle that and exit 0 so that
update-
we can't find any oem metapackages if any are applicable. If the indexes
become good again then we'll find them next time. (LP: #1913726)
-- Iain Lane <email address hidden> Fri, 29 Jan 2021 12:41:07 +0000