While other flatpak apps have no problems. Any suggestions?
Firefox is one of the few exceptions I suggest always use native version
If it is due to an inefficiency of Firefox it seems strange to me that no fork has solved the problem, other browsers like Brave work perfectly.
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
The extension is probably not broken because of Firefox but because Flatpak’s sandboxing prevents it from talking to KeePassXC.
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
The only “Firefox” not presenting this start issue for me is Floorp but it’s proprietary.
Is this new, or has it been happening for a few days/weeks? I’m on Fedora Atomic (which Bazzite is based on) and have never experienced this (though I mostly use Mullvad browser, a fork of Firefox). I tried Bazzite a few weeks ago and also never experienced this with the Firefox flatpak. If it’s been happening for awhile, it may be hardware-specific or a config thing. Out of curiosity (just to get a 1:1 comparison), do you experience the same thing with the Mullvad browser flatpak?
I’m on a fresh install. I experienced this with Firefox, LibreWolf and Waterfox.
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
Any issues lately with your network? When DNS is down or having issues, Firefox and forks take forever to start up.
Nothing special, I don’t think that’s the problem since the lag is at every launch and it takes something like a minute to appear.
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.
I have many flatpak apps bork down on me (steam, wine, emulators…) just install from your distro repo instead and only use flatpak if you don’t have other choices
You’re on X or Wayland?
