Ubuntu
linux-meta-nvidia-5.19 package

  1. Bug #2017980
  2. Comment #7

Comment 7 for bug 2017980

Revision history for this message
Chris (mail-christianmayer) wrote (last edit ): Re: Chrome crashes with FATAL:credentials.cc(127)] Check failed: . : Permission denied (13)

Running Kubuntu 22.04 (lsb_release -a: Ubuntu 22.04.2 LTS) yesterday I was asked to update these packages (packagekit role='update-packages'):
Install: linux-objects-nvidia-510-5.19.0-1010-nvidia-lowlatency:amd64 (5.19.0-1010.10, automatic),
 linux-signatures-nvidia-5.19.0-1010-nvidia-lowlatency:amd64 (5.19.0-1010.10, automatic),
 linux-image-5.19.0-1010-nvidia-lowlatency:amd64 (5.19.0-1010.10, automatic),
 linux-modules-5.19.0-1010-nvidia-lowlatency:amd64 (5.19.0-1010.10, automatic),
 linux-modules-nvidia-510-5.19.0-1010-nvidia-lowlatency:amd64 (5.19.0-1010.10, automatic),
 linux-modules-nvidia-510-nvidia-lowlatency-edge:amd64 (5.19.0-1010.10, automatic)
Upgrade: libmm-glib0:amd64 (1.20.0-1~ubuntu22.04.1, 1.20.0-1~ubuntu22.04.2),
modemmanager:amd64 (1.20.0-1~ubuntu22.04.1, 1.20.0-1~ubuntu22.04.2)

Then I shut down the machine for the night. And starting it today chrome doesn't start up with the same error message as above:

$ google-chrome
[11173:11173:0701/102011.173050:FATAL:credentials.cc(127)] Check failed: . : Keine Berechtigung (13)
Trace/Breakpoint ausgelöst (Speicherabzug geschrieben)

(Translated in English: Permission denied - core dumped)

=> So I'm also affected by that issue since this last package update

Adding "--no-sandbox" also makes chrome run again