Bug 2277223 - Firefox on Fedora WS 40 inside VMWare Fusion (Intel, M1) takes several minutes to open
Summary: Firefox on Fedora WS 40 inside VMWare Fusion (Intel, M1) takes several minute...
Keywords:
Status: NEW
Alias: None
Product: Fedora
Classification: Fedora
Component: firefox
Version: 40
Hardware: All
OS: Linux
unspecified
medium
Target Milestone: ---
Assignee: Gecko Maintainer
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2024-04-25 20:11 UTC by Mike B.
Modified: 2024-05-06 12:18 UTC (History)
6 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed:
Type: ---
Embargoed:


Attachments (Terms of Use)

Description Mike B. 2024-04-25 20:11:24 UTC
After upgrading to F40 Workstation on VMs with mac host (both M1 and Intel based macs, virtualization with VMWare Fusion), Firefox takes over 4 minutes to open.

The same happens when running firefox --safe-mode from terminal.

Reproducible: Always

Steps to Reproduce:
1. Install Fedora WS 39
2. Upgrade to Fedora WS 40
3. Open Firefox.
Actual Results:  
Firefox opens after several minutes.

Expected Results:  
Firefox opens in 1-2 seconds.

Comment 1 Mike B. 2024-04-26 06:19:55 UTC
Same behaviour on a freshly installed F40 WS.

Comment 2 Mike B. 2024-04-27 10:38:15 UTC
Additional info: changing the Fedora VM’s Network Adapter settings from NAT to Bridged solves the issue.

Other user on Fedora Discussion reports a similar issue in a non-VM environment: workaround was to disable a firewall he was using.

Comment 3 Martin Stransky 2024-05-06 05:57:39 UTC
Looks like DNS lookup issue, Firefox is very slow if DNS is broken.

Comment 4 Mike B. 2024-05-06 12:18:12 UTC
I have noticed the same behaviour with the Anaconda Installer, when launching it from a live session. Changing the Network Adapter settings fixes it too.

I am posting this here in case the 2 issues are related.


Note You need to log in before you can comment on or make changes to this bug.