Edit:
I turned off my wifi card, and now it launches immediately. Of course, what is a browser with no internet. But I guess there’s something about the network I moved to thats causing the delay. I’ll try a different network tomorrow and update for science
OG post: This applies to librewolf and firefox flatpaks. Just to preface, I’ve been using these flatpaks for years and never experienced anything like this.
This morning I did my business as normal with no issues. I usually open and close firefox alot and it takes maybe 10-30 seconds to start.
Then I shutdown for awhile. Came back and fired up firefox… nothing happened. The process is not using any cpu, it just sits. I kill the process and try again nothing changes. After 3-5 minutes, the window finally pops up.
My system installation of firefox works fine. So does the flatpaks for qutebrowser and tor browser. I ran flatpak repair and reinstalled them. Nothing has changed.
I didn’t make any changes to my system. There were no significant updates. I have no idea why this started.
If anybody has any tips on troubleshooting this, I would appreciate it.
Btw I’m on fedora39, and I’ve tested this on sway, gnome, hyprland, and gnome on xorg.
I’ve been considering switching to Linux, but did you say Firefox takes 30 seconds to start? Is that standard? Edit: what a strange bunch you are to downvote a random question.
No, it opens without delay.
Yeah I am on a potato, i just gave that as a reference. Its really probably more like 10 the first time it opens. After that its faster.
Excellent, thank you.
Non-sense, any linux, even the most wasteful in resources, ubuntu, mint, manjaro, debian, fedora, gnome plasma DE, uses a fraction of resources to start and execute whatever. I have 2-3 friends running daily on early/mid 2core intel/amd machines where w10/11 wouldn’t even boot!
@Suspiciousbrowsing @somethingsomethingidk