Bug 2166185

Summary:	firefox won't open in gnome using AMD ATI FirePro W5100
Product:	[Fedora] Fedora	Reporter:	Basil Eric Rabi <ericbasil.rabi>
Component:	firefox	Assignee:	Gecko Maintainer <gecko-bugs-nobody>
Status:	CLOSED DUPLICATE	QA Contact:	Fedora Extras Quality Assurance <extras-qa>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	37	CC:	erack, gecko-bugs-nobody, jhorak, klaas, pjasicek, rstrode, sandmann, stransky
Target Milestone:	---
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2023-02-01 20:06:13 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Basil Eric Rabi 2023-02-01 05:24:13 UTC

Description of problem:
I recently installed fedora 37 to my old machine which formerly uses fedora 35. I used gnome and I noticed firefox won't open anymore. Opening it via terminal shows no response either. When I switched to sway window manager, I can open it via alacritty and it shows some message:

$ firefox
Crash Annotation GraphicsCriticalError: |[0][GFX1-]: glxtest: VA-API test failed: no supported VAAPI profile found. (t=0.537796) [GFX1-]: glxtest: VA-API test failed: no supported VAAPI profile found.
Crash Annotation GraphicsCriticalError: |[C0][GFX1-]: Couldn't sanitize RENDERER device: BONAIRE (t=35.161) [GFX1-]: Couldn't sanitize RENDERER device: BONAIRE

Version-Release number of selected component (if applicable):
firefox-109.0-4.fc37.x86_64

Additional info:
Maybe this is related to hardware but firefox works for me without this issue in fedora 35 gnome.
Host: HP Z640 Workstation
CPU: Intel Xeon E5-2620 v4 (32) @ 2.100GHz
GPU: AMD ATI FirePro W5100

Comment 1 Martin Stransky 2023-02-01 20:06:13 UTC

Dupe of Bug 2147344. Will update Fedora package soon.

*** This bug has been marked as a duplicate of bug 2147344 ***