I tried to launch it with --no-sandbox, and we have this return :

#/usr/bin/google-chrome-stable --no-sandbox

[69134:69156:0704/101329.358591:ERROR:bus.cc(399)] Failed to connect to the 
bus: Could not parse server address: Unknown address type (examples of valid 
types are "tcp" and on UNIX "unix")
[69134:69156:0704/101329.359203:ERROR:bus.cc(399)] Failed to connect to the 
bus: Could not parse server address: Unknown address type (examples of valid 
types are "tcp" and on UNIX "unix")
Authorization required, but no authorization protocol specified
Authorization required, but no authorization protocol specified
Authorization required, but no authorization protocol specified
Authorization required, but no authorization protocol specified
[69134:69156:0704/101329.453872:ERROR:bus.cc(399)] Failed to connect to the 
bus: Could not parse server address: Unknown address type (examples of valid 
types are "tcp" and on UNIX "unix")
[69134:69156:0704/101329.453898:ERROR:bus.cc(399)] Failed to connect to the 
bus: Could not parse server address: Unknown address type (examples of valid 
types are "tcp" and on UNIX "unix")
[69134:69156:0704/101329.518587:ERROR:bus.cc(399)] Failed to connect to the 
bus: Could not parse server address: Unknown address type (examples of valid 
types are "tcp" and on UNIX "unix")
[69134:69156:0704/101329.518613:ERROR:bus.cc(399)] Failed to connect to the 
bus: Could not parse server address: Unknown address type (examples of valid 
types are "tcp" and on UNIX "unix")
Authorization required, but no authorization protocol specified
[69170:69170:0704/101329.556446:ERROR:angle_platform_impl.cc(43)] 
Display.cpp:1014 (initialize): ANGLE Display::initialize error 12289: Could not 
open the default X display.
ERR: Display.cpp:1014 (initialize): ANGLE Display::initialize error 12289: 
Could not open the default X display.
[69170:69170:0704/101329.557215:ERROR:gl_display.cc(504)] EGL Driver message 
(Critical) eglInitialize: Could not open the default X display.
[69170:69170:0704/101329.557593:ERROR:gl_display.cc(917)] eglInitialize OpenGL 
failed with error EGL_NOT_INITIALIZED, trying next display type
Authorization required, but no authorization protocol specified
[69170:69170:0704/101329.559419:ERROR:angle_platform_impl.cc(43)] 
Display.cpp:1014 (initialize): ANGLE Display::initialize error 12289: Could not 
open the default X display.
ERR: Display.cpp:1014 (initialize): ANGLE Display::initialize error 12289: 
Could not open the default X display.
[69170:69170:0704/101329.559602:ERROR:gl_display.cc(504)] EGL Driver message 
(Critical) eglInitialize: Could not open the default X display.
[69170:69170:0704/101329.559707:ERROR:gl_display.cc(917)] eglInitialize 
OpenGLES failed with error EGL_NOT_INITIALIZED
[69170:69170:0704/101329.559807:ERROR:gl_ozone_egl.cc(23)] 
GLDisplayEGL::Initialize failed.
[69170:69170:0704/101329.562896:ERROR:viz_main_impl.cc(186)] Exiting GPU 
process due to errors during initialization

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to ubuntu-drivers-common 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/~desktop-packages
Post to     : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

Reply via email to