Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

I failed to launch chrome in WSL #160

Open
Satone7 opened this issue Nov 8, 2019 · 1 comment
Open

I failed to launch chrome in WSL #160

Satone7 opened this issue Nov 8, 2019 · 1 comment
Milestone

Comments

@Satone7
Copy link

Satone7 commented Nov 8, 2019

My system is windows10 subsystem for Ubuntu 18.04, and I use Remote-WSL in vscode to work in Ubuntu 18.04.

I tried this way but " /home/satone/.vscode: No such file or directory "

please help me

satone@DESKTOP-HP164JC:~$ chromium-browser 
Failed to move to new namespace: PID namespaces supported, Network namespace supported, but failed: errno = Permission denied
Trace/breakpoint trap (core dumped)
satone@DESKTOP-HP164JC:~$ sudo chromium-browser 
[1338:1338:1108/163640.913428:ERROR:zygote_host_impl_linux.cc(89)] Running as root without --no-sandbox is not supported. See https://crbug.com/638180.
satone@DESKTOP-HP164JC:~$ chromium-browser --no-sandbox

(chromium-browser:1345): Gtk-WARNING **: 16:36:49.646: cannot open display: 

Error: Failed to launch chrome!
[1108/163419.520955:FATAL:zygote_host_impl_linux.cc(116)] 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 0x7f547596b879
#1 0x7f54758c8c63
#2 0x7f54758dd013
#3 0x7f547707795e
#4 0x7f547550cadc
#5 0x7f547555872c
#6 0x7f547550b0b1
#7 0x7f547555799d
#8 0x7f547555770b
#9 0x7f54732e81b8
#10 0x7f5469e41b97
#11 0x7f54732e802a

Received signal 6
#0 0x7f547596b879
#1 0x7f54758c8c63
#2 0x7f547596b401
#3 0x7f54701e2890
#4 0x7f5469e5ee97
#5 0x7f5469e60801
#6 0x7f547596a265
#7 0x7f54758dd461
#8 0x7f547707795e
#9 0x7f547550cadc
#10 0x7f547555872c
#11 0x7f547550b0b1
#12 0x7f547555799d
#13 0x7f547555770b
#14 0x7f54732e81b8
#15 0x7f5469e41b97
#16 0x7f54732e802a
r8: 0000000000000000 r9: 00007fffdefc4fd0 r10: 0000000000000008 r11: 0000000000000008
r12: 00007fffdefc6298 r13: 00007fffdefc5278 r14: 00007fffdefc5278 r15: 00007fffdefc5290
di: 0000000000000002 si: 00007fffdefc4fd0 bp: 00007fffdefc5220 bx: 00007f546a20c840
dx: 0000000000000000 ax: 0000000000000000 cx: 0000000000000008 sp: 00007fffdefc4fd0
ip: 00007f5469e5ee97 efl: 0000000000000246 cgf: 00000053002b0033 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

@yzane yzane added this to the 1.4.3 milestone Mar 11, 2020
@yzane
Copy link
Owner

yzane commented Mar 11, 2020

Please upgrade Markdown PDF to ver1.4.3 and try.

tat3 pushed a commit to tat3/vscode-markdown-pdf-2 that referenced this issue Sep 4, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants