[Bug 1942497] [NEW] Update the hardware support for Lenovo ThinkCentre M70q/M80q/M90q in oem-sutton.newell-cade-meta
Launchpad Bug Tracker
1942497 at bugs.launchpad.net
Tue Sep 14 08:58:20 UTC 2021
You have been subscribed to a public bug by Bin Li (binli):
[Impact]
* It should have no impact at all because these changes shall have been
applied and verified in the corresponding OEM archive before this SRU
process.
[Test Plan]
* Install Ubuntu 20.04.x LTS on Lenovo ThinkCentre M70q/M80q/M90q and
remove oem-sutton.newell-cade-meta manually if any.
* Enable focal-proposed and execute the update-manager.
* The update-manager should show "Hardware support for Lenovo
ThinkCentre M70q/M80q/M90q". If not, please change "When there are
security updates" and "When there are other updates" in the Updates of
software-properties-gtk to "Display immediately", install the older
firefox by `sudo apt install firefox=75.0+build3-0ubuntu1` and reboot
the system to wait for the update-manager pop up automatically.
* After it installed oem-sutton.newell-cade-meta by update-manager and
reboot the system, you should see the system booting from the linux-
generic-hwe-20.04 kernel.
[Where problems could occur]
* oem-sutton.newell-cade-meta is installed but it is not updated to the
version in the corresponding OEM archive.
* The update-manager didn't show "Hardware support for Lenovo
ThinkCentre M70q/M80q/M90q" at all.
[Other Info]
* You can see all oem-sutton.newell-cade-meta versions on https://people.ubuntu.com/~fourdollars/oem-meta-packages/.
* I have used ppa:oem-solutions-engineers/oem-projects-meta to verify it before this SRU process.
** Affects: oem-priority
Importance: Critical
Assignee: Bin Li (binli)
Status: Confirmed
** Affects: oem-sutton.newell-cade-meta (Ubuntu)
Importance: Undecided
Status: New
** Tags: oem-meta-packages oem-priority oem-scripts-1.13
--
Update the hardware support for Lenovo ThinkCentre M70q/M80q/M90q in oem-sutton.newell-cade-meta
https://bugs.launchpad.net/bugs/1942497
You received this bug notification because you are a member of Ubuntu Sponsors Team, which is subscribed to the bug report.
More information about the Ubuntu-sponsors
mailing list