Brave starts with Ozone platform X11 instead of Wayland even after specifying it to do so

[SmollClover]

Description

Steps to Reproduce

1. Install Brave version 1.65.122 Chromium: 124.0.6367.82 (Official Build) (64-bit) on Linux with Wayland as the compositor
2. Set flag #ozone-platform-hint to Auto or Wayland
3. Start Brave as normal

Actual result:

Brave will start with Ozone platform X11 regardless.

Expected result:

Brave should start with Ozone platform Wayland as was the case with previous versions.

Reproduces how often:

Very easy to reproduce when using the mentioned version on a Wayland system.

Brave version (brave://version info)

Brave		1.65.122 Chromium: 124.0.6367.82 (Official Build) (64-bit) 
Revision	64099bd820a06a2843326660372e895b7d78f20b
OS		Linux

Version/Channel Information:

• Can you reproduce this issue with the current release?
  • Yes
• Can you reproduce this issue with the beta channel?
  • Uncertain
• Can you reproduce this issue with the nightly channel?
  • Uncertain

Other Additional Information:

• Does the issue resolve itself when disabling Brave Shields?
  • No
• Does the issue resolve itself when disabling Brave Rewards?
  • No
• Is the issue reproducible on the latest version of Chrome?
  • No (tried Chromium 123.0.6312.86 (Official Build) Fedora Project (64-bit))

Miscellaneous Information:

Selection of the Ozone platform had worked prior to the fix from #37498

[rillian]

I can reproduce with 1.67.37 nightly (fedora 40 gnome-desktop). Passing --ozone-platform=wayland on the command line does result in brave://gpu reporting wayland, along with blurry scaling.

Follow-up to brave/brave-core#23166

[why-not-try-calmer]

I can reproduce on 1.65.122 Chromium: 124.0.6367.82(nixos-unstable).

I can also confirm that the workaround works, namely running brave --ozone-platform=wayland.

[sojusnik]

Still happens with Version 1.65.123 (Chromium: 124.0.6367.91).

[cyangalaxy]

I can reproduce with 1.67.37 nightly (fedora 40 gnome-desktop). Passing --ozone-platform=wayland on the command line does result in brave://gpu reporting wayland, along with blurry scaling.

Follow-up to brave/brave-core#23166

You can fix the blurryness with Ozone Wayland by also adding this flag: --disable-features=WaylandFractionalScaleV1

[qdrop17]

I can confirm the issue you mentioned. To launch Brave, I have to use the command brave-browser --ozone-platform=wayland > /dev/null 2>&1 & due to the problem reported in #37954. It would be great if Brave could start directly with Wayland when the flag is set, as this workaround is inconvenient. This issue might be related to some dependencies with the profile manager, although I'm not entirely sure.

Brave 1.65.123 Chromium: 124.0.6367.91 (Official Build) (64-bit)

[SmollClover]

As of 1.65.126 Chromium: 124.0.6367.118 (Official Build) (64-bit) the issue seems to be fixed?
Launching Brave with #ozone-platform-hint set to Auto while also providing no additional command-line argument has set the ozone platform correctly again to be Wayland.

If others can confirm that it's not just on my end and that the new stable version seems to be fixed, then I think this Issue is resolved.

[urbenlegend]

Can confirm that ozone-platform-hint works properly now.

[SmollClover]

Since the issue seems to be fixed, I'll close this Issue.