Swarf, In that AI generated text there are what appear random ".5" and ".4" inserted for unknown reason. Maybe you can edit those out to improve readability.
Oh im having this issue too but im also having secure boot disabled so i can ignore this. I have been thold that secure boot is just microsoft's way to continue spying on linux users, is this true or false?
I would call this "False."
You may be thinking of the TPM chip, which includes a backdoor for Microsoft to access; the given reason is that an end user may need Microsoft to access directly in order to troubleshoot.
My primary objection is... When does Microsoft ever help end users troubleshoot?
Either way, Secure Boot is a curated list, like a bouncer at a night club, that only allows Microsoft Signed programs to initialize at boot. While that can have issues if Microsoft has not signed on a program - it does not contain any spyware.
They refer to the external sources in order listed at the bottom, i.e., sources that went to producing the main body. Discourse can't cope with lower indices from clipboard.
I finally got fed up and uninstalled fwupd with
- sudo apt purge fwupd
- sudo apt autoremove
and am done with it
- if you don't need it all the time (or ever)
Only use Zorin OS 17 Pro
No dual boot and no secure boot (disabled in bios)
is a radical solution but effective
3 Likes
If other distros can achieve smooth DBX updates, it puts the onus on Zorin OS to analyze its own implementation and find ways to improve.
2 Likes
Hello!
I was resolve that issue on fresh install of Zorin Core 17.3 with all commands: first two and other 4 commands. Otherwise I'm Zorin user almost two years, 17.1 was been my first installation. And I like it very much. I hope to will others resolve that issue also.
Best regards from Slovenia!
I did the same thing on my second laptop, a Lenovo where I could not remove the problem as I could with my HP notebook, and completely uninstalled Zorin 17.3 Core's pre-installed ‘fwupd’ and installed the latest/candidate fwupd 2.0.12 version, and the error no longer appeared. Here is the link where you can obtain the latest version candidate: Install fwupd on Linux | Snap Store
1 Like
This shows that an emergency backport fix is needed from the Zorin Group as a .DEB (not everyone has snap; I've disabled it on my setup). But why is this crucial update available only as a snap? That really sucks. Kinda gives validation to what I've said before about Zorin needing to change its code base over to Debian, too. And it goes to highlight the need for the Zorin Group to release more up-to-date versions of Zorin OS quicker so these kind of things can be prevented.
1 Like
We wouldn't want them to prioritize speed over stability, though.
Distro maintenance is difficult. They're the experts, so I expect they have their reasons for going this particular speed (compatibility/stability and security testing, most likely -- with a dash of sanity maintenance).
Uninstalling the fwupdmr altogether seems like an odd hack to get rid of the update and error message, but doesn't solve the underlying problem (update the dbx). Furthermore, I think fwupdmgr is used to update other firmware too (like USB devices and dongles), so removing it doesn't seem great.
I would like to know what experts think about the snap solution/workaround.
- The new fwupdmgr seems like a path to the solution, but in lieu of an updated version in the distro, is there some obvious problem with it as a snap?
- As a snap, can it be temporarily installed alongside the system fwupdmgr just to get this particular update? (I thought that was part of the point of snaps, though you may possibly need to use the explicit path to the snap fwupdmgr to make the terminal calls)
2 Likes
Very much agree re. speed vs stability.
I chose Zorin after trying a half dozen different distros because I realised stability was a key factor for me. One distro that I was initially very excited about had an update, and a part of it broke. I realised that being on the cutting edge was a price I didn't care to pay for.
The offset is situations like this, but I think so long as these sort of circumstances are on the rarer side (relatively) speaking, it's probably still the right distro for me.
Everything's a compromise; I think it's a question as to what soup (i.e. compromise) each Goldilock's prefers.
1 Like
I assume everyone has read this post, some days ago, by the devs? Secure Boot Update failed - #9 by AZorin or same here Problems with Secure boot - #30 by AZorin
The latter of the two was referenced (linked) by Aravisian in his OP at the top of this thread.
After spending some time researching this issue further, we've identified and created a potential solution for it with the standard fwupd package (APT). However, it would need to be tested more thoroughly to ensure that it fully resolves the issue and doesn't introduce any regressions that would affect the stability of the system in general.
How to test the solution
If you're still experiencing this issue – even after following the steps I mentioned in this post – and you're happy to test pre-production software, you can apply this solution by opening the Terminal (Ctrl+Alt+T) and entering these commands:
sudo add-apt-repository ppa:zorinos/fwupd
sudo apt update
sudo apt dist-upgrade
After installing all updates, please restart your computer to apply the changes.
To make sure that the original stuck firmware update gets installed, you can open the Terminal and enter these four commands:
sudo fwupdmgr refresh
sudo fwupdmgr get-updates
sudo fwupdmgr update
sudo rm /var/lib/fwupd/pending.db
Finally, restart your computer once more to resolve the original issue fully.
Feedback
Please let us know if following these steps to test this solution resolved the original issue for you. In addition, please let us know if you noticed any stability issues with other parts of the system during everyday use after applying this solution.
This information would help us to fully prepare this solution to be potentially included as a software update for all Zorin OS 17 users.
13 Likes
Thank you very much, Artyom. Your communication is appreciated. And yes. Looks like what I said elsewhere on this forum was basically correct; that you guys need to issue an emergency fix via APT (.DEB). Sounds good. I am sure other users will be happy to hear this. Again, thank you very much for all you and Kyrill do.
@AZorin
Hello Artyom,
thanks for the information, I reinstalled fwup apt to test and then followed your instructions.
After the steps it looks like the error message no longer appears.
It seems to work.
1 Like
This is, I hope, good news for users who failed to fix the persistent error and install the annoyingly specific UEFI DBX security update. I solved the problem myself, so I won't worry about it again, as so far everything is working normally.
1 Like
- Original issue resolved
- I'll report back re. stability in a few days
1 Like
@AZorin, computer has been stable since fix applied.
2 Likes
I can confirm this resolved my issue on a Dell laptop.
3 Likes