Bug 2190179

Summary:	Chromium doesn't launch as a native wayland apps when in wayland session
Product:	[Fedora] Fedora	Reporter:	Chanon Somwang <noninmeet20210618>
Component:	chromium	Assignee:	Tom "spot" Callaway <spotrh>
Status:	CLOSED WONTFIX	QA Contact:	Fedora Extras Quality Assurance <extras-qa>
Severity:	medium	Docs Contact:
Priority:	unspecified
Version:	38	CC:	spotrh, than, tpopela, yaneti
Target Milestone:	---	Keywords:	Regression
Target Release:	---
Hardware:	x86_64
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2023-07-14 10:37:21 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Chanon Somwang 2023-04-27 12:42:45 UTC

Formerly I use chromium-freeworld which use the wayland ozone platform when wayland session is being used, The fedora chromium package's changelog indicate that fedora's chromium package used to follow the same behavior so I assume this is a regression.

Reproducible: Always

Steps to Reproduce:
1.Launch chromium using the application menu or command line
2.Type chrome://gpu in the address bar
3.Check the value of "Ozone platform" in the "Driver information" section of the page
Actual Results:  
The value of "Ozone platform" is X11 when XDG_SESSION_TYPE is wayland

Expected Results:  
The value of "Ozone platform" is wayland when XDG_SESSION_TYPE is wayland

Comment 1 Than Ngo 2023-07-14 10:37:21 UTC

It was intended not to set the Wayland-Ozone platform by default when using a Wayland session. The reason is that  the video hardware decoder no longer works with such setting.