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.
Could you leave
journalctl -f
running while Firefox is starting? Anything interesting happening right after initiating the start and/or before it actually starts?The only thing that came up was some memory allocation/cgroup/.slice stuff for the container.
I’m not on that network anymore, and the problem is gone. So I cant reproduce.
Maybe I should have run wireshark?
I mean, you could, sure.
As a next sensible step though, I’d start firefox from the CLI with more verbose logs enabled.