On Wed, Sep 13, 2023 at 06:55:40AM +1000, David wrote: [...]
> Similar situation to mine, although specifics vary. > The situation here is with Chromium on a SID laptop, while Chromium on > a Stable desktop is just fine. > Starting from a terminal gives: > > Gtk-Message: 06:46:36.954: Failed to load module "appmenu-gtk-module" > libva error: /usr/lib/x86_64-linux-gnu/dri/iHD_drv_video.so init failed > [12968:12968:0913/064637.144984:ERROR:chrome_browser_cloud_management_c > ontroller.cc(163)] Cloud management controller initialization aborted > as CBCM is not enabled. > [12968:12999:0913/064637.896873:ERROR:nss_util.cc(357)] After loading > Root Certs, loaded==false: NSS error code: -8018 > [0913/064638.283625:ERROR:elf_dynamic_array_reader.h(64)] tag not found > [13049:1:0100/000000.316639:ERROR:broker_posix.cc(41)] Recvmsg error: > Connection reset by peer (104) > Segmentation fault > > It just looked like something that needed the developers to wake up in > the morning, so I've left it for now. > I do get a flash of Chromium on the screen before it dies, so it's > classic seg fault. It just looks like the latest development phase > hasn't been married up too well with the context. This seems to be a bit different: in my case, some four Chromium processes stay around, hogging some RAM (a couple of 100MB) and a tiny bit of CPU. No flashes, no segfaults. Cheers -- t
signature.asc
Description: PGP signature
