Update from https://bugs.chromium.org/p/chromium/issues/detail?id=1459821 as it's not public visible:
``` @Reporter, Thanks for filing the Issue. Please find the magic signature & stack trace for the crash id# 8e7f32382b1ddc1c Magic signature : [Assert] sandbox::`anonymous namespace'::CheckCloneNewUserErrno Stack Trace Thread 0 chrome (id: 0x00010cf6)crashedMAGIC SIGNATURE THREADcontent_copy 0x0000560a0003ddb3(chrome -immediate_crash.h:146)??logging::LogMessage::~LogMessage() 0x0000560a022d31f7(chrome -logging.cc:1107)??logging::ErrnoLogMessage::~ErrnoLogMessage() 0x0000560a0619dcdd(chrome -logging.cc:1101)logging::ErrnoLogMessage::~ErrnoLogMessage() 0x0000560a01a7f08d(chrome -check.cc:198)??logging::CheckError::~CheckError() 0x0000560a0735454a(chrome -credentials.cc:126)sandbox::(anonymous namespace)::CheckCloneNewUserErrno(int) 0x0000560a01f159fc(chrome -credentials.cc:280)sandbox::Credentials::CanCreateProcessInNewUserNS() 0x0000560a01f156ff(chrome -zygote_host_impl_linux.cc:114)content::ZygoteHostImpl::Init(base::CommandLine const&) 0x0000560a01f0efc4(chrome -content_main_runner_impl.cc:382)content::(anonymous namespace)::InitializeZygoteSandboxForBrowserProcess(base::CommandLine const&) 0x0000560a01f0efc4(chrome -content_main_runner_impl.cc:1033)content::ContentMainRunnerImpl::Initialize(content::ContentMainParams) 0x0000560a0204a6bd(chrome -content_main.cc:301)content::RunContentProcess(content::ContentMainParams, content::ContentMainRunner*) 0x0000560a0204a6bd(chrome -content_main.cc:343)content::ContentMain(content::ContentMainParams) 0x0000560a020487ff(chrome -chrome_main.cc:187)ChromeMain 0x00007f29a5029d8f(libc.so.6 + 0x00029d8f) 0x00007f29a5f4c03f(ld-linux-x86-64.so.2 + 0x0003a03f) 0x00007f29a5029e3f(libc.so.6 + 0x00029e3f) 0x0000560a033991c9(chrome + 0x0000000005c281c9)_start 0x00007ffc8a640b07 As per crash ID (8e7f32382b1ddc1c) adding Internals>Core [...] ``` -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-meta-nvidia-5.19 in Ubuntu. https://bugs.launchpad.net/bugs/2017980 Title: FATAL:credentials.cc(127)] Check failed: . : Permission denied (13) Status in linux-meta-nvidia-5.19 package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-510 package in Ubuntu: Confirmed Status in ubuntu-drivers-common package in Ubuntu: Confirmed Bug description: With this kernel linux-image-nvidia-5.19 (version 5.19.0.1009.10) I experience that google-chrome crashes. It shows ```shell [11849:11849:0428/091628.955956:FATAL:credentials.cc(127)] Check failed: . : Permission denied (13) Trace/breakpoint trap (core dumped)". ``` To be honest I don't think it has anything to do with google-chrome at all. When google-chrome starts it (normally) request the system key-manager (KWallet in my case) for access to the users keys before it actually shows anything from chrome. Not even that part (the KWallet password box) shows up. I can only reproduce this problem with this specific kernel. It should be possible to take google-chrome out of the equation by using another application that starts by request the desktop key manager for access. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-nvidia-5.19 (not installed) ProcVersionSignature: Ubuntu 5.15.0-1023.23-nvidia 5.15.92 Uname: Linux 5.15.0-1023-nvidia x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82.4 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: KDE Date: Fri Apr 28 11:23:23 2023 InstallationDate: Installed on 2016-01-08 (2666 days ago) InstallationMedia: Kubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) SourcePackage: linux-meta-nvidia-5.19 UpgradeStatus: Upgraded to jammy on 2022-07-21 (281 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-meta-nvidia-5.19/+bug/2017980/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
