Comment 11 for bug 1867092

No i didn't enrolled a MOK key in the system.Infact I want not prompted with any blue screen .I was a good and smooth install as it usually is.But this error didn't occur the first time i boot up.But then second time onwards it started to appear.

Sent from Yahoo Mail on Android

  On Fri, Mar 13, 2020 at 12:05, Steve Langasek<email address hidden> wrote: This error is not a result of SecureBoot being supported or not.  Why is
shim unable to write to an nvram variable at runtime?  That looks like a
problem with the firmware's UEFI implementation.

I believe we also should only be setting MokListRT, if MokList is also
set.  Were you prompted to enroll a MOK key on this system (unfriendly
blue screen), and did you do so?

The most likely cause for Ubuntu to prompt to you to enroll MOK is if
you have nvidia driver packages installed; but your bug report shows
that you are using nouveau drivers and there is no nvidia kernel module
loaded.  Did you previously try to install the nvidia binary drivers?

** Changed in: shim (Ubuntu)
      Status: Confirmed => Incomplete

** Changed in: grub2 (Ubuntu)
      Status: Confirmed => Invalid

** Changed in: mokutil (Ubuntu)
      Status: Confirmed => Invalid

You received this bug notification because you are subscribed to the bug

  Failed to set MokListRT: Invalid Parameter

Status in grub2 package in Ubuntu:
Status in mokutil package in Ubuntu:
Status in shim package in Ubuntu:
Status in shim-signed package in Ubuntu:

Bug description:
  I am testing Ubuntu 20.04 Daily built the latest version on my MacBook pro-13inch late 2012 model Non-retina display. and I am getting the error while I boot my MacBook using a Pendrive in which I have installed the Ubuntu Daily 20.04 OS.
  Error is as follows :

  Failed. to set MokListRT: Invalid Parameter
  Could not create MokListRT: Invalid Parameter
  Importing MOK states has failed: import_mok_state() failed : invalid Parameter
  Continuing boot since secure mode is disabled.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.4.0-14.17-generic 5.4.18
  Uname: Linux 5.4.0-14-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.11-0ubuntu20
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Mar 12 10:40:44 2020
  DistUpgraded: Fresh install
  DistroCodename: focal
  DistroVariant: ubuntu
  DkmsStatus: bcmwl,, 5.4.0-14-generic, x86_64: installed
  ExtraDebuggingInterest: Yes, if not too technical
  Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] (rev 09) (prog-if 00 [VGA controller])
    Subsystem: Apple Inc. 3rd Gen Core processor Graphics Controller [106b:00fa]
  InstallationDate: Installed on 2020-03-11 (0 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200309)
  MachineType: Apple Inc. MacBookPro9,2
  PATH=(custom, no user)
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-14-generic root=UUID=70f5287a-ef7d-48fd-a479-01244bc3fecf ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  Title: Xorg freeze
  UpgradeStatus: No upgrade log present (probably fresh install) 07/24/2019
  dmi.bios.vendor: Apple Inc.
  dmi.board.asset.tag: Base Board Asset Tag# Mac-6F01561E16C75D06
  dmi.board.vendor: Apple Inc.
  dmi.board.version: MacBookPro9,2
  dmi.chassis.type: 10
  dmi.chassis.vendor: Apple Inc.
  dmi.chassis.version: Mac-6F01561E16C75D06
  dmi.modalias: dmi:bvnAppleInc.:bvr229.,2:pvr1.0:rvnAppleInc.:rnMac-6F01561E16C75D06:rvrMacBookPro9,2:cvnAppleInc.:ct10:cvrMac-6F01561E16C75D06: MacBook Pro MacBookPro9,2
  dmi.product.sku: System SKU#
  dmi.product.version: 1.0
  dmi.sys.vendor: Apple Inc.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.100-4
  version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.0-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.7-2ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20190815-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

To manage notifications about this bug go to: