I am unable to reproduce this issue here using an unmodified, current groovy image of either Ubuntu (http://cdimage.ubuntu.com/ubuntu/daily-live/20200826/groovy-desktop-amd64.iso) or Kubuntu (http://cdimage.ubuntu.com/kubuntu/daily-live/20200831/groovy-desktop-amd64.iso) in a KVM instance configured with the Microsoft SecureBoot keys.
Is this problem still reproducible for you with the current daily images listed above?
What are the contents of your secureboot firmware variables, as reported by mokutil --db and mokutil --dbx?
> Followed by an OK box - which when selected offers to import the SHIM key
What key, exactly, are you being offered to import? Can you please attach a screenshot?
I am unable to reproduce this issue here using an unmodified, current groovy image of either Ubuntu (http:// cdimage. ubuntu. com/ubuntu/ daily-live/ 20200826/ groovy- desktop- amd64.iso) or Kubuntu (http:// cdimage. ubuntu. com/kubuntu/ daily-live/ 20200831/ groovy- desktop- amd64.iso) in a KVM instance configured with the Microsoft SecureBoot keys.
Is this problem still reproducible for you with the current daily images listed above?
What are the contents of your secureboot firmware variables, as reported by mokutil --db and mokutil --dbx?
> Followed by an OK box - which when selected offers to import the SHIM key
What key, exactly, are you being offered to import? Can you please attach a screenshot?