@[email protected] to [email protected] • 4 months agoFlatpak Firefox (and forks) very slow to startmessage-square61fedilinkarrow-up139arrow-down14file-text
arrow-up135arrow-down1message-squareFlatpak Firefox (and forks) very slow to start@[email protected] to [email protected] • 4 months agomessage-square61fedilinkfile-text
minus-square@[email protected]OPlinkfedilink2•4 months agoIf 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.
minus-squareResponsabilidadelinkfedilinkPortuguês8•4 months agoNot 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
minus-square@[email protected]linkfedilink5•4 months agoThe extension is probably not broken because of Firefox but because Flatpak’s sandboxing prevents it from talking to KeePassXC.
minus-squareResponsabilidadelinkfedilinkPortuguês2•4 months agoI know. That’s why I’m using native Firefox version, which works flawlessly
minus-square@[email protected]linkfedilink2•4 months agoFlatpak 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
minus-square@[email protected]OPlinkfedilink4•4 months agoThe only “Firefox” not presenting this start issue for me is Floorp but it’s proprietary.
minus-square@[email protected]linkfedilink1•4 months agoRun it from the terminal to get more info. Also run it through a profiler software like perf with the GUI hotspot. Also, you are not by accident using secureblue, are you?
minus-square@[email protected]linkfedilink1•4 months agoDont mind then. Secureblue uses a strange hacky workaround for manking Flatpaks supposedly more secure. So then try the other things I said.
minus-square@[email protected]OPlinkfedilink2•edit-23 months agohttps://raw.githubusercontent.com/Floorp-Projects/Floorp-private-components/main/LICENSE I’m not sure, Wikipedia says partially
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.
I know. That’s why I’m using native Firefox version, which 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
The only “Firefox” not presenting this start issue for me is Floorp but it’s proprietary.
Run it from the terminal to get more info.
Also run it through a profiler software like
perfwith the GUIhotspot.Also, you are not by accident using secureblue, are you?
What is it? I’m on Bazzite.
Dont mind then. Secureblue uses a strange hacky workaround for manking Flatpaks supposedly more secure.
So then try the other things I said.
Is floorp proprietary ?
https://raw.githubusercontent.com/Floorp-Projects/Floorp-private-components/main/LICENSE
I’m not sure, Wikipedia says partially