This bug was fixed in the package shim - 15+1552672080.a4a1fbe-0ubuntu2
---
shim (15+1552672080.a4a1fbe-0ubuntu2) focal; urgency=medium
* d/patches/fix-path-checks.patch: Cherry-pick upstream fix for regression
in loading fwupd, or anything else specified as an argument (LP: #18
This bug was fixed in the package shim - 15+1552672080.a4a1fbe-0ubuntu2
---
shim (15+1552672080.a4a1fbe-0ubuntu2) focal; urgency=medium
* d/patches/fix-path-checks.patch: Cherry-pick upstream fix for regression
in loading fwupd, or anything else specified as an argument (LP: #18
This bug was fixed in the package shim - 15+1552672080.a4a1fbe-0ubuntu2
---
shim (15+1552672080.a4a1fbe-0ubuntu2) focal; urgency=medium
* d/patches/fix-path-checks.patch: Cherry-pick upstream fix for regression
in loading fwupd, or anything else specified as an argument (LP: #18
Marking this as verification done. This was a regression in focal(devel)
regarding path lookup that was reverted prior to release, we have
validated that this works in groovy, and the binary is the same across
all releases, so this does not need per-series re-verification.
--
You received this bu
** Tags removed: verification-needed verification-needed-bionic
verification-needed-focal verification-needed-xenial
** Tags added: verification-done verification-done-bionic
verification-done-focal verification-done-xenial
--
You received this bug notification because you are a member of Ubunt
** Description changed:
+ (this is a regression of shim in groovy, fixed by new upstream release,
+ it can serve as regression test case for 15+1552672080.a4a1fbe-0ubuntu2
+ SRU)
+
The latest shim upload does not seem able to load fwupd. Selecting fwupd
in BIOS boot menu seems to go directly
Hello Julian, or anyone else affected,
Accepted shim into xenial-proposed. The package will build now and be
available at https://launchpad.net/ubuntu/+source/shim/15+1552672080
.a4a1fbe-0ubuntu2 in a few hours, and then in the -proposed repository.
Please help us by testing this new package. Se
Hello Julian, or anyone else affected,
Accepted shim into bionic-proposed. The package will build now and be
available at https://launchpad.net/ubuntu/+source/shim/15+1552672080
.a4a1fbe-0ubuntu2 in a few hours, and then in the -proposed repository.
Please help us by testing this new package. Se
Hello Julian, or anyone else affected,
Accepted shim into focal-proposed. The package will build now and be
available at https://launchpad.net/ubuntu/+source/shim/15+1552672080
.a4a1fbe-0ubuntu2 in a few hours, and then in the -proposed repository.
Please help us by testing this new package. See
** Changed in: oem-priority
Status: New => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1864223
Title:
shim 15+1552672080.a4a1fbe-0ubuntu1 fails to load fwupd
To manage notifi
This bug was fixed in the package shim - 15+1552672080.a4a1fbe-0ubuntu2
---
shim (15+1552672080.a4a1fbe-0ubuntu2) focal; urgency=medium
* d/patches/fix-path-checks.patch: Cherry-pick upstream fix for regression
in loading fwupd, or anything else specified as an argument (LP: #18
@seth-arnold +1
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1864223
Title:
shim 15+1552672080.a4a1fbe-0ubuntu1 fails to load fwupd
To manage notifications about this bug go to:
https://bugs.laun
I don't think that this broken package was announced widely enough --
the fallout from it cost my team perhaps an hour today. I don't know
where this was announced, but I think probably more places needed to
hear about it at the time.
Whoever works on shim, *please* announce future cases like this
Right, you have to force it to install the older version as I mentioned
in that post. Not sure if you did that or not based on your reply:)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1864223
Title
Ah, indeed, the "broken" one isn't even in the archive anymore, so there
is nothing I can upgrade to:
$ apt-cache policy shim shim-signed
shim:
Installed: 15+1552672080.a4a1fbe-0ubuntu1
Candidate: 15+1552672080.a4a1fbe-0ubuntu1
Version table:
*** 15+1552672080.a4a1fbe-0ubuntu1 100
1
This is a technical limitation, because we can't re-upload shim with a
higher version to downgrade people automatically, as we would not have a
signature for the binaries that upload would built.
And shim-signed has a versioned dependency on shim, as it needs to, so
we could not just bump the vers
People who had focal installed and uptodate prior to the beta (roughly)
won't get this working again until we can SRU a fixed shim binary or
they manually downgrade to the old versions in the release pocket.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is s
Hey @ahasenack,
You have the "broken" versions installed. You need to do the steps in
https://bugs.launchpad.net/ubuntu/+source/shim/+bug/1864223/comments/27.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net
I don't have boot order lock.
shim is 15+1552672080.a4a1fbe-0ubuntu1, shim-signed is
1.41+15+1552672080.a4a1fbe-0ubuntu1
Applying firmware updates isn't working. I reboot, nothing different
happens, I'm back in the desktop, and get another prompt to apply the
same firmware update.
** Attachment
** Changed in: shim (Ubuntu)
Milestone: ubuntu-20.04-beta => ubuntu-20.04.1
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1864223
Title:
shim 15+1552672080.a4a1fbe-0ubuntu1 fails to load fwupd
If the entry disappeared on it's own, that sounds like it's probably the
firmware's doing in somnething like "de-duping" entries. And it would explain
this behavior better. Something along the lines of:
1) Reboot system
2) Firmware runs de-dupe algorithm
3) Firmware tries to run BootNext (fails
Thanks Mario. The theory makes sense.
I _think_ that after boot with BootNext=, entry disappeared and
BootCurrent was 0001 (but I cannot be 100% sure as I did not save the config at
the time).
My firmware _did_ respect BootNext when it was set to 0002, and it was
the only updater entry.
>From your circumstances I don't believe there is any evidence to support
that shim attempted to load fwupd, nor evidence that boot entry was even
used.
The only way to prove this would be to look at what "BootCurrent" was
set to after a "failed" attempt. If it's set to Boot0001 then your
firmwar
Before raising the issue with fwupdmgr, why did not shim load the
updater from the entry as instructed by BootNext? Configuration
looks strange, but legit to the eye. Does shim or firmware check for
duplicate entries? Does shim or firmware not allow to use entry 0?
Right now, I am unsure what
OK thanks for confirming it's not cause by boot order lock.
I think that your scenario is a separate issue from the shim one
entirely. I would recommend bringing it to discussion upstream to
figure out why the entry didn't get re-used. It could be a firmware
issue too.
--
You received this bug
I did not change any bios settings since upgrade from eoan, and firmware
update worked in eoan.
But I found something interesting.
In "normal life" my efi configuration looks like this:
BootCurrent: 0001
Timeout: 0 seconds
BootOrder: 0001,0019,001A,001B,001C,001D,001E,001F,0020,0021,0022,0023,00
@crosser:
If you're matching the version of shim and shim-signed in the archive
now and hitting this problem you have a different issue. It's notable
that your manufacturer has a firmware option for boot order locking that
is commonly causing similar behaviors. If you have enabled it, you may
wa
crosser@journex:~$ apt policy shim-signed
shim-signed:
Installed: 1.40+15+1533136590.3beb971-0ubuntu1
Candidate: 1.40+15+1533136590.3beb971-0ubuntu1
Version table:
*** 1.40+15+1533136590.3beb971-0ubuntu1 500
500 http://ftp.tu-ilmenau.de/mirror/ubuntu focal/main amd64 Packages
Meant to sat "thanks" in my last post too:)
Anyways, here is the command to downgrade the packages if you are
affected by this:
$ sudo apt install shim=15+1533136590.3beb971-0ubuntu1 shim-
signed=1.40+15+1533136590.3beb971-0ubuntu1
Thanks again!
--
You received this bug notification because y
Oh, you have to manually downgrade the packages to what's in main now?
I guess that should be documented somewhere for those of us who are
affected by this since it's not obvious (at least to me:)) that's what
one needs to do.
--
You received this bug notification because you are a member of Ubun
The bad versions have been demoted to proposed, and were removed
recently. You need a shim-signed 1.40.something installed, 1.41 was
broken.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1864223
Title
jik, I can't tell you what's going on on your device.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1864223
Title:
shim 15+1552672080.a4a1fbe-0ubuntu1 fails to load fwupd
To manage notifications a
Could it be that newer "bad" versions continue to linger on ubuntu
mirrors?
Julian, can you post here, which version is known to work and is going
to the official distro?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.la
If "you don't get downgraded to [the working versions] if you caught the
broken one," then can someone explain to me how my laptop suddenly
successfully upgraded two different firmware files after it failed to do
so for weeks presumably because of this bug?
--
You received this bug notification b
Yes that's what the bug report is about - those are the broken versions.
We reverted to older ones. You don't get downgraded to them if you
caught the broken one, it's not technically possible.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to U
Eugene I'm sure you misconfigured something. You need to downgrade shim-
signed (not only shim).
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1864223
Title:
shim 15+1552672080.a4a1fbe-0ubuntu1 fai
I have shim 15+1552672080.a4a1fbe-0ubuntu1 and shim-signed
1.41+15+1552672080.a4a1fbe-0ubuntu1 installed on my 7th gen Lenovo
Carbon X1 and it still fails to boot the firmware updater properly.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to U
I see 1.40+15+1533136590.3beb971-0ubuntu1 in the main focal repo, and
15+1552672080.a4a1fbe-0ubuntu1 in -proposed. Neither of them load
fwupdx64.efi for me?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bug
We reverted the shim upload in focal. A fixed one will be released after
focal release.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1864223
Title:
shim 15+1552672080.a4a1fbe-0ubuntu1 fails to loa
I think this has been fixed in focal? Within the last few days (I
believe) my laptop successfully installed the firmware updates that had
been failing to install because of this issue.
Which is weird because the bug says it's in shim, but my dpkg log says
the last time the shim package was updated
** Tags added: focal
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1864223
Title:
shim 15+1552672080.a4a1fbe-0ubuntu1 fails to load fwupd
To manage notifications about this bug go to:
https://bugs
** Also affects: oem-priority
Importance: Undecided
Status: New
** Changed in: oem-priority
Importance: Undecided => Critical
** Changed in: oem-priority
Assignee: (unassigned) => Rex Tsai (chihchun)
--
You received this bug notification because you are a member of Ubuntu
Bugs
** Tags added: oem-priority
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1864223
Title:
shim 15+1552672080.a4a1fbe-0ubuntu1 fails to load fwupd
To manage notifications about this bug go to:
https
@juliank,
If it's unlikely that this is done before the release can we revert back
to the older shim for release and bump up to this new one after it comes
through?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpa
@Julian, of course I understand the implications. Thank you for the pointer.
(Is it an option to revert to previous signed shim for the release? It did
work.)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/
Let's be clear: I don't want you to test it - You need a machine w/
secure boot disabled, and need to replace shim-signed with shim and
manually replace the shim binary to the ESP. You'll end up with an
unsupported system.
That said, it is in its usual location, the uefi development ppa:
https://
If there is an updated package available, I am willing to test it on my
system..
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1864223
Title:
shim 15+1552672080.a4a1fbe-0ubuntu1 fails to load fwupd
Removing the sponsors team, as there's nothing to sponsor here.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1864223
Title:
shim 15+1552672080.a4a1fbe-0ubuntu1 fails to load fwupd
To manage notif
The attachment "shim_15+1552672080.a4a1fbe-0ubuntu2.debdiff" seems to be
a debdiff. The ubuntu-sponsors team has been subscribed to the bug
report so that they can review and hopefully sponsor the debdiff. If
the attachment isn't a patch, please remove the "patch" flag from the
attachment, remove
We already have an ubuntu2 in the shim PPA. It's blocked by
https://github.com/CanonicalLtd/shim-review/pull/1
** Changed in: shim (Ubuntu)
Status: Triaged => In Progress
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https:/
I have rebuilt shim from focal with the suggested patch from upstream
and can confirm that with the resulting shimx64.efi (and Secure Boot
disabled) shim would successfully launch fwupd as expected and pending
firmware updates were successfully installed. See attached for the
debdiff used in this c
As confirmed on the upstream bug:
Commit
https://github.com/rhboot/shim/commit/e563bc3dcd17d91861d3b363ed19d30228f409e1
caused the issue, and it was already fixed by upstream commit
https://github.com/rhboot/shim/commit/1870bae796022f8bbf60465352eac329ff1d6ffd
--
You received this bug notificati
@Steve
Yes; from what I can gather this will definitely require source
modifications to shim.
The concern I have is that beta is the milestone that many more people
start to download and actually start testing Ubuntu images. With how
widely OEMs support UEFI firmware updates now, I expect a larg
Mario, you've set a beta milestone for this but if this requires changes
to the shim source, that is not achievable without us rolling back to an
earlier version of shim-signed. We are not going to have this fixed and
re-signed by Microsoft in time for beta.
--
You received this bug notification
** Changed in: shim (Ubuntu)
Milestone: None => ubuntu-20.04-beta
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1864223
Title:
shim 15+1552672080.a4a1fbe-0ubuntu1 fails to load fwupd
To manage
Right, tracking this in https://github.com/rhboot/shim/issues/194
** Bug watch added: github.com/rhboot/shim/issues #194
https://github.com/rhboot/shim/issues/194
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchp
To clarify my comment #1: update files are installed in
/boot/efi/EFI/ubuntu/fw, but on reboot, there is no sign of fwupdx64.efi
ever running, boot process goes straight to grub.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://
Yes
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1864223
Title:
shim 15+1552672080.a4a1fbe-0ubuntu1 fails to load fwupd
To manage notifications about this bug go to:
https://bugs.launchpad.net/ub
I think that it happens to me, and it's regression going from eoan to
focal. Firmware updates are downloaded and installed, and even if I set
BootNext by hand, it is bypassed.
Linux-Firmware-Updater looks suspicious to me:
# efibootmgr -v|grep Linux-Firmware-Updater
Boot0002* Linux-Firmware-Updat
59 matches
Mail list logo
