Somebody has reported the issue to the Chromium project:
https://urldefense.proofpoint.com/v2/url?u=https-3A__bugs.chromium.org_p_chromium_issues_detail-3Fid-3D1261617&d=DwIGaQ&c=gRgGjJ3BkIsb5y6s49QqsA&r=gd8BzeSQcySVxr0gDWSEbN-P-pgDXkdyCtaMqdCgPPdW1cyL5RIpaIYrCn8C5x2A&m=jMp6t8Rxbp2JjDBwHInruaIXYHTXHs01gK0rGSv28qhrDaBTlxvZf__y9cfdNxBf&s=5apCcSZDXA4zQHBZ6C02tCjXHvSgLU4BpYIY8YaT5r4&e=
The University of St Andrews is a charity registered in Scotland, No: SC013532
On 23/10/2021, 17:11, "Mailing list for Scientific Linux users worldwide on
behalf of Götz Waschk" <scientific-linux-us...@listserv.fnal.gov on behalf of
goetz.was...@desy.de> wrote:
I have seen this. The solution was rpm -e google-chrome-stable . You
could try to run Google Chrome in an EL8 singularity container, e.g.
based on CentOS8, AlmaLinux8 or Rocky Linux 8.
