chrome Check failed

Bug #2025537 reported by Viacheslav G
16
This bug affects 2 people
Affects Status Importance Assigned to Milestone
chromium-browser (Ubuntu)
Incomplete
Undecided
Unassigned

Bug Description

local_slava@worksystem:~$ google-chrome
[19394:19394:0701/201749.072306:FATAL:credentials.cc(127)] Check failed: . : Отказано в доступе (13)
Trace/breakpoint trap (core dumped)

How fix this? After update ubuntu...

Revision history for this message
Olivier Robert (novhak) wrote :

Were you using the generic kernel stack ? If yes, check your kernel release number (uname -r) to confirm it’s still the generic kernel (should end with “-generic”).

If your kernel stack suddenly changed, you’re not alone. People have reported the updates going fancy and installing unwanted kernel stacks. I hope this won’t get unnoticed by Canonical for too long, as it could have severe availability consequences for some people.

Revision history for this message
Chris Guiver (guiverc) wrote :

Thank you for taking the time to report this bug and helping to make Ubuntu better.

Bug reporting is about finding & fixing problems thus preventing future users from hitting the same bug.

I suspect a Support site would be more appropriate, eg. https://answers.launchpad.net/ubuntu. You can also find help with your problem in the support forum of your local Ubuntu community http://loco.ubuntu.com/ or asking at https://askubuntu.com or https://ubuntuforums.org, or for more support options please look at https://discourse.ubuntu.com/t/community-support/709

Google chrome is a Google product, and not a Ubuntu package. Bug reports on google products are not managed on Launchpad (a Ubuntu bug tracker). Refer https://support.google.com/chrome/answer/95315

FYI: This bug report can be converted into a question, which is geared at support.

Changed in chromium-browser (Ubuntu):
status: New → Incomplete
Revision history for this message
Viacheslav G (slboss222) wrote :

@novhak

5.19.0-1010-nvidia-lowlatency

Revision history for this message
Olivier Robert (novhak) wrote :

@slboss222 OK, so this is a confirmed kernel stack change.

While this is likely a bug, it’s probably not a Chromium bug, but rater related to the ubuntu-drivers-common package. Can you post the output of “LC_ALL=C apt list --installed 'linux-*'” (without the “”) ?

This will help confirm the origin of the bug, as well as determine the steps to solve the problem.

The possible cause is the Ubuntu third-party driver logic choosing an Nvidia driver for another kernel stack, which then triggers installation of those kernels, to satisfy dependencies.

The solution would be to uninstall those non-generic kernels and associated drivers (provided there’s at least one generic kernel installed) and then rebooting.

It’s also possible that the Nvidia driver version is too old, and that may be what triggered the bug. Running “ubuntu-drivers install” should bring it up to date.

Revision history for this message
Matheus Henrique (estmatheush) wrote :

@novhak

Here is the output of "LC_ALL=C apt list --installed 'linux-*'”

Listing... Done
linux-base/jammy,jammy,now 4.5ubuntu9 all [installed,automatic]
linux-firmware/jammy-updates,jammy-updates,jammy-security,jammy-security,now 20220329.git681281e4-0ubuntu3.14 all [installed,automatic]
linux-generic-hwe-22.04/jammy-updates,jammy-security,now 5.19.0.46.47~22.04.21 amd64 [installed]
linux-headers-5.19.0-46-generic/jammy-updates,jammy-security,now 5.19.0-46.47~22.04.1 amd64 [installed,automatic]
linux-headers-generic-hwe-22.04/jammy-updates,jammy-security,now 5.19.0.46.47~22.04.21 amd64 [installed,automatic]
linux-hwe-5.19-headers-5.19.0-46/jammy-updates,jammy-updates,jammy-security,jammy-security,now 5.19.0-46.47~22.04.1 all [installed,automatic]
linux-image-5.19.0-1010-nvidia-lowlatency/jammy-updates,jammy-security,now 5.19.0-1010.10 amd64 [installed,automatic]
linux-image-5.19.0-46-generic/jammy-updates,jammy-security,now 5.19.0-46.47~22.04.1 amd64 [installed,automatic]
linux-image-generic-hwe-22.04/jammy-updates,jammy-security,now 5.19.0.46.47~22.04.21 amd64 [installed,automatic]
linux-libc-dev/jammy-updates,jammy-security,now 5.15.0-76.83 amd64 [installed,automatic]
linux-modules-5.19.0-1010-nvidia-lowlatency/jammy-updates,jammy-security,now 5.19.0-1010.10 amd64 [installed,automatic]
linux-modules-5.19.0-46-generic/jammy-updates,jammy-security,now 5.19.0-46.47~22.04.1 amd64 [installed,automatic]
linux-modules-extra-5.19.0-46-generic/jammy-updates,jammy-security,now 5.19.0-46.47~22.04.1 amd64 [installed,automatic]
linux-modules-nvidia-510-5.19.0-1010-nvidia-lowlatency/jammy-updates,jammy-security,now 5.19.0-1010.10 amd64 [installed,automatic]
linux-modules-nvidia-510-generic-hwe-22.04/jammy-updates,jammy-security,now 5.19.0-46.47~22.04.1+5 amd64 [installed]
linux-modules-nvidia-510-nvidia-lowlatency-edge/jammy-updates,jammy-security,now 5.19.0-1010.10 amd64 [installed,auto-removable]
linux-modules-nvidia-525-5.19.0-46-generic/jammy-updates,jammy-security,now 5.19.0-46.47~22.04.1+5 amd64 [installed,automatic]
linux-modules-nvidia-525-generic-hwe-22.04/jammy-updates,jammy-security,now 5.19.0-46.47~22.04.1+5 amd64 [installed,automatic]
linux-objects-nvidia-510-5.19.0-1010-nvidia-lowlatency/jammy-updates,jammy-security,now 5.19.0-1010.10 amd64 [installed,automatic]
linux-objects-nvidia-525-5.19.0-46-generic/jammy-updates,jammy-security,now 5.19.0-46.47~22.04.1+5 amd64 [installed,automatic]
linux-signatures-nvidia-5.19.0-1010-nvidia-lowlatency/jammy-updates,jammy-security,now 5.19.0-1010.10 amd64 [installed,automatic]
linux-signatures-nvidia-5.19.0-46-generic/jammy-updates,jammy-security,now 5.19.0-46.47~22.04.1+5 amd64 [installed,automatic]
linux-sound-base/jammy,jammy,now 1.0.25+dfsg-0ubuntu7 all [installed,automatic]

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.