I think it is related to this issue, but also could be related to my corporate proxy. I can't tell you why because I don't remember. Should give you a more detailed output from puppeteer, instead of the generic error. It is also worth adding dumpio: true to your options to debug. Setsebool -P unconfirmed_chrome_sandbox_transition 0 If Arch Linux uses SELinux, you may also have to run this: Pango libXcomposite libXcursor libXdamage libXext libXi libXtst cups-libs libXScrnSaver libXrandr GConf2 alsa-lib atk gtk3 ipa-gothic-fonts xorg-x11-fonts-100dpi xorg-x11-fonts-75dpi xorg-x11-utils xorg-x11-fonts-cyrillic xorg-x11-fonts-Type1 xorg-x11-fonts-misc liberation-mono-fonts liberation-narrow-fonts liberation-narrow-fonts liberation-sans-fonts liberation-serif-fonts glib2 Some are duplicates from your question, but I don't think they all are: I also don't know what the Arch Linux equivalents are. I had to install all of these libraries manually. Puppeteer is a Node library which provides a high-level API to control Chrome or Chromium over the DevTools Protocol. puppeteer has no bugs, it has no vulnerabilities, it has a Permissive License and it has medium support. This is straight from my docs, but I had to hand-jam the contents because my docs are on an intranet. puppeteer is a TypeScript library typically used in Automation, Nodejs applications. I had to do the following to get puppeteer working. I should also mention this is for RHEL EC2 instances behind a corporate proxy (not Arch Linux), but I still feel like it may help. There's too much for me to put this in a comment, so I will summarize here.
0 Comments
Leave a Reply. |