Puppeteer Chromium launch failure on Raspberry Pi

See original GitHub issue

got a big fat juicy error while trying to get this to run on a Raspberry pi. May of been too ambitious, but would like advice if you got it.

[11:35:53 PM] info :: ℹ selected stores: amazon, asus, bestbuy, evga, gamestop, microcenter, newegg, nvidia, nvidia-api, officedepot
[11:35:53 PM] info :: ℹ selected brands: asus, evga, msi, nvidia
[11:35:53 PM] info :: ℹ selected series: 3090
(node:21151) UnhandledPromiseRejectionWarning: Error: Failed to launch the browser process!
/home/pi/nvidia-snatcher/node_modules/puppeteer/.local-chromium/linux-800071/chrome-linux/chrome: 26: /home/pi/nvidia-snatcher/node_modules/puppeteer/.local-chromium/linux-800071/chrome-linux/chrome: Syntax error: Unterminated quoted string


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

    at onClose (/home/pi/nvidia-snatcher/node_modules/puppeteer/lib/cjs/puppeteer/node/BrowserRunner.js:193:20)
    at Interface.<anonymous> (/home/pi/nvidia-snatcher/node_modules/puppeteer/lib/cjs/puppeteer/node/BrowserRunner.js:183:68)
    at Interface.emit (events.js:326:22)
    at Interface.close (readline.js:424:8)
    at Socket.onend (readline.js:202:10)
    at Socket.emit (events.js:326:22)
    at endReadableNT (_stream_readable.js:1252:12)
    at processTicksAndRejections (internal/process/task_queues.js:80:21)
(Use `node --trace-warnings ...` to show where the warning was created)
(node:21151) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). To terminate the node process on unhandled promise rejection, use the CLI flag `--unhandled-rejections=strict` (see https://nodejs.org/api/cli.html#cli_unhandled_rejections_mode). (rejection id: 1)
(node:21151) [DEP0018] DeprecationWarning: Unhandled promise rejections are deprecated. In the future, promise rejections that are not handled will terminate the Node.js process with a non-zero exit code

Issue Analytics

  • State:closed
  • Created 3 years ago
  • Comments:9 (4 by maintainers)

github_iconTop GitHub Comments

4reactions
Rusnacommented, Oct 5, 2020

after the following, nvidia-snatcher is running on my Raspberry Pi 3B on Raspbian OS 32bit (desktop edition). I hope this helps other fellows:

Prerequisities: $ curl -sL https://deb.nodesource.com/setup_14.x | sudo -E bash - $ sudo apt update $ sudo apt upgrade $ sudo apt install git nodejs

Install as per instructions on github.

Configure following before typing npm run start to start: $ which chromium $ which chromium-browser /usr/bin/chromium-browser <-- USE THE ONE FOUND IN NEXT COMMAND $ export PUPPETEER_EXECUTABLE_PATH='/usr/bin/chromium-browser' $ export PUPPETEER_SKIP_CHROMIUM_DOWNLOAD=1 $ npm run start

3reactions
undauntcommented, Oct 5, 2020

@Rusna run a ‘which chromium’ to see where it’s located on your system, (and if there is even a result. try both chromium and chromium-browser). Whatever gives you a result, then run EXPORT… (that thing)

Eg: I had to run PUPPETEER_EXECUTABLE_PATH=‘/usr/bin/chromium-browser’ on one system and PUPPETEER_EXECUTABLE_PATH=‘chromium’ on another.

Read more comments on GitHub >

github_iconTop Results From Across the Web

Is raspberry pi 3 b+ compatible? Failed to launch. · Issue #4249
Try using your chromium-browser, rather than Puppeteer's chrome which might not work on the PI's ARM architecture. const browser = await ...
Read more >
Puppeteer on Raspbian NodeJS - Sami C.
You would get the following error trying to run: Error: Failed to launch chrome! /home/xxxx/.../node_modules/puppeteer/.local-chromium/liniux- ...
Read more >
Impossible to launch Puppeteer on Raspberry - General
I have an issue when I try to launch puppeteer with my Raspberry using node-red. I am using the node-red-contrib-puppeteer-new library and this...
Read more >
Impossible to launch Puppeteer with node-red on Raspberry
1 Answer 1 · sudo apt install chromium-browser chromium-codecs-ffmpeg · copy chromium-browser from /usr/bin/ to /.nodered/node_modules/puppeteer/.
Read more >
Problem starting Chromium headless from Node script on ...
js from starup of the Pi! I use Puppeteer to start Chromium, and everything in my server.js works except starting the browser through...
Read more >

github_iconTop Related Medium Post

No results found

github_iconTop Related StackOverflow Question

No results found

github_iconTroubleshoot Live Code

Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free

github_iconTop Related Reddit Thread

No results found

github_iconTop Related Hackernoon Post

No results found

github_iconTop Related Tweet

No results found

github_iconTop Related Dev.to Post

No results found

github_iconTop Related Hashnode Post

No results found