[Bug 1944468] Re: Electron applications all crash upon launch

[Michael Hudson-Doyle]

I think you have things a bit backwards there. You are using a Docker
image that has clone3 enabled in its libc and the container runtime in
the environment the github action is running in is the thing that is not
supporting the clone3 syscall. Whether the glibc in Ubuntu 21.10 issues
the clone3 syscall or not is entirely irrelevant to this.

What is relevant to your issue is where docker get their container
runtime from. I've looked this up in the past but I can't remember the
details now. I don't think it's the version that's in the Ubuntu 20.04
archives though (the update will the needed fix is in proposed now and
will hopefully migrate to updates soon, which will help a lot of people
facing this issue -- but not afaict github actions). Basically you need
to watch https://github.com/actions/virtual-environments/issues/3812 I
think.

** Bug watch added: github.com/actions/virtual-environments/issues #3812
   https://github.com/actions/virtual-environments/issues/3812

-- 
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to glibc in Ubuntu.
https://bugs.launchpad.net/bugs/1944468

Title:
  Electron applications all crash upon launch

Status in glibc package in Ubuntu:
  Fix Released
Status in glibc source package in Impish:
  Fix Released

Bug description:
  Just a few weeks ago, I noticed the .deb version of Visual Studio Code
  crashing upon launch. I also noticed Element (matrix client) also
  would crash. The only thing these applications have in common is
  electron. I was hoping this would get noticed by someone and that the
  issue would be figured out, but I guess that person had to be me.

  Erroneously-filed bug 1943568 exhibits the same issues. Experimenting
  with Visual Studio Code provided this:

  [347381:0921/133026.728654:ERROR:proxy_config_service_linux.cc(608)] inotify_init failed: Too many open files (24)
  [347419:0921/133026.764752:ERROR:file_path_watcher_linux.cc(326)] inotify_init() failed: Too many open files (24)
  [main 2021-09-21T20:30:26.930Z] update#setState idle
  [347381:0921/133027.009472:ERROR:gpu_process_host.cc(1007)] GPU process exited unexpectedly: exit_code=159
  [347381:0921/133027.323205:ERROR:gpu_process_host.cc(1007)] GPU process exited unexpectedly: exit_code=159
  [347381:0921/133027.690827:ERROR:gpu_process_host.cc(1007)] GPU process exited unexpectedly: exit_code=159
  [347490:0921/133027.728195:ERROR:gpu_init.cc(440)] Passthrough is not supported, GL is swiftshader
  [347381:0921/133027.879310:ERROR:gpu_process_host.cc(1007)] GPU process exited unexpectedly: exit_code=159
  [347495:0921/133027.894439:ERROR:gpu_init.cc(440)] Passthrough is not supported, GL is swiftshader
  [347381:0921/133028.049455:ERROR:gpu_process_host.cc(1007)] GPU process exited unexpectedly: exit_code=159
  [347499:0921/133028.063977:ERROR:gpu_init.cc(440)] Passthrough is not supported, GL is swiftshader
  [347381:0921/133028.216114:ERROR:gpu_process_host.cc(1007)] GPU process exited unexpectedly: exit_code=159
  [347511:0921/133028.222585:ERROR:gpu_init.cc(440)] Passthrough is not supported, GL is disabled
  [347381:0921/133028.384052:ERROR:gpu_process_host.cc(1007)] GPU process exited unexpectedly: exit_code=159
  [347515:0921/133028.442903:ERROR:gpu_init.cc(440)] Passthrough is not supported, GL is disabled
  [347381:0921/133028.596590:ERROR:gpu_process_host.cc(1007)] GPU process exited unexpectedly: exit_code=159
  [347519:0921/133028.602088:ERROR:gpu_init.cc(440)] Passthrough is not supported, GL is disabled
  [347381:0921/133028.749373:ERROR:gpu_process_host.cc(1007)] GPU process exited unexpectedly: exit_code=159
  [347381:0921/133028.749401:FATAL:gpu_data_manager_impl_private.cc(415)] GPU process isn't usable. Goodbye.
  Server response: 
  Server response: 
  Illegal instruction (core dumped)

  
  Atom provided this:

  [347834:0921/133121.907198:FATAL:gpu_data_manager_impl_private.cc(439)]
  GPU process isn't usable. Goodbye.

  Unexpected crash report id length
  Failed to get crash dump id.
  Report Id: 

  Unexpected crash report id length
  Failed to get crash dump id.
  Report Id: 
  Illegal instruction (core dumped)

  
  When either application was provided "--no-sandbox" at the command line, they would run normally. However, Element does not pass that via command line, so I was unable to use the workaround for that.

  Upon investigating the runtime dependencies for Element, Atom, and
  VSCode, the one thing they had in common was libgtk-3-0, and the date
  of 2021-09-03 for publishing coincides with the time in which these
  errors started to appear.

  Another workaround, other than the "--no-sandbox" usage, is to use the
  snap version of the apps if available, or flatpak. These provide their
  own versions of these dependencies, which tells me these .deb-based
  applications are affected by libgtk-3-0.

  Granted, those applications are not in the Ubuntu repository, however,
  many people (including myself) rely on those to function correctly. It
  would be very bad if Electron apps failed to function when 21.10 is
  released.

  ProblemType: Bug
  DistroRelease: Ubuntu 21.10
  Package: libgtk-3-0 3.24.30-1ubuntu1
  ProcVersionSignature: Ubuntu 5.13.0-16.16-lowlatency 5.13.13
  Uname: Linux 5.13.0-16-lowlatency x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu69
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: KDE
  Date: Tue Sep 21 13:25:17 2021
  InstallationDate: Installed on 2021-03-20 (184 days ago)
  InstallationMedia: Ubuntu-Studio 21.04 "Hirsute Hippo" - Alpha amd64 (20210320)
  SourcePackage: gtk+3.0
  UpgradeStatus: Upgraded to impish on 2021-06-13 (100 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/glibc/+bug/1944468/+subscriptions