Flatpak Firefox (and forks) very slow to start

Not only because of performance issues, but also because it's clunky sometimes. For example, I cannot use KeePassXC Browser extension on Flatpak Firefox cause this implementation is borked. However in native version works flawlessly

Flatpak Firefox and Chromium are very different. Note that Flatpak Firefox starts normally fast for me.

Use the native version, it is one of the best maintained software and has access to "user namespaces" for isolation.

Now search on the internet what that is XD

Hm, it could be a new issue then. I'm not seeing it on the Bazzite issues page, perhaps you should open a new issue on it here, and provide your hardware specs. At the very least, you could see if this issue is reproducible on other installs, and someone there could help to obtain more useful debug info to determine the actual problem. You could also report it on the Mozilla Bugzilla page, as chances are this is a Firefox issue and not a Bazzite issue, but I admit that the interface for bug reports is less intuitive for non-developers there. Bazzite devs would likely direct you to there first anyway though.

All I can really say myself is that I don't experience this on Fedora Atomic KDE 40.20240607 with Mullvad Browser or the Firefox flatpak. I suspect it is either a hardware/config issue (on fresh install, I'd say a config issue is a distro issue if you haven't changed anything), or that this is Bazzite specific and not present in upstream Fedora Atomic. Regardless, it's a good idea to report this so that other users don't experience the same bug

It also happens when the hosts file is messed up and the system can’t resolve its own hostnames. Opensuse used to be pretty notorious for doing something odd to the hosts file by default that really only affected Firefox.

Edit: the increased security they’re trying around the browser might also be triggering that local resolution issue

I don’t think that’s the problem

Listen to the parent, this is almost certainly something to do with DNS (i.e. Firefox is not getting an answer for some reason, then timing out, then using maybe a backup DNS server; maybe there are multiple rounds of this). Who knows how your distro and that flatpak produce this interaction, but something is going on there.

Sorry for giving a rather useless advice. Of cause, you know about native packages, but since you are asking about flatpak, you, probably, have a reason to chose it. So, my original message was mostly intended as a joke, for which I am sorry.

Yeah that is a dumb decision of the uBlue folks. I really like their tooling but their Flatpak browser stuff (and a bit more) are annoying.

You also cant even layer Firefox, due to this rpm-ostree bug

https://github.com/coreos/rpm-ostree/issues/4554

Make some noise there if you want.

Probably best that you do the same (installing packages in the FS overlay kind of starts to defeat the point of containerization). You could try installing it with a distrobox and then exporting the app—see if that fixes your loading issues.

I run Bazzite on a gaming laptop from 2015, and I haven't noticed any particularly long load times. Do you have some browser extension(s) that are maybe causing issues?

IMHO I would avoid the ublue distros and just go for official fedora spins. The guys have good intentions, but they don't have the means to maintain that many distros "properly". I often end up enabling copr packages for bazzite in my fedora install, just to find out the program doesn't work.

That being said, as the other comments told you, you can still install native apps on immutable distros, it's just a bit more work. I don't expect distrobox or toolbox to be much faster than flatpak, as they are all just containers with a nice cli, except flatpak is easier to update. But trying costs nothing

Except Ubuntu b/c they’re pushing snaps.