Flatpak Firefox (and forks) very slow to start
Flatpak Firefox (and forks) very slow to start
While other flatpak apps have no problems. Any suggestions?
You're viewing a single thread.
Firefox is one of the few exceptions I suggest always use native version
12 0 ReplyIf 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.
3 1 ReplyNot 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
8 0 ReplyThe extension is probably not broken because of Firefox but because Flatpak's sandboxing prevents it from talking to KeePassXC.
6 1 ReplyI know. That's why I'm using native Firefox version, which works flawlessly
2 0 Reply
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
2 0 ReplyThe only "Firefox" not presenting this start issue for me is Floorp but it's proprietary.
4 0 ReplyRun it from the terminal to get more info.
Also run it through a profiler software like
perf
with the GUIhotspot
.Also, you are not by accident using secureblue, are you?
1 0 ReplyWhat is it? I'm on Bazzite.
1 0 ReplyDont mind then. Secureblue uses a strange hacky workaround for manking Flatpaks supposedly more secure.
So then try the other things I said.
1 0 Reply
Is floorp proprietary ?
1 0 Replyhttps://raw.githubusercontent.com/Floorp-Projects/Floorp-private-components/main/LICENSE
I'm not sure, Wikipedia says partially
2 0 Reply