DNF stuck at removing breeze-icon-theme

,

When I did a sudo dnf upgrade, the process freezed at Removing old breeze-icon-theme.

After half an hour, I killed the process and rebooted, and ran sudo dnf remove --duplicates, and it stuck again.

I tried erasing it directly with sudo rpm --erase but yielded the same result.

Here is the terminal output:

[ Irrelevant lines omitted ]
  Cleanup          : elfutils-default-yama-scope-0.186-1.fc35.noarch                                                                                                                 105/376 
  Obsoleting       : breeze-icon-theme-5.85.0-1.fc35.noarch                                                                                                                          106/376 
warning: file /usr/share/icons/breeze/apps/48/itinerary.svg: remove failed: No such file or directory
warning: file /usr/share/icons/breeze/actions/16/media-write-cd.svg: remove failed: No such file or directory
warning: file /usr/share/icons/breeze-dark/apps/48/itinerary.svg: remove failed: No such file or directory
warning: file /usr/share/icons/breeze-dark/actions/16/media-write-cd.svg: remove failed: No such file or directory


1 Like

Icon themes sometimes contain lots of files, and so they do take time. You should just let dnf run and finish it’s transaction. By interrupting it, you’ve not put your system in an inconsistent state :frowning: . Best to re-run dnf remove breeze-icon-theme and let it finish.

breeze-icon-theme has ~52000 files and the package manager needs to do quite a bit of computation to correctly install or remove all of them (because they do more than just put files in place, they also have to updated the package database etc.,):

$ sudo dnf repoquery -l breeze-icon-theme | wc -l
51595

In comparison, the kernel only has ~3000 files:

$ rpm -ql kernel-core-5.15.16-200.fc35.x86_64 | wc -l
2835

Someone else had reported another icon theme which took ~40 minutes on their system to install because it similarly had many tens of thousands of files.

It could be a bug or performance bottleneck in rpm, so you could file one if you wish and the rpm developer can take a look at it for you.

https://docs.fedoraproject.org/en-US/quick-docs/howto-file-a-bug/

1 Like