Zesty updating a package that uses dkms is not triggering mokutil and causing aptd to use 100% cpu

[Dave Morley]

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.

[Iain Lane (laney)]

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.

[Brian Murray (brian-murray)]

What zesty image were you using? Was it just Ubuntu or Xubuntu or something else?

[Mathieu Trudel-Lapierre (cyphermox)]

I can't seem to reproduce this here; whether using a default install or with libgtk2-perl installed. Is there anything you can add to this bug that would help us reproducing the issue? Anything special about this install?

[Dave Morley (davmor2)]

Mathieu Hey dude I'll keep an eye out for it over the next few days but it normally kicks in with driver updates that request dkms and I've not had one of those for a while.

[Brian Murray (brian-murray)]

Any news on this?