Error: Failed to lanuch chrome!

[chorulex]

I can not execute "Export(PDF)" on my vscode in Centos7.

error:
Error: Failed to launch chrome!
[0724/173226.582954:FATAL:zygote_host_impl_linux.cc(124)] No usable sandbox! Update your kernel or see https://chromium.googlesource.com/chromium/src/+/master/docs/linux_suid_sandbox_development.md for more information on developing with the SUID sandbox. If you want to live dangerously and need an immediate workaround, you can try using --no-sandbox.
#0 0x5568e32b1b0c base::debug::StackTrace::StackTrace()
#1 0x5568e32ca780 logging::LogMessage::~LogMessage()
#2 0x5568e235a2b1 content::ZygoteHostImpl::Init()
#3 0x5568e1fccc65 content::BrowserMainLoop::EarlyInitialization()
#4 0x5568e1fd2a69 content::BrowserMainRunnerImpl::Initialize()
#5 0x5568e70fc9a8 headless::HeadlessContentMainDelegate::RunProcess()
#6 0x5568e2feca00 content::RunNamedProcessTypeMain()
#7 0x5568e2fed2e8 content::ContentMainRunnerImpl::Run()
#8 0x5568e2ff6f24 service_manager::Main()
#9 0x5568e2febf14 content::ContentMain()
#10 0x5568e70fb9b9 headless::(anonymous namespace)::RunContentMain()
#11 0x5568e70fba42 headless::HeadlessBrowserMain()
#12 0x5568e2ff3f9d headless::HeadlessShellMain()
#13 0x5568e16521ac ChromeMain
#14 0x7fba05a81445 __libc_start_main
#15 0x5568e165202a _start

Received signal 6
#0 0x5568e32b1b0c base::debug::StackTrace::StackTrace()
#1 0x5568e32b1671 base::debug::(anonymous namespace)::StackDumpSignalHandler()
#2 0x7fba0b9be6d0
#3 0x7fba05a95277 __GI_raise
#4 0x7fba05a96968 __GI_abort
#5 0x5568e32b0105 base::debug::BreakDebugger()
#6 0x5568e32cabca logging::LogMessage::~LogMessage()
#7 0x5568e235a2b1 content::ZygoteHostImpl::Init()
#8 0x5568e1fccc65 content::BrowserMainLoop::EarlyInitialization()
#9 0x5568e1fd2a69 content::BrowserMainRunnerImpl::Initialize()
#10 0x5568e70fc9a8 headless::HeadlessContentMainDelegate::RunProcess()
#11 0x5568e2feca00 content::RunNamedProcessTypeMain()
#12 0x5568e2fed2e8 content::ContentMainRunnerImpl::Run()
#13 0x5568e2ff6f24 service_manager::Main()
#14 0x5568e2febf14 content::ContentMain()
#15 0x5568e70fb9b9 headless::(anonymous namespace)::RunContentMain()
#16 0x5568e70fba42 headless::HeadlessBrowserMain()
#17 0x5568e2ff3f9d headless::HeadlessShellMain()
#18 0x5568e16521ac ChromeMain
#19 0x7fba05a81445 __libc_start_main
#20 0x5568e165202a _start
r8: 00007fba0bd93ac0 r9: 0000000000000002 r10: 0000000000000008 r11: 0000000000000202
r12: 00007ffea1624a58 r13: 0000000000000161 r14: 00007ffea1624a60 r15: 00007ffea16245f9
di: 0000000000003ea2 si: 0000000000003ea2 bp: 00007ffea16245a0 bx: 00007ffea1624610
dx: 0000000000000006 ax: 0000000000000000 cx: ffffffffffffffff sp: 00007ffea1624468
ip: 00007fba05a95277 efl: 0000000000000202 cgf: 0000000000000033 erf: 0000000000000000
trp: 0000000000000000 msk: 0000000000000000 cr2: 0000000000000000
[end of stack trace]
Calling _exit(1). Core file will not be generated.

[Infiltrator]

Same issue on Debian 9.5.

I have tried symlinking chrome to /opt/google/chrome/chrome-sandbox, but it does not make a difference.

Error: Failed to launch chrome!
[0806/160921.334036:FATAL:zygote_host_impl_linux.cc(124)] No usable sandbox! Update your kernel or see https://chromium.googlesource.com/chromium/src/+/master/docs/linux_suid_sandbox_development.md for more information on developing with the SUID sandbox. If you want to live dangerously and need an immediate workaround, you can try using --no-sandbox.
#0 0x5585e36b7b0c base::debug::StackTrace::StackTrace()
#1 0x5585e36d0780 logging::LogMessage::~LogMessage()
#2 0x5585e27602b1 content::ZygoteHostImpl::Init()
#3 0x5585e23d2c65 content::BrowserMainLoop::EarlyInitialization()
#4 0x5585e23d8a69 content::BrowserMainRunnerImpl::Initialize()
#5 0x5585e75029a8 headless::HeadlessContentMainDelegate::RunProcess()
#6 0x5585e33f2a00 content::RunNamedProcessTypeMain()
#7 0x5585e33f32e8 content::ContentMainRunnerImpl::Run()
#8 0x5585e33fcf24 service_manager::Main()
#9 0x5585e33f1f14 content::ContentMain()
#10 0x5585e75019b9 headless::(anonymous namespace)::RunContentMain()
#11 0x5585e7501a42 headless::HeadlessBrowserMain()
#12 0x5585e33f9f9d headless::HeadlessShellMain()
#13 0x5585e1a581ac ChromeMain
#14 0x7f0e68476b17 __libc_start_main
#15 0x5585e1a5802a _start

Received signal 6
#0 0x5585e36b7b0c base::debug::StackTrace::StackTrace()
#1 0x5585e36b7671 base::debug::(anonymous namespace)::StackDumpSignalHandler()
#2 0x7f0e6dc908e0 <unknown>
#3 0x7f0e68489f3b gsignal
#4 0x7f0e6848b2f1 abort
#5 0x5585e36b6105 base::debug::BreakDebugger()
#6 0x5585e36d0bca logging::LogMessage::~LogMessage()
#7 0x5585e27602b1 content::ZygoteHostImpl::Init()
#8 0x5585e23d2c65 content::BrowserMainLoop::EarlyInitialization()
#9 0x5585e23d8a69 content::BrowserMainRunnerImpl::Initialize()
#10 0x5585e75029a8 headless::HeadlessContentMainDelegate::RunProcess()
#11 0x5585e33f2a00 content::RunNamedProcessTypeMain()
#12 0x5585e33f32e8 content::ContentMainRunnerImpl::Run()
#13 0x5585e33fcf24 service_manager::Main()
#14 0x5585e33f1f14 content::ContentMain()
#15 0x5585e75019b9 headless::(anonymous namespace)::RunContentMain()
#16 0x5585e7501a42 headless::HeadlessBrowserMain()
#17 0x5585e33f9f9d headless::HeadlessShellMain()
#18 0x5585e1a581ac ChromeMain
#19 0x7f0e68476b17 __libc_start_main
#20 0x5585e1a5802a _start
  r8: 0000000000000000  r9: 00007fffe5602c50 r10: 0000000000000008 r11: 0000000000000246
 r12: 00007fffe5603358 r13: 0000000000000161 r14: 00007fffe5603360 r15: 00007fffe5602ef9
  di: 0000000000000002  si: 00007fffe5602c50  bp: 00007fffe5602ea0  bx: 0000000000000006
  dx: 0000000000000000  ax: 0000000000000000  cx: 00007f0e68489f3b  sp: 00007fffe5602c50
  ip: 00007f0e68489f3b efl: 0000000000000246 cgf: 002b000000000033 erf: 0000000000000000
 trp: 0000000000000000 msk: 0000000000000000 cr2: 0000000000000000
[end of stack trace]
Calling _exit(1). Core file will not be generated.


TROUBLESHOOTING: https://github.com/GoogleChrome/puppeteer/blob/master/docs/troubleshooting.md

[Infiltrator]

Setting vscode config "markdown-pdf.executablePath": "/opt/google/chrome/chrome-sandbox" yields:

Error: Failed to launch chrome!
The setuid sandbox provides API version 1, but you need 0
Please read https://chromium.googlesource.com/chromium/src/+/master/docs/linux_suid_sandbox_development.md.

close: Bad file descriptor


TROUBLESHOOTING: https://github.com/GoogleChrome/puppeteer/blob/master/docs/troubleshooting.md

Chrome is version 68.0.3440.84-1.

[Infiltrator]

To anybody else having this problem: setting vscode config "markdown-pdf.executablePath": "/opt/google/chrome/chrome" instead of chrome-sandbox fixes this issue.

[smahi]

@Infiltrator thank you so much.
It works for me, I am on Debian Buster.

[yzane]

Please upgrade Markdown PDF to ver1.4.3 and try.