You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Error: Failed to launch the browser process! 1922:1922:0122/170019.535775:FATAL:zygote_host_impl_linux.cc(128) No usable sandbox! If you are running on Ubuntu 23.10+ or another Linux distro that has disabled unprivileged user namespaces with AppArmor, see https://chromium.googlesource.com/chromium/src/+/main/docs/security/apparmor-userns-restrictions.md. Otherwise see https://chromium.googlesource.com/chromium/src/+/main/docs/linux/suid_sandbox_development.md for more information on developing with the (older) SUID sandbox. If you want to live dangerously and need an immediate workaround, you can try using --no-sandbox. 0122/170019.543272:ERROR:file_io_posix.cc(145) open /sys/devices/system/cpu/cpu0/cpufreq/scaling_cur_freq: No such file or directory (2) 0122/170019.543322:ERROR:file_io_posix.cc(145) open /sys/devices/system/cpu/cpu0/cpufreq/scaling_max_freq: No such file or directory (2)
at ChildProcess.onClose (file:///home/runner/work/serv00-auto-scripts/serv00-auto-scripts/node_modules/@puppeteer/browsers/lib/esm/launch.js:303:24)
at ChildProcess.emit (node:events:530:35)
at ChildProcess._handle.onexit (node:internal/child_process:293:12)
Node.js v20.18.1
##errorProcess completed with exit code 1.
The text was updated successfully, but these errors were encountered:
Error: Failed to launch the browser process!
1922:1922:0122/170019.535775:FATAL:zygote_host_impl_linux.cc(128) No usable sandbox! If you are running on Ubuntu 23.10+ or another Linux distro that has disabled unprivileged user namespaces with AppArmor, see https://chromium.googlesource.com/chromium/src/+/main/docs/security/apparmor-userns-restrictions.md. Otherwise see https://chromium.googlesource.com/chromium/src/+/main/docs/linux/suid_sandbox_development.md for more information on developing with the (older) SUID sandbox. If you want to live dangerously and need an immediate workaround, you can try using --no-sandbox.
0122/170019.543272:ERROR:file_io_posix.cc(145) open /sys/devices/system/cpu/cpu0/cpufreq/scaling_cur_freq: No such file or directory (2)
0122/170019.543322:ERROR:file_io_posix.cc(145) open /sys/devices/system/cpu/cpu0/cpufreq/scaling_max_freq: No such file or directory (2)
TROUBLESHOOTING: https://pptr.dev/troubleshooting
Node.js v20.18.1
##errorProcess completed with exit code 1.
The text was updated successfully, but these errors were encountered: