Closed Bug 1782286 Opened 4 years ago Closed 3 years ago

Firefox is unusable on Ventura Public Beta 2

Categories

(Firefox :: Address Bar, defect)

Firefox 103
Desktop
macOS
defect

Tracking

()

RESOLVED WORKSFORME

People

(Reporter: matthew.ogawa, Unassigned)

References

(Blocks 1 open bug)

Details

User Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_15_7) AppleWebKit/605.1.15 (KHTML, like Gecko) Version/16.0 Safari/605.1.15

Steps to reproduce:

Updated Firefox to version 103 and Ventura to Public Beta 2.
Restarted my computer.
Opened Firefox.

This happens on the Nightly and Beta builds as well. Launching in Rosetta 2 did not fix the issue.

Actual results:

Firefox became unresponsive.

  • Nothing loads in a tab
  • Creating a new tab works, but I cannot switch to the tab
  • I can type in the address bar, but nothing happens

Expected results:

Firefox works normally

Blocks: 1773708
OS: Unspecified → macOS
Hardware: Unspecified → Desktop

(In reply to Steven Michaud [:smichaud] (Retired) from comment #1)

Let me take a guess that you're doing this in a VMware Fusion VM. With default settings, networking doesn't work in this configuration. None of your apps should be able to reach the network.

The solution is here.

No virtual machine, this is running natively on my MacBook.

The Bugbug bot thinks this bug should belong to the 'Firefox::Address Bar' component, and is moving the bug to that component. Please correct in case you think the bot is wrong.

Component: Untriaged → Address Bar

QA doesn't have yet have mac 13 preview for testing, so nothing we can do here to confirm at the moment.

Later edit: I stand corrected, we do :).

I'm not able to reproduce this issue on the latest versions Firefox 104.0.1, Nightly 106.0a1 and Firefox 105.0b4 on Ventura 13.0. I'm able to search in Firefox by specific terms or web addresses and the websites are loaded properly in both current and new tab.
Closing this as resolved:worksforme.

Status: UNCONFIRMED → RESOLVED
Closed: 3 years ago
Resolution: --- → WORKSFORME

matthew,
Are you still seeing this problem?
If no, what resolved it for you?

Flags: needinfo?(matthew.ogawa)

I downgraded back to Monterey 12.6, in the end I didn't figure out what the issue was on Ventura.

Flags: needinfo?(matthew.ogawa)
You need to log in before you can comment on or make changes to this bug.