Your message dated Mon, 21 Nov 2022 16:24:37 +0100
with message-id <7841e023-71f1-40e7-d465-59e25529d...@elfii.nl>
and subject line Re: Bug#1006457: Chromium fails to start on aarch64 systems
has caused the Debian Bug report #1006457,
regarding Chromium fails to start on aarch64 systems
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 ow...@bugs.debian.org
immediately.)
--
1006457: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1006457
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: chromium
Version: 98.0.4758.102-1~deb11u1
Latest Chromium on Debian Bullseye fails to start on aarch64/arm64
systems. Different ones with different kernels were tested, though all
Linux 5.10 variants, using (and generally supporting) modesetting DDX.
Only v98 from security repo is affected, v90 from "regular" Bullseye
repo starts fine.
-------
[2380:2380:0220/184034.039483:ERROR:gpu_process_host.cc(978)] GPU
process exited unexpectedly: exit_code=6
*** stack smashing detected ***: terminated
*** stack smashing detected ***: terminated
[2380:2380:0220/184034.122230:ERROR:gpu_process_host.cc(978)] GPU
process exited unexpectedly: exit_code=6
*** stack smashing detected ***: terminated
*** stack smashing detected ***: terminated
*** stack smashing detected ***: terminated
[2380:2380:0220/184034.167681:ERROR:gpu_process_host.cc(978)] GPU
process exited unexpectedly: exit_code=6
*** stack smashing detected ***: terminated
*** stack smashing detected ***: terminated
[2380:2380:0220/184034.198424:ERROR:system_web_app_manager.cc(320)]
Exceeded SWA install retry attempts. Skipping installation, will retry
on next OS update or when locale changes.
[2380:2380:0220/184034.200305:ERROR:gpu_process_host.cc(978)] GPU
process exited unexpectedly: exit_code=6
*** stack smashing detected ***: terminated
*** stack smashing detected ***: terminated
*** stack smashing detected ***: terminated
[2380:2380:0220/184034.225990:ERROR:gpu_process_host.cc(978)] GPU
process exited unexpectedly: exit_code=6
*** stack smashing detected ***: terminated
*** stack smashing detected ***: terminated
[2380:2380:0220/184034.240862:ERROR:gpu_process_host.cc(978)] GPU
process exited unexpectedly: exit_code=6
[2380:2380:0220/184034.240968:FATAL:gpu_data_manager_impl_private.cc(448)]
GPU process isn't usable. Goodbye.
-------
The X server itself works well, any other X application starts fine, X
server logs show no errors, but a regular exit like when you exit the X
client. It's hence definitely Chromium itself which fails. We tried all
kind of GPU related flags, like "--disable-gpu", changing renderer,
disabling GPU rasterization and all such, any combination or skipping
all of them, even the ones shipped by default with the package
(/etc/chromium.d) makes no difference. Starting with xinit (as root),
startx or from desktop doesn't make a difference either.
Best regards,
Micha
--- End Message ---
--- Begin Message ---
Version: 104.0.5112.79-1~deb11u1
On Sun, 31 Jul 2022 13:49:44 -0400 Andres Salomon <dilin...@queued.net>
wrote:
> The builds are almost identical, except for the compiler (clang 11) and
> build environment used. Clang 13 has been backported to stable (it's
> currently in stable-proposed-updates, and should be in the bullseye
> 11.5 release).
>
> The next chromium upload should be built against clang-13, which may
> behave better for you.
>
This has indeed fixed the problem, thanks!
--- End Message ---
