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.

  • somethingsomethingidk@lemmy.worldOP
    3·
    10 months ago

    Nope it’s all green.

    Idk if you saw my update but turning of the wifi fixes this problem.

    I did move to a new network yesterday, I just didn’t think that could impact the flatpak launch, while not affecting the systems binary launch.

    It’s a real head scratcher

    • rtxn@lemmy.worldEnglish
      2·
      10 months ago

      What brand and model is your wifi card? Linux has always had issues with Broadcom modules, but I don’t know why or how that would affect flatpak. Maybe you can find a relevant permission in Flatseal (like allowing the browser to control the wifi card) and turn it off for Firefox.

      • somethingsomethingidk@lemmy.worldOP
        2·
        10 months ago

        The card is Realtek. I found an askubuntu thread where all flatpak commands were hanging, and their solution was to disable the nic.

        This has only happened on this network. I didnt mention at first because I didnt think it mattered, but I’m visiting someone and moved networks.

        The instant I take the dev down, the browsers pop up. I would bet money that when I go to my home net everything will work.

        The flatseal angle didnt work either. The only reference is names on system bus.