#1075982 chromium: please set ozone default to "auto"

Package:
chromium
Source:
chromium
Description:
web browser
Submitter:
Daniel Kahn Gillmor
Date:
2025-04-21 17:00:02 UTC
Severity:
normal
#1075982#5
Date:
2024-07-08 21:08:47 UTC
From:
To:
https://chromium.googlesource.com/chromium/src/+/HEAD/docs/ozone_overview.md
says:


It looks like it's possible to change the default from X11 to Auto by
setting the following build parameter:

    ozone_platform="auto"

It seems reasonable to me for debian's chromium to do this, as it means
that chromium will Just Work™ on systems without XWayland.
#1075982#10
Date:
2024-09-29 03:12:36 UTC
From:
To:
 >> I typically use set --ozone-platform-hint=auto, or set it explicitly
 >> in chrome://flags/#ozone-platform-hint (See
 >> https://bugs.debian,org/1075982, where i explain why i think this
 >> should be the default).

This upstream bug (just like
https://issues.chromium.org/issues/329678163 before it) is exactly why I
haven't enabled wayland by default. Upstream just doesn't seem to care
about fixing wayland bugs in a timely fashion yet.

If wayland users have to manually switch chromium from using xwayland to
wayland, then hopefully they'll know how to switch it back when upstream
inevitably breaks the wayland backend.

I really hope this upstream situation changes soon.

Thanks for this! I can include the patch in the next 129 upload
(probably uploaded on Wednesday). Since I'm not currently using wayland,
I'd appreciate if you could test it out once I do so, and tell me if it
resolves the issue completely or not.
#1075982#15
Date:
2024-10-02 01:14:58 UTC
From:
To:
Hi!

Great! I'll gladly test and report back, at the moment this hits sid.

Thanks,
Guillem
#1075982#20
Date:
2024-10-03 01:35:26 UTC
From:
To:
ugh, i understand your reluctance here.

Yes, many thanks to Guillem for identifying this, and to Andres for
considering it.  I'll do what i can to test it as soon as it's available
in the archive.

Regards,
#1075982#25
Date:
2024-10-04 04:06:42 UTC
From:
To:
Hi!

Just restarted with the new chromium version just uploaded, w/o the
--disable-gpu-memory-buffer-video-frames option, played a video, and
it no longer show those log messages! So, it looks confirmed. :)

Thanks,
Guillem
#1075982#30
Date:
2024-10-04 13:56:41 UTC
From:
To:
I can confirm the same results on my end.  Thank you very much for
sorting this out!  stderr is much happier ☺
#1075982#35
Date:
2025-04-21 16:57:14 UTC
From:
To:
On Sat, 28 Sep 2024 23:12:36 -0400 Andres Salomon <dilinger@queued.net> wrote:
After trixie releases, I'd like to try defaulting the ozone backend to
'auto' in sid and seeing how it goes.