View Issue Details

IDProjectCategoryView StatusLast Update
0002278Rocky-Linux-9fwupdpublic2023-11-21 22:09
ReporterDanie de Jager Assigned ToLouis Abel  
Status closedResolutionwon't fix 
Summary0002278: uninstall fwupd prevent system to boot due to shum-x64 removal
DescriptionI cleaned up a host running Rocky 9.1. I removed fwupd as I did not need it as I'm running the host in the cloud which won't have any firmware updates.
I did not fully appreciate the consequences of what will happen when removing shim-x64 will have on my life.

Due to the current dependencies fwupd effectively becomes a required package, even if I don't have a host that would be supported by it. Can the dependency be revaluated not to remove shim-x64? I can see that shim-x64 would be required and should already be installed on the host but can it stay behind when uninstalling something like fwupd and not cause other users to break their systems?
Steps To Reproduceyum remove fwupd -y

 fwupd x86_64 1.7.9-1.el9 @baseos 7.1 M
Removing dependent packages:
 shim-x64 x86_64 15.6-1.el9.rocky.0.1 @baseos 4.5 M
Removing unused dependencies:
 bubblewrap x86_64 0.4.1-6.el9 @baseos 102 k
 flashrom x86_64 1.2-10.el9 @appstream 1.8 M
 fwupd-plugin-flashrom x86_64 1.7.9-1.el9 @appstream 2.1 M
 libgcab1 x86_64 1.4-6.el9 @baseos 207 k
 libjcat x86_64 0.1.6-3.el9 @baseos 181 k
 libsmbios x86_64 2.4.3-4.el9 @baseos 388 k
 libxmlb x86_64 0.3.3-1.el9 @baseos 279 k
 mokutil x86_64 2:0.4.0-9.el9 @baseos 90 k
TagsNo tags attached.


Danie de Jager

Danie de Jager

2023-02-17 07:58

reporter   ~0002511

I made a typo on the summary. The package is shim-x64
Louis Abel

Louis Abel

2023-02-17 08:58

administrator   ~0002512

Thank you for the report.

We understand the need to "debloat" or remove "unnecessary" packages. This is a case where there are package dependencies outside of our control.

In majority of cases, package dependencies are determined at build time. In this report, shim-x64 requires dbxtool and fwupd provides dbxtool.

[root@xmpp01 ~]# rpm -q shim-x64 --requires
dbxtool >= 0.6-3
mokutil >= 1:0.3.0-1
rpmlib(CompressedFileNames) <= 3.0.4-1
rpmlib(FileDigests) <= 4.6.0-1
rpmlib(PayloadFilesHavePrefix) <= 4.0-1
rpmlib(PayloadIsZstd) <= 5.4.18-1
[root@xmpp01 ~]# dnf repoquery -q --whatprovides dbxtool

There's unfortunately no (recommended) way around this, other than to run the cloud images in BIOS mode and remove the packages then. We will likely not make adjustments to the packages as it would make us deviate from upstream (RHEL) behavior. RHEL and CentOS stream has this behavior and thus we inherit it.

Ultimately, it may be better to report this upstream to They may be able to provide clarification on why it is the way it is and/or if they would be open to adjusting the behavior, which could potentially come down to us in 8.8 and 9.2.

Setting to acknowledge for the time being.
Danie de Jager

Danie de Jager

2023-02-17 11:18

reporter   ~0002513

I logged a ticket on Red Hat Bugzilla:
Louis Abel

Louis Abel

2023-11-21 22:09

administrator   ~0005195

Upstream closed ticket as not a bug. Closing downstream ticket.

Issue History

Date Modified Username Field Change
2023-02-17 07:55 Danie de Jager New Issue
2023-02-17 07:58 Danie de Jager Note Added: 0002511
2023-02-17 08:58 Louis Abel Assigned To => Louis Abel
2023-02-17 08:58 Louis Abel Status new => acknowledged
2023-02-17 08:58 Louis Abel Note Added: 0002512
2023-02-17 11:18 Danie de Jager Note Added: 0002513
2023-11-21 22:09 Louis Abel Status acknowledged => closed
2023-11-21 22:09 Louis Abel Resolution open => won't fix
2023-11-21 22:09 Louis Abel Note Added: 0005195