Bug#1062533: chromium: Chromium doesn't launch in ARM64!
There is something update: I was enabling "chrome://flags/#enable-unsafe-webgpu" flag, and it was working fine with all the previous versions, now I have tried disabled it, and the chromium works now. I don't understand why when it enabled prevents chromium from running/launching. Thank you On Fri, 2024-02-02 at 04:17 -0500, Andres Salomon wrote: > Running 'grep chromium /var/log/dpkg.log' (or /var/log/dpkg.log.1 if > it > was already rotated) should tell you what version it was upgraded > from. > > On 2/1/24 15:43, Sally A.haj wrote: > > I don't remember exactly, but I believe it was the very recent > > before > > the latest, because I usually do update the system every week or > > so. > > > > Thank you. > > On Thu, 2024-02-01 at 15:36 -0500, Andres Salomon wrote: > > > > > > > > > On 2/1/24 15:23, Sally A.haj wrote: > > > [...] > > > > > > > > * What outcome did you expect instead? > > > > Before the latest update, it was working just fine. > > > > I am using Gnome/Wayland on Raspberry Pi 4 for a quite some > > > > times, > > > > and this the first time I face an issue with chromium. > > > > > > > > > > Thanks for the report. What exactly was the previous version that > > > worked > > > for you? > >
Bug#1062533: chromium: Chromium doesn't launch in ARM64!
Yes Andres, I run the command you mentioned, and this is the previous version: 121.0.6167.85-1~deb12u1. Thank you. On Fri, 2024-02-02 at 04:17 -0500, Andres Salomon wrote: > Running 'grep chromium /var/log/dpkg.log' (or /var/log/dpkg.log.1 if > it > was already rotated) should tell you what version it was upgraded > from. > > On 2/1/24 15:43, Sally A.haj wrote: > > I don't remember exactly, but I believe it was the very recent > > before > > the latest, because I usually do update the system every week or > > so. > > > > Thank you. > > On Thu, 2024-02-01 at 15:36 -0500, Andres Salomon wrote: > > > > > > > > > On 2/1/24 15:23, Sally A.haj wrote: > > > [...] > > > > > > > > * What outcome did you expect instead? > > > > Before the latest update, it was working just fine. > > > > I am using Gnome/Wayland on Raspberry Pi 4 for a quite some > > > > times, > > > > and this the first time I face an issue with chromium. > > > > > > > > > > Thanks for the report. What exactly was the previous version that > > > worked > > > for you? > >
Bug#1062533: chromium: Chromium doesn't launch in ARM64!
Running 'grep chromium /var/log/dpkg.log' (or /var/log/dpkg.log.1 if it was already rotated) should tell you what version it was upgraded from. On 2/1/24 15:43, Sally A.haj wrote: I don't remember exactly, but I believe it was the very recent before the latest, because I usually do update the system every week or so. Thank you. On Thu, 2024-02-01 at 15:36 -0500, Andres Salomon wrote: On 2/1/24 15:23, Sally A.haj wrote: [...] * What outcome did you expect instead? Before the latest update, it was working just fine. I am using Gnome/Wayland on Raspberry Pi 4 for a quite some times, and this the first time I face an issue with chromium. Thanks for the report. What exactly was the previous version that worked for you? OpenPGP_0x645D0247C36E7637.asc Description: OpenPGP public key OpenPGP_signature.asc Description: OpenPGP digital signature
Bug#1062533: chromium: Chromium doesn't launch in ARM64!
On 2/1/24 15:23, Sally A.haj wrote: [...] * What outcome did you expect instead? Before the latest update, it was working just fine. I am using Gnome/Wayland on Raspberry Pi 4 for a quite some times, and this the first time I face an issue with chromium. Thanks for the report. What exactly was the previous version that worked for you? OpenPGP_0x645D0247C36E7637.asc Description: OpenPGP public key OpenPGP_signature.asc Description: OpenPGP digital signature
Bug#1062533: chromium: Chromium doesn't launch in ARM64!
I don't remember exactly, but I believe it was the very recent before the latest, because I usually do update the system every week or so. Thank you. On Thu, 2024-02-01 at 15:36 -0500, Andres Salomon wrote: > > > On 2/1/24 15:23, Sally A.haj wrote: > [...] > > > > * What outcome did you expect instead? > > Before the latest update, it was working just fine. > > I am using Gnome/Wayland on Raspberry Pi 4 for a quite some times, > > and this the first time I face an issue with chromium. > > > > Thanks for the report. What exactly was the previous version that > worked > for you?
Bug#1062533: chromium: Chromium doesn't launch in ARM64!
Package: chromium Version: 121.0.6167.139-1~deb12u1 Severity: normal Tags: upstream X-Debbugs-Cc: sallya...@yahoo.com, t...@security.debian.org Dear Maintainer, *** Reporter, please consider answering these questions, where appropriate *** * What led up to the situation? I just updated the system normally, then reboot the system, then tried to run chromium, but it doens't run at all. * What was the outcome of this action? When I run chromium from the terminal, I get this out put: chromium [4905:4905:0201/151723.065989:ERROR:policy_logger.cc(156)] :components/enterprise/browser/controller/chrome_browser_cloud_management_controller.cc(161) Cloud management controller initialization aborted as CBCM is not enabled. Please use the `--enable-chrome-browser-cloud-management` command line flag to enable it if you are not using the official Google Chrome build. [0201/151723.154339:ERROR:elf_dynamic_array_reader.h(64)] tag not found [0201/151723.163572:WARNING:exception_snapshot_linux.cc(263)] fpsimd not found [4905:4935:0201/151723.102253:ERROR:check.cc(297)] Check failed: false. NOTREACHED log messages are omitted in official builds. Sorry! [4905:4905:0201/151723.260722:ERROR:check.cc(297)] Check failed: false. NOTREACHED log messages are omitted in official builds. Sorry! [4905:4905:0201/151723.334295:ERROR:message_formatter.cc(93)] MessageFormat({0,number,percent}) failed with U_MISSING_RESOURCE_ERROR [0201/151723.359887:ERROR:elf_dynamic_array_reader.h(64)] tag not found Segmentation fault sally@sally-deb:~$ [4950:4950:0100/00.997428:ERROR:gbm_wrapper.cc(75)] Failed to get fd for plane.: No such file or directory (2) [4950:4950:0100/00.997701:ERROR:gbm_wrapper.cc(258)] Failed to export buffer to dma_buf: No such file or directory (2) [4950:4950:0100/00.998357:ERROR:gbm_wrapper.cc(75)] Failed to get fd for plane.: No such file or directory (2) [4950:4950:0100/00.998481:ERROR:gbm_wrapper.cc(258)] Failed to export buffer to dma_buf: No such file or directory (2) [4950:4950:0100/00.999079:ERROR:gbm_wrapper.cc(75)] Failed to get fd for plane.: No such file or directory (2) [4950:4950:0100/00.999196:ERROR:gbm_wrapper.cc(258)] Failed to export buffer to dma_buf: No such file or directory (2) [4950:4950:0100/00.999782:ERROR:gbm_wrapper.cc(75)] Failed to get fd for plane.: No such file or directory (2) [4950:4950:0100/00.999894:ERROR:gbm_wrapper.cc(258)] Failed to export buffer to dma_buf: No such file or directory (2) * What outcome did you expect instead? Before the latest update, it was working just fine. I am using Gnome/Wayland on Raspberry Pi 4 for a quite some times, and this the first time I face an issue with chromium. -- System Information: Debian Release: 12.4 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'stable-security'), (500, 'stable') Architecture: arm64 (aarch64) Kernel: Linux 6.5.0-0.deb12.4-arm64 (SMP w/4 CPU threads) Kernel taint flags: TAINT_CRAP Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled