Failed to set MokListRT: Invalid Parameter

This change was made by a bot.

Just remove shim/shim-signed/mokutil, and make sure you also deleted /boot/efi/EFI/*/shimx64.efi, then this problem goes away. It's not related to linux kernel.

Status changed to 'Confirmed' because the bug affects multiple users.

https://support.apple.com/en-us/HT208330 2012 MBP don't have T2 Security Chip, therefore no Secure Boot support. So don't try secure boot on it. (which sounds this should be a WONTFIX/INVALID bug, but let shim developers decide).

Even if it is Won't Fix, then users should not be presented with error messages for non-errors.

so will the error message go away in the upcoming updates or not?

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?

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
report.
https://bugs.launchpad.net/bugs/1867092

Title:
  Failed to set MokListRT: Invalid Parameter

Status in grub2 package in Ubuntu:
  Invalid
Status in mokutil package in Ubuntu:
  Invalid
Status in shim package in Ubuntu:
  Incomplete
Status in shim-signed package in Ubuntu:
  Confirmed

Bug description:
  Hello,
  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, 6.30.223.271+bdcom, 5.4.0-14-generic, x86_64: installed
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
  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
  ProcEnviron:
  LANGUAGE=en_IN:en
  PATH=(custom, no user)
  XDG_RUN...

Just to confirm that I installed it correctly i reinstalled the Ubuntu 20.04 OS completely but still getting the same screen error. I Even cleared any Boot file junk and NVRAM data to reset Just to be safe but still getting this error.
The installation process followed is as per books.
But still getting this error please help me to get rid of it.
Thank you.

I can confirm that this error is shown after clean installing Ubuntu 20.04 on a Mac and rebooting.
My device is a late 2015 iMac. Seems to work well but as stated above users shouldn't be presented such a error when there is actually no problem.

I've got the same issue on my Macbook Pro early 2008. Deleting /boot/efi/EFI/ubuntu/shimx64.efi doesn't help at all.

"Solution": Press "alt" when booting the macbook. Select "Boot from next target" and your system should boot by showing the error message. Alternatively, do exactly the same by starting a LIVE USB system at the first time.

Hi! I also have got this on my Macbook air 2012 running Linux mint 20 xfce after latest package update.

Just installed 20.04 my Macbook 2010. At first it booted ok. Then when logging on the screen would flash and go right back to the log on screen. I thought it had to do with chrome remote desk top. After some searching I landed on this thread. https://askubuntu.com/questions/1231410/cant-log-in-on-ubuntu-20-04 One of the post talked about following this and it worked. https://www.how2shout.com/how-to/ubuntu-20-04-lts-stuck-login-loop-general-solution.html Basicly it just told about using alt, ctl, F3 to log in. Then it said to do a apt update/upgrade. After doing that it did fix my hanging on the gui log in screen, but that was when I stated seeing "MokListRT" error. Since I am not using secure boot, mine will continue loading all the way though. I was getting a crash report for chrome-remote-desktop. I remove it and still getting the error. Being new to Ubuntu 20.04 this may be normal, but everytime I log on I see a pop up for an application requesting access to the "default keyring". It does not tell me which application. I suspected it to be chrome, so I canceled the popup, then went into chrome, and it did pop back up. So I assume that chrome is requesting the access.

I hope this detail help narrow down more than it confuses. Any logs that I can help with let me know.

The MokListRT error has nothing to do with either chrome, or problems logging into the desktop.

The day before yesterday, I got the error as originally reported, except I was running Kubuntu 20.04, got the updates available prompt, opened Discover, updated shim and shim-signed, waited for both the regular software update and grub update to finish, and then restarted.

I posted a question on Ask Ubuntu, then found a CentOS bug with a fix I was able to adapt to my own situation and answer my own question. If you're a bug fixer, read the first note on the CentOS bug; if you've got this same problem, read the Ask Ubuntu question and answer:

https://bugs.centos.org/view.php?id=15522#c33203
https://askubuntu.com/questions/1277828/how-do-i-fix-broken-boot-after-shim-update

So the issue here appears to be that the new shim treats a failure to write MokListRT to nvram as a fatal error, even when not booting in SecureBoot mode, with the consequence that systems with no nvram space available will fail to boot.

This will take time to resolve upstream due to the requirement to go through a signing cycle with Microsoft for any new binaries. However, it sounds like the bug is well-characterized and we should be able to work with upstream for a proper fix.

Is this related to the problem? Haven't attempted this solution yet, but I am on a 2011 Macbook Pro running Ubuntu 20.04 experiencing the same issue.

https://askubuntu.com/questions/1279602/ubuntu-20-04-failed-to-set-moklistrt-invallid-parameter

This seems to work on MacBook Air 2012

sudo su -
cd /boot/efi/EFI/ubuntu
cp grubx64.efi shimx64.efi
reboot

You effectively just did the same as uninstalling shim-signed but in a weird way that will get reverted every update.

This worked for me on my MPB 2015

apt-get purge shim
mv /boot/efi/EFI/ubuntu /root/ubuntu-efi.bak #backing up just in case
grub-install /dev/sda1

I can also confirm this bug for Kubuntu 18.04 LTS at an older Apple iMac 8,1 computer. The solution seems to purge shim and then reinstall grub.

It would be really great if the corresponding devs can fix this issue by add a simple check (for an Apple EFI environment) before shim is installed. Or it may be also possible to make shim aware that there also exists non Secure Boot capable UEFI systems. (So far I know, Apple introduced the Secure Boot feature not before 2017.) On such nun Secure Boot compliant systems shim only has to be inactive and quiet. ;-)

I can reproduce on a 2008 iMac and a 2011 Mac Mini. I can also confirm that Rowan's steps in comment #23 work to fix the problem.

I have this issue when booting Ubuntu 20.4 on an iMac 21.5' mid-2010 from a Live USB pendrive.

i have this problem on a 17" Macbook Pro 4,1 from 2008. until recently, with nvidia drivers installed, both Ubuntu and MX Linux performed very well, now i can get anything on this computer to boot except mac os and i can't even get an official mac os install dvd to boot, nor a techtool pro 4 which i found in an old cd wallet to try to fix problems. i never really used anything but Ubuntu since around 2009, and it's still running 10.6 snow leopard.

I faced this, but not on a Mac. I have an ordinary Desktop PC with a Gigabyte 880GM-USB3 (rev3.1) motherboard. This old motherboard does not have secure boot or MokManager or UEFI etc. It has a legacy BIOS. I installed Ubuntu 20.10 (Groovy Gorilla) yesterday. Each time I start the PC, I'm shown the following message for around 10 seconds and only then it proceeds to grub:
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 System BootOrder not found. Initializing defaults.
Creating boot entry "Boot0002" with label "ubuntu" for file "\EFI\ubuntu\shimx64.efi"
Failed to set MokListRT: Invalid Parameter
Could not create MokListRT: Invalid Parameter
Import MOK states has failed: import_mok_state() failed: Invalid Parameter
Continuing boot since secure mode is disabled.

I've attached an image of the error screen. The annoying thing about this bug is that each time I start my PC, this message is shown for 10 seconds. Please fix this. Many people still use old computers that don't have MokManager etc. Please take that into account.

> This old motherboard does not have
> secure boot or MokManager or UEFI
> etc. It has a legacy BIOS.

That's not true. This code is never executed on systems that don't have UEFI.

The 10 second delay before boot proceeds may be addressed by the version of shim currently in impish-proposed, which will be brought back to all currently supported releases of Ubuntu. However, the error messages themselves indicate problems with the UEFI implementation on your motherboard, which is evidently not preserving runtime variables set by the OS. You might want to check if there are firmware updates for your motherboard that fix this, or else check your settings so that you are actually booting in bios mode, which you currently are not.

@Steve: Ok, the /sys/firmware/efi folder exists, so I guess there might be EFI support somewhere, but I'm quite confident the BIOS options have nothing regarding MokManager or UEFI. After creating a bootable USB (Groovy Gorilla), it wouldn't boot. I don't remember the error message, but there was some solution on the internet which I followed to (I think), convert the USB filesystem to GPT or something, and only then it worked. Toward the end of the Ubuntu installation, I encountered this error: "Executing grub-install /dev/sda failed. This is a fatal error" (Image attached).

On Wed, May 12, 2021 at 12:01:47PM -0000, Nav wrote:
> Toward the end of the Ubuntu installation, I encountered this
> error: "Executing grub-install /dev/sda failed. This is a fatal error"

That is unrelated to this bug report. Please file a separate bug for
installer issues.

Could you please boot daily impish image, and let us know if you still observe the messages in question?

@Steve: I had mentioned installer issues in Comment 12 for bug 1905491 (https://bugs.launchpad.net/ubuntu/+source/usb-creator/+bug/1905491/comments/12). Entered my computer's BIOS and checked...there was no option for secure boot or MokManager. Very confident that the old BIOS does not support these. The following partitions were what got automatically created:
Device Type.
/dev/sda1 BIOS boot.
/dev/sda2 EFI System.
/dev/sda3 Linux filesystem.
@Dimitri: It'll be many days before I can download and try a live USB boot of Impish. Although I'm not sure if live boot will show the error I've mentioned in comment #28. The error of comment #30 I could perhaps reproduce, by creating a dual boot with Groovy Gorilla. It'll take a while before I can start with this.

@Dimitri: Just noticed that Impish is part of a daily build. I live in a 3rd world country, and use the internet from my mobile phone. There's a daily limit of 1GB and the download speed is around 1MBps to 5MBps. Impish is 2.6GB. If you've made any patches that support legacy motherboards and helps avoid the errors during installation and boot, please let me know when those patches are applied to the LTS version. I've been wanting to install the LTS version, but as I remember, I had faced installation issues, which is why I downloaded Groovy Gorilla...where I faced installation issues again, but somehow managed to get through. I need to use a torrent to download Ubuntu over a span of multiple days. Kinda hoping y'all keep the ISO size small. I've also been informing Steam, Snap and the Android SDK teams that these massive download sizes are quite crippling for people in 3rd world countries :-) Waiting to hear about the LTS patch that I could test for you.

 I am getting the same error after an update to Ubuntu 18.04

> I am getting the same error after an update to Ubuntu 18.04

After updating from what to what? There have not been any updates to the shim-signed package in 18.04 since September of last year.

  I generally accept official updates (but not upgrades) to my Ubuntu
version 18.04 Bionic.
   I don't have a record of these updates but after one recent update
(about a week or two ago) I'm
   getting this warning "Failed to set MokListRT Invalid parameter secure
mode disabled" etc.

On Fri, May 21, 2021 at 2:15 PM Steve Langasek <email address hidden>
wrote:

> > I am getting the same error after an update to Ubuntu 18.04
>
> After updating from what to what? There have not been any updates to
> the shim-signed package in 18.04 since September of last year.
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1867092
>
> Title:
> Failed to set MokListRT: Invalid Parameter
>
> Status in grub2 package in Ubuntu:
> Invalid
> Status in mokutil package in Ubuntu:
> Invalid
> Status in shim package in Ubuntu:
> Triaged
> Status in shim-signed package in Ubuntu:
> Triaged
>
> Bug description:
> Hello,
> 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, 6.30.223.271+bdcom, 5.4.0-14-generic, x86_64:
> installed
> ExtraDebuggingInterest: Yes, if not too technical
> GraphicsCard:
> 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
> ProcEnviron:
> LANGUAGE=en_IN:en
> PATH=(custom, no user)
> XDG_RUNTIME_DIR=<set>
> LANG=en_IN
> SHELL=/bin/bash
> 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)
> dmi.bios.date: 07/24/2019
> dmi.bios.vendor: Apple Inc.
> dmi.bios.version: 229.0.0.0.0
> dmi.board.asset.tag: Base Board Asset Tag#
> dmi.board.name: Mac-6F01561E16C75D06
> dmi.board.vendo...

Please show logs (/var/log/apt/history.log) showing what versions of shim-signed you had installed before and after the problem started.

   OK, Here's the history.log file. I see I had some unintended upgrades.

On Fri, May 21, 2021 at 4:05 PM Steve Langasek <email address hidden>
wrote:

> Please show logs (/var/log/apt/history.log) showing what versions of
> shim-signed you had installed before and after the problem started.
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1867092
>
> Title:
> Failed to set MokListRT: Invalid Parameter
>
> Status in grub2 package in Ubuntu:
> Invalid
> Status in mokutil package in Ubuntu:
> Invalid
> Status in shim package in Ubuntu:
> Triaged
> Status in shim-signed package in Ubuntu:
> Triaged
>
> Bug description:
> Hello,
> 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, 6.30.223.271+bdcom, 5.4.0-14-generic, x86_64:
> installed
> ExtraDebuggingInterest: Yes, if not too technical
> GraphicsCard:
> 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
> ProcEnviron:
> LANGUAGE=en_IN:en
> PATH=(custom, no user)
> XDG_RUNTIME_DIR=<set>
> LANG=en_IN
> SHELL=/bin/bash
> 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)
> dmi.bios.date: 07/24/2019
> dmi.bios.vendor: Apple Inc.
> dmi.bios.version: 229.0.0.0.0
> dmi.board.asset.tag: Base Board Asset Tag#
> dmi.board.name: 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.0.0.0.0:bd07/24/2019:svnAppleInc.:pnMacBookPro9,2:pvr1.0:rvnAppleInc.:rnMa...

Ok, that log file shows no changes to the shim-signed package version installed.

There is an update to grub, which would trigger re-running grub-install, which would install the current shimx64.efi to your ESP.

I don't know why you would not have had an up-to-date shimx64.efi on your system previously, unless you had manually changed the contents of the ESP.

  I certainly didn't manually change the contents of the ESP (whatever that
is).
   Please tell me the command to update grub and re-run grub-insIstall?
   I was advised at one point never to upgrade but, apparently this
happened anyway
   unattended. Is there recommended software to protect Ubuntu against
malware?
   Thank you for your help.

On Fri, May 21, 2021 at 8:20 PM Steve Langasek <email address hidden>
wrote:

> Ok, that log file shows no changes to the shim-signed package version
> installed.
>
> There is an update to grub, which would trigger re-running grub-install,
> which would install the current shimx64.efi to your ESP.
>
> I don't know why you would not have had an up-to-date shimx64.efi on
> your system previously, unless you had manually changed the contents of
> the ESP.
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1867092
>
> Title:
> Failed to set MokListRT: Invalid Parameter
>
> Status in grub2 package in Ubuntu:
> Invalid
> Status in mokutil package in Ubuntu:
> Invalid
> Status in shim package in Ubuntu:
> Triaged
> Status in shim-signed package in Ubuntu:
> Triaged
>
> Bug description:
> Hello,
> 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, 6.30.223.271+bdcom, 5.4.0-14-generic, x86_64:
> installed
> ExtraDebuggingInterest: Yes, if not too technical
> GraphicsCard:
> 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
> ProcEnviron:
> LANGUAGE=en_IN:en
> PATH=(custom, no user)
> XDG_RUNTIME_DIR=<set>
> LANG=en_IN
> SHELL=/bin/bash
> 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 pr...

I also had this problem, cping grubx64.efi over shimx64.efi fixed the issue for me

Forgot to mention this is on a mid-2011 macbook air running Ubuntu 18.04 LTS which I just apt upgrade'd

Ok, thanks for the update.

On Sun, Jul 4, 2021 at 5:30 PM mipser <email address hidden> wrote:

> Forgot to mention this is on a mid-2011 macbook air running Ubuntu 18.04
> LTS which I just apt upgrade'd
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1867092
>
> Title:
> Failed to set MokListRT: Invalid Parameter
>
> Status in grub2 package in Ubuntu:
> Invalid
> Status in mokutil package in Ubuntu:
> Invalid
> Status in shim package in Ubuntu:
> Triaged
> Status in shim-signed package in Ubuntu:
> Triaged
>
> Bug description:
> Hello,
> 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, 6.30.223.271+bdcom, 5.4.0-14-generic, x86_64:
> installed
> ExtraDebuggingInterest: Yes, if not too technical
> GraphicsCard:
> 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
> ProcEnviron:
> LANGUAGE=en_IN:en
> PATH=(custom, no user)
> XDG_RUNTIME_DIR=<set>
> LANG=en_IN
> SHELL=/bin/bash
> 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)
> dmi.bios.date: 07/24/2019
> dmi.bios.vendor: Apple Inc.
> dmi.bios.version: 229.0.0.0.0
> dmi.board.asset.tag: Base Board Asset Tag#
> dmi.board.name: 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.0.0.0.0:bd07/24/2019:svnAppleInc.:pnMacBookPro9,2:pvr1.0:rvnAppleInc.:rnMac-6F01561E16C75D06:rvrMacBookPro9,2:cvnAppleInc.:ct10:cvrMac-6F01561E16C75D06:
> dmi.pro...

Just wanted to chime in and say that on my Mac Mini late 2014 (macmini7,1), Ubuntu Server 22.04 no longer exhibits this problem (but 20.04 does.)