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

Failed to launch the browser process! - Debian Buster #213

Open
micha-net opened this issue Nov 7, 2021 · 2 comments · May be fixed by #216
Open

Failed to launch the browser process! - Debian Buster #213

micha-net opened this issue Nov 7, 2021 · 2 comments · May be fixed by #216

Comments

@micha-net
Copy link

I run the latest docker image (docker run -it -v ~/.aws:/root/.aws -t aal sportradar/aws-azure-login --mode=debug) and get the error message bellow since one week (worked before). Same with --mode=gui

I am not sure which details help, so here are the host kernel version and the docker version. Linux itself runs as a VM.
Linux kernel: 4.19.0-18-amd64
Docker version 20.10.10, build b485636

`Error: Failed to launch the browser process!
Fontconfig warning: "/etc/fonts/fonts.conf", line 100: unknown element "blank"
[16:16:1107/120831.707576:ERROR:browser_main_loop.cc(1425)] Unable to open X display.
[1107/120831.711154:ERROR:nacl_helper_linux.cc(307)] NaCl helper process running without a sandbox!
Most likely you need to configure your SUID sandbox correctly

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

at onClose (/aws-azure-login/node_modules/puppeteer/lib/cjs/puppeteer/node/BrowserRunner.js:194:20)
at ChildProcess.<anonymous> (/aws-azure-login/node_modules/puppeteer/lib/cjs/puppeteer/node/BrowserRunner.js:185:79)
at ChildProcess.emit (events.js:387:35)
at ChildProcess.emit (domain.js:470:12)
at Process.ChildProcess._handle.onexit (internal/child_process.js:277:12)

`

@5n00p4eg
Copy link

5n00p4eg commented Nov 8, 2021

I have the same issue on Fedora 34

@micha-net
Copy link
Author

This issue is related to this one: #210

After changing my default MFA method to the app it worked again for me.
The browser crash should not happen anyway though imho. For several of my colleagues the browser did not crash.

@jordiprats jordiprats linked a pull request Jan 5, 2022 that will close this issue
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

Successfully merging a pull request may close this issue.

2 participants