Your message dated Tue, 29 Aug 2023 15:28:26 -0400
with message-id <[email protected]>
and subject line Re: Bug#1016438: chromium: Ozone wayland platfrom broken on
aarch64 build after 97.0.4692.99-1
has caused the Debian Bug report #1016438,
regarding chromium: Ozone wayland platfrom broken on aarch64 build after
97.0.4692.99-1
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)
--
1016438: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1016438
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: chromium
Version: 98.0.4758.80-1
Severity: important
X-Debbugs-Cc: [email protected]
Dear Maintainer,
the aarch64 build of version 97.0.4692.99-1 can be successfully run with
--ozone-platform-hint=wayland and hardware acceleration works in this setting.
Unfortunately, from 98.0.4758.80-1 onwards all the way to the latest available
103.0.5060.134-1, --ozone-platform-hint=wayland is broken and chromium fails to
start (no window appears) when running --ozone-platform-hint=wayland.
Could there be a regression in the build configuration between version 97 and
98?
Attempting to start the chromium 98 and 103 builds with Ozone Wayland Platform
prints errors like
[40197:40197:0730/170137.393978:ERROR:gpu_init.cc(486)] Passthrough is not
supported, GL is egl, ANGLE is
[40197:40197:0730/170137.679681:ERROR:gbm_wrapper.cc(292)] Failed to export
buffer to dma_buf: No such file or directory (2)
[40197:40197:0730/170137.681056:ERROR:gbm_pixmap_wayland.cc(75)] Cannot
create bo with format= RGBA_8888 and usage=SCANOUT
[40197:40197:0730/170137.681871:ERROR:gpu_memory_buffer_factory_native_pixmap.cc(198)]
Failed to create pixmap 1536x1280, RGBA_8888, usage SCANOUT
[40197:40197:0730/170137.682767:ERROR:gbm_wrapper.cc(292)] Failed to export
buffer to dma_buf: No such file or directory (2)
[40197:40197:0730/170137.683567:ERROR:gbm_pixmap_wayland.cc(75)] Cannot
create bo with format= RGBA_8888 and usage=GPU_READ
[40197:40197:0730/170137.684044:ERROR:gpu_memory_buffer_factory_native_pixmap.cc(198)]
Failed to create pixmap 1536x1280, RGBA_8888, usage GPU_READ
[40197:40197:0730/170137.684419:ERROR:shared_image_backing_factory_gl_image.cc(355)]
CreateSharedImage: Failed to create bindable image
[40197:40197:0730/170137.684715:ERROR:shared_image_factory.cc(770)]
CreateSharedImage: could not create backing.
[40197:40197:0730/170137.685672:ERROR:shared_context_state.cc(543)] Failed to
make current since context is marked as lost
[40197:40197:0730/170137.686140:ERROR:skia_output_surface_impl_on_gpu.cc(1703)]
Failed to make current.
[40197:40197:0730/170137.687022:ERROR:shared_context_state.cc(543)] Failed to
make current since context is marked as lost
[40197:40197:0730/170137.687478:ERROR:skia_output_surface_impl_on_gpu.cc(1703)]
Failed to make current.
[40197:40197:0730/170137.688920:ERROR:shared_context_state.cc(543)] Failed to
make current since context is marked as lost
[40197:40197:0730/170137.689612:ERROR:skia_output_surface_impl_on_gpu.cc(1703)]
Failed to make current.
[40197:40197:0730/170137.690294:ERROR:shared_context_state.cc(543)] Failed to
make current since context is marked as lost
[40197:40197:0730/170137.690672:ERROR:skia_output_surface_impl_on_gpu.cc(1703)]
Failed to make current.
[40197:40197:0730/170137.691283:ERROR:raster_decoder.cc(1244)]
RasterDecoderImpl: Context lost during MakeCurrent.
[40197:40197:0730/170137.701335:ERROR:shared_image_stub.cc(519)]
SharedImageStub: context already lost
[40197:40197:0730/170137.705387:ERROR:shared_image_stub.cc(519)]
SharedImageStub: context already lost
[40143:40236:0730/170137.709873:ERROR:nss_util.cc(349)] After loading Root
Certs, loaded==false: NSS error code: -8018
[40197:40197:0730/170137.781652:ERROR:gbm_wrapper.cc(292)] Failed to export
buffer to dma_buf: No such file or directory (2)
Whereas with chromium 97 with Ozone Wayland Platform
[44179:44179:0730/174942.364802:ERROR:gpu_init.cc(457)] Passthrough is not
supported, GL is egl, ANGLE is
[44179:44179:0730/174942.374620:ERROR:sandbox_linux.cc(378)]
InitializeSandbox() called with multiple threads in process gpu-process.
While --ozone-platform-hint=x11 works for these newer builds, it is not an
acceptable alternative as only software rendering without hardware acceleration
is functional on those builds. Specifically, with Ozone Wayland Platform,
chrome://gpu lists "GL_VENDOR: freedreno" "GL_RENDERER: FD618", which indicates
working hardware acceleration, whereas the Ozone X11 Platform lists
"GL_RENDERER ANGLE (freedreno, FD618, OpenGL 3.3 (Core Profile) Mesa 22.1.3)"
and "GL_VERSION OpenGL ES 2.0.0 (ANGLE 2.1.0 git hash: unknown hash)"
indicating the lack of hardware acceleration due to the use of ANGLE.
Below system information is generated while running the last functional build,
97.0.4692.99-1.
-- System Information:
Debian Release: bookworm/sid
APT prefers testing
APT policy: (500, 'testing'), (1, 'unstable')
Architecture: arm64 (aarch64)
Kernel: Linux 5.19.0-rc8-stb-cbq (SMP w/8 CPU threads; PREEMPT)
Locale: LANG=C.UTF-8, LC_CTYPE=C.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
Versions of packages chromium depends on:
ii chromium-common 97.0.4692.99-1
ii libasound2 1.2.6.1-2+b1
ii libatk-bridge2.0-0 2.38.0-4
ii libatk1.0-0 2.38.0-1
ii libatomic1 12.1.0-2
ii libatspi2.0-0 2.44.1-1
ii libc6 2.33-7
ii libcairo2 1.16.0-5
ii libcups2 2.4.2-1
ii libdbus-1-3 1.14.0-1
ii libdrm2 2.4.110-1
ii libevent-2.1-7 2.1.12-stable-5+b1
ii libexpat1 2.4.8-1
ii libflac8 1.3.4-2
ii libfontconfig1 2.13.1-4.4
ii libfreetype6 2.12.1+dfsg-3
ii libgbm1 22.0.5-1
ii libgcc-s1 12.1.0-2
ii libglib2.0-0 2.72.2-2
ii libharfbuzz0b 2.7.4-1+b1
ii libicu67 67.1-7
ii libjpeg62-turbo 1:2.1.2-1
ii libjsoncpp25 1.9.5-4
ii liblcms2-2 2.12~rc1-2
ii libminizip1 1.1-8+b1
ii libnspr4 2:4.34-1
ii libnss3 2:3.79-1
ii libopenjp2-7 2.5.0-1
ii libopus0 1.3.1-2
ii libpango-1.0-0 1.50.7+ds-1
ii libpng16-16 1.6.37-5
ii libpulse0 15.0+dfsg1-4+b1
ii libre2-9 20220601+dfsg-1
ii libsnappy1v5 1.1.9-2
ii libstdc++6 12.1.0-2
ii libwebp6 0.6.1-2.1
ii libwebpdemux2 1.2.2-2+b1
ii libwebpmux3 1.2.2-2+b1
ii libx11-6 2:1.7.5-1
ii libxcb1 1.14-3
ii libxcomposite1 1:0.4.5-1
ii libxdamage1 1:1.1.5-2
ii libxext6 2:1.3.4-1
ii libxfixes3 1:6.0.0-1
ii libxkbcommon0 1.4.0-1
ii libxml2 2.9.14+dfsg-1
ii libxrandr2 2:1.5.2-2+b1
ii libxslt1.1 1.1.34-4
ii zlib1g 1:1.2.11.dfsg-4
Versions of packages chromium recommends:
ii chromium-sandbox 97.0.4692.99-1
Versions of packages chromium suggests:
pn chromium-driver <none>
pn chromium-l10n <none>
pn chromium-shell <none>
Versions of packages chromium-common depends on:
ii libc6 2.33-7
ii libstdc++6 12.1.0-2
ii libx11-6 2:1.7.5-1
ii libxext6 2:1.3.4-1
ii x11-utils 7.7+5
ii xdg-utils 1.1.3-4.1
ii zlib1g 1:1.2.11.dfsg-4
Versions of packages chromium-common recommends:
ii chromium-sandbox 97.0.4692.99-1
pn fonts-liberation <none>
ii gnome-shell [notification-daemon] 42.2-1
ii libgl1-mesa-dri 22.0.5-1
pn libu2f-udev <none>
ii notification-daemon 3.20.0-4+b1
pn system-config-printer <none>
ii upower 0.99.19-1
Versions of packages chromium-sandbox depends on:
ii libc6 2.33-7
-- no debconf information
--- End Message ---
--- Begin Message ---
Great, thanks for letting me know. Closing.
On Tue, Aug 29 2023 at 09:40:13 AM -04:00:00, Leonard Lausen
<[email protected]> wrote:
Thank you for fixing the arm64 issues. I can confirm Ozone wayland
platform works well on arm64 since a few releases.
On 3/19/23 21:03, Andres Salomon wrote:
At the time this bug was filed, arm64 had various other issues. But
they're all cleaned up now, and I'm wondering if this bug is still
an issue for you with chromium 111.
Also, --ozone-platform=wayland is what I use these days.
--- End Message ---
