You are not logged in.

Pages: 1

#1 2024-04-14 20:57:58

ewaller
Administrator
From: Pasadena, CA
Registered: 2009-07-13
Posts: 19,804

Chromium odd behavior with Preferred Ozone Platform Flag

Did an update yesterday and Chrome launched with a blank screen, except when the cursor moved over it and you get a trail of blinking cursors.  This may or may not be related to the other ongoing Chomium threads.  This system is an Intel Iris Xe platform as opposed to the other threads seeming to be Nvidia specific.

Played around disabling all flags and it now runs, but runs in xWayland.  I would prefer that it run native.  I traced the problem down to the 'Preferred Ozone platform' flag being set to Auto.   Setting it to Default causes Chromium to run under xWayland, as does setting it to X11.   Setting it to Wayland (or Auto) causes things to go pear shapped.

The odd part, running 

chromium --ozone-platform=wayland

works just fine.  Chromium runs in Native Wayland without xWayland

Anyone else seeing anything like this?

Nothing is too wonderful to be true, if it be consistent with the laws of nature -- Michael Faraday
Sometimes it is the people no one can imagine anything of who do the things no one can imagine. -- Alan Turing
---
How to Ask Questions the Smart Way

Online

#2 2024-04-15 01:32:12

jokerpoker
Member
Registered: 2024-04-06
Posts: 1

Re: Chromium odd behavior with Preferred Ozone Platform Flag

I have the same problem,  this work

Offline

#3 2024-04-15 05:10:36

duhdugg
Member
Registered: 2022-04-21
Posts: 5

Re: Chromium odd behavior with Preferred Ozone Platform Flag

same problem here with 

--ozone-platform-hint=auto

and 

--ozone-platform-hint=wayland

I found this chromium bug: https://issues.chromium.org/issues/329678163

although mine seems to work with the same as OP: 

--ozone-platform=wayland

Offline

#4 2024-04-15 05:57:42

byron3000
Member
Registered: 2014-02-06
Posts: 2

Re: Chromium odd behavior with Preferred Ozone Platform Flag

Same here, the command:

chromium --ozone-platform=wayland

fixes it, but I have in the chrome://flags/

Preferred Ozone platform set to Wayland that have to be the same behavior and it not work.

Do you know which flag we have to set to fix this issue?

Offline

Pages: 1

Board footer

Powered by FluxBB