[Bug 1642215] Re: Zesty updating a package that uses dkms is not triggering mokutil and causing aptd to use 100% cpu
Iain Lane
iain at orangesquash.org.uk
Wed Nov 23 11:56:12 UTC 2016
Hey Brian, could you take a look if you have a moment please?
I think that somehow u-m isn't propagating the question to the user -
and I also think that this might affect yakkety (and maybe xenial) too.
** Changed in: update-manager (Ubuntu)
Assignee: (unassigned) => Brian Murray (brian-murray)
--
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to update-manager in Ubuntu.
https://bugs.launchpad.net/bugs/1642215
Title:
Zesty updating a package that uses dkms is not triggering mokutil and
causing aptd to use 100% cpu
Status in update-manager package in Ubuntu:
New
Bug description:
STEPS:
Prerequisite:
A system with UEFI and Secureboot enabled
1. Install Zesty image from a couple of days ago
2. Update the system and run top
EXPECTED:
I expect the system to update and close
ACTUAL:
System stops late on in the upgrade process and triggers 100% of cpu usage, When I kill the system and run sudo apt -f install the first think that happens is I get a window for mokutil so my assumption is that update-manager isn't triggering a window for this, causing the update-maanger window to grey out and become unusable and aptd unable to move on then uses 100% of the cpu.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/update-manager/+bug/1642215/+subscriptions
More information about the foundations-bugs
mailing list