Removing base package using rpm-ostree

Hi everyone, happy user of aurora as daily driver. My question is how to properly remove/mask a base package. ubuntu-family-fonts and solaar are not required (the former is messing up rendering in some sites in chromium) and so I have done:

rpm-ostree override remove solaar ubuntu-family-fonts

This seems to work but on reboot nothing has changed. I just see “InactiveBaseRemovals: solaar ubuntu-family-fonts” when doing rpm-ostree status --verbose on the running image.
I’ve tried an override reset and doing it again from scratch but it doesn’t seem to have any effect.

Sorry if this has been answered previously, couldn’t find anything similar.


Update: today’s upgrade of the base image seems to have removed the packages :thinking: :thinking:

RemovedBasePackages: solaar 1.1.11-1.fc40 ubuntu-family-fonts 0.83-1.fc31

So perhaps it’s fixed now, or that triggering an upgrade removes the items that are in InactiveBaseRemovals. I’m not sure. Hope someone can shed light on this!

I don’t have an answer to your question but i hope someone will answer because i wanted to know the same thing, when i was using Bazzite i removed some softwares i didn’t need using the same command, then after some days it couldn’t update anymore because of that missing package making some kind of conflict, so i went back in time and it broke everything. Atomic distros are very new to me (only 2 weeks) but i think they really are the future so i will not go back to traditional distros, so i installed Bluefin instead which runs better with less softwares that i wanted to remove, so i removed only some of the flatpaks but i want to understand more about how things work without breaking them.


Other than some rare occassions there’s no reason to do local layering on a bluefin/aurora system. It doesn’t get you space back (it actually costs you more), and just slows down updates and reintroduces the jank we’re trying to get away from.

1 Like

So the smart thing to do would be to install the right distro which ships less software we don’t need and maybe only remove some flatpacks so we don’t mess with rpm-ostree and keep the image as it is, that is why i prefer using Bluefin over Bazzite, it has less stuff i don’t need even if i also use it for gaming.

Is there a reason why you prefer Bluefin over the main uBlue image?

The main reason is that i didn’t know i could just use the main Ublue image, i’m very satisfied with Bluefin at the moment, everything i do on it just works well, fast and better than on any other distro, i’m just not a fan of the dino logo. There is so much information out there that even after nearly 2 decades using Linux there is still so much i don’t know, thanx for asking this question, now that my curiosity is itching I’m going to get more info about Ublue.

1 Like

to do local layering

Are you talking about layering packages, overriding base packages, or both?

It doesn’t get you space back (it actually costs you more)

Is it always the case?
What’s the reason behind that?
Would that be able to be fixed? Maybe after using zstd:chunked?

Yeah both. I’m not sure on the technical details, I’m sure it’s in an upstream issue somewhere.

I’m not sure on the technical details

I wasn’t either, but deep diving into the implementation, I think it’s due to rpm-ostree not having implemented zstd:chunked yet

It is planned to be implemented in Fedora 41
This information has been affirmed again to me by a Red Hat employee less than 12h ago

I second this, is there away this can be changed to a Ublue logo or straight fedora logo please?

I want to know if possible and change it my self as its a personal preference. Just makes it feel, unprofessional imho (dino logo)

I have the same feeling about it, i wish i could have a more classy logo on my favorite distro.

@tolga_erok @visnu_Deva

Please kindly keep this post on-topic :slightly_smiling_face:

I created a post about the Bluefin Logo Feedback specifically