Error: Failed to launch Chrome

[RidaAyed]

Hi.

Same problem as in #37 . Remains after full update:
4.16.13-1-ARCH

$ mmdc -i flowchart.mmd -o output.svg

(node:23812) UnhandledPromiseRejectionWarning: Error: Failed to launch chrome!
[0604/132833.412465:FATAL:zygote_host_impl_linux.cc(126)] 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 0x560ba482482c base::debug::StackTrace::StackTrace()
#1 0x560ba47ab290 logging::LogMessage::~LogMessage()
#2 0x560ba37a15d1 content::ZygoteHostImpl::Init()
#3 0x560ba44dad91 content::ContentMainRunnerImpl::Initialize()
#4 0x560ba44e4c12 service_manager::Main()
#5 0x560ba44d9184 content::ContentMain()
#6 0x560ba86b1a39 headless::(anonymous namespace)::RunContentMain()
#7 0x560ba86b1ac2 headless::HeadlessBrowserMain()
#8 0x560ba44e1f8f headless::HeadlessShellMain()
#9 0x560ba2a5a1ac ChromeMain
#10 0x7f9a18c3e06b __libc_start_main
#11 0x560ba2a5a02a _start

Received signal 6
#0 0x560ba482482c base::debug::StackTrace::StackTrace()
#1 0x560ba4824391 base::debug::(anonymous namespace)::StackDumpSignalHandler()
#2 0x7f9a1ec16a80 <unknown>
#3 0x7f9a18c5186b __GI_raise
#4 0x7f9a18c3c40e __GI_abort
#5 0x560ba48231e5 base::debug::BreakDebugger()
#6 0x560ba47ab6da logging::LogMessage::~LogMessage()
#7 0x560ba37a15d1 content::ZygoteHostImpl::Init()
#8 0x560ba44dad91 content::ContentMainRunnerImpl::Initialize()
#9 0x560ba44e4c12 service_manager::Main()
#10 0x560ba44d9184 content::ContentMain()
#11 0x560ba86b1a39 headless::(anonymous namespace)::RunContentMain()
#12 0x560ba86b1ac2 headless::HeadlessBrowserMain()
#13 0x560ba44e1f8f headless::HeadlessShellMain()
#14 0x560ba2a5a1ac ChromeMain
#15 0x7f9a18c3e06b __libc_start_main
#16 0x560ba2a5a02a _start
  r8: 0000000000000000  r9: 00007ffcf45df0d0 r10: 0000000000000008 r11: 0000000000000246
 r12: 00007ffcf45df7d8 r13: 0000000000000161 r14: 00007ffcf45df7e0 r15: 00007ffcf45df379
  di: 0000000000000002  si: 00007ffcf45df0d0  bp: 00007ffcf45df320  bx: 0000000000000006
  dx: 0000000000000000  ax: 0000000000000000  cx: 00007f9a18c5186b  sp: 00007ffcf45df0d0
  ip: 00007f9a18c5186b 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.

[maritz]

Same thing in 4.17.0-1-MANJARO.

How up-to-date am I supposed to be? :-D

[enra64]

For anyone else that stumbles on this (like me) instead of reading the documentation, see https://github.com/mermaidjs/mermaid.cli#options, where this problem is described as well as the workaround.

On arch, the kernel option to enable this feature is not enabled by default, which is why an up-to-date kernel won't help. (https://github.com/Antergos/antergos-packages/issues/164)

[aloisklink]

Development has moved to the https://github.com/mermaid-js/mermaid-cli repo, please re-open your issue there if it's still relevant. The package has also been renamed on NPM to @mermaid-js/mermaid-cli, so you may need to run npm uninstall mermaid.cli && npm install @mermaid-js/mermaid-cli to get the latest version of this package.