This site will have limited functionality while we undergo maintenance to improve your experience. If an article doesn't solve your issue and you want to ask a question, we have our support community waiting to help you at @FirefoxSupport on Twitter and/r/firefox on Reddit.

Search Support

Avoid support scams. We will never ask you to call or text a phone number or share personal information. Please report suspicious activity using the “Report Abuse” option.

Learn More

Won't run on FreeBSD 14

  • 1 reply
  • 0 have this problem
  • 16 views
  • Last reply by TyDraniu

more options

I run FreeBSD 14 with Hyprland. Firefox always ran great up to version 123. Now anyway you run it it just hangs you can ctrl c to escape. I went back to 122 and it started right up. But now that pkg install has upgraded to 123 same thing just hangs. It compiles with no problems I changed config tried all setting but same thing. Please can someone figure this out. I have every browser ever made on freebsd but I love Firefox and I'm going crazy without it. I thought by running it from a terminal it might show a error but it just hangs and no messages with ctrl c. Any information you might need just ask me. Also when ran from terminal and htop shoes 1 core almost to 100%

I run FreeBSD 14 with Hyprland. Firefox always ran great up to version 123. Now anyway you run it it just hangs you can ctrl c to escape. I went back to 122 and it started right up. But now that pkg install has upgraded to 123 same thing just hangs. It compiles with no problems I changed config tried all setting but same thing. Please can someone figure this out. I have every browser ever made on freebsd but I love Firefox and I'm going crazy without it. I thought by running it from a terminal it might show a error but it just hangs and no messages with ctrl c. Any information you might need just ask me. Also when ran from terminal and htop shoes 1 core almost to 100%

All Replies (1)

more options

I guess the best option is to file a bug on https://bugzilla.mozilla.org.

If you can, try to run mozregression to narrow the problem.