Bug 2190179 - Chromium doesn't launch as a native wayland apps when in wayland session
Summary: Chromium doesn't launch as a native wayland apps when in wayland session
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Fedora
Classification: Fedora
Component: chromium
Version: 38
Hardware: x86_64
OS: Linux
unspecified
medium
Target Milestone: ---
Assignee: Tom "spot" Callaway
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2023-04-27 12:42 UTC by Chanon Somwang
Modified: 2023-07-14 10:37 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2023-07-14 10:37:21 UTC
Type: ---
Embargoed:

Attachments (Terms of Use)

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.
Note You need to log in before you can comment on or make changes to this bug.