I wish Firefox would not be a system app. Options should be available. I don’t and wont ever use this browser for many reasons and so for me I don’t even want it on my system. I’m using Silverblue and like it for my desktop, not my laptop. I think if I tried removing it the system would probably crash, maybe not but don’t want to take the chance.
2 Likes
Looks like 5 years ago someone had the same thought. Personally I use Vivaldi but I guess Firefox is still hanging around somewhere…
You can remove firefox by using the following command in the terminal then giving your system a reboot.
rpm-ostree override remove firefox firefox-langpacks
3 Likes
Technically, the command from the previous post will not remove the Firefox packages. They will still be present in the underlying OSTree repository, but they will not be visible. Personally, I would recommend the following approach:
If you really need to remove Firefox or any other package from an Atomic Desktop base image, you can do so by building a derived image from the still unofficial bootable container images. Once you have build your customized image, you will probably also want to rechunk it before switching to it.
1 Like
Personally I don’t see the point of removing Firefox from the base image. I use Vivaldi but Firefox is still present on my system. My son might use it if he is trying to do something like solve a problem that I encountered. But it really isn’t causing me any issues by being there either.
YMMV… Each to his own I guess…
2 Likes
Not a good idea… Hi, new member here! Proud user of silverblue. With nvidia drivers, its really hard to have hardware decoding with firefox flatpak (at least the first 4: H264-VP9-VP8-AV1-HEVC). Libva/about:config/flatseal, i spend my day before i realize that rpm firefox just work and the only thing i have to change is one line in about:config. Please, dont remove firefox from the base system, it just works.
Hello @domenico and welcome to 
!
I’m currently using AMD Radeon RX 5700 and Firefox from Flathub and hardware decoding works fine. Your issues are likely not related to Firefox from Flathub.
It’s extra drive/SSD writes to update an unnecessary package, or a version lock that might be forgotten after a while (leaving FF not updated, that might get accidentally opened at a later date). It’d also move every icon past F down an extra space on GNOME 
1 Like
Thanks. My issues are not related to amd and firefox from flathub, but from nvidia proprietary drivers and hardware decoding with firefox from flathub. Hardware decoding is a mess when you try to connect gpu drivers and firefox flatpak from flathub: disable this, add this, after august 2025, dont do this, if you have vaapi dont do that… With RPM version, its easy. Maybe, maybe its a good reason to keep rpm firefox in silverblue, no?
Not really with Atomic - the overrides are done locally on the machine so you still need to download the image/package updates before then being discarded from the final boot image.
1 Like
Fedora does not support proprietary third-party software, nor does it guarantee that it will work properly if installed.
Considering the above, I personally don’t think so.
You may also find the following informative:
1 Like
Browsers are just a basic service for system applications, and they can be Firefox or any other; it’s just that Fedora chose Firefox. You haven’t considered situations without internet access, such as local preview and debugging, maybe just accessing a router’s management interface. Of course, you can uninstall it after installing another browser; it’s just an application.
2 Likes