Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

cli Error: Failed to launch the browser process! (libxshmfence.so.1: cannot open shared object file: No such file or directory)

See original GitHub issue

Describe the bug Since last update, I got the error described below. As I got this error at a new Project, I also try to only re-run an deployment-script, which works perfectly fine 3 Day’s ago. So I’m sure the issue depends on something that was changed in the last release.

As there seems only this line to be changed: https://github.com/onderceylan/pwa-asset-generator/commit/bc655fdec9427fec2deeea9a29408d9d2048ba13, the question is, how can I archive the opposite of this command with a cli-parameter for npx-command?!

To Reproduce Steps to reproduce the behavior:

Execute cli command npx pwa-asset-generator -n ./public/assets/images/logo.svg ./public/assets/appIcons/ --path-override /assets/appIcons -m ./public/manifest.json -i ./public/assets/appIcons/index.html --padding "10px"
Result ins:

1:39:25 PM installer Chromium is not found in module folder, gonna have to download r848005 for you once 🤔
1:39:32 PM installer Chromium downloaded to /builds/onepager1/xxx.de/yarn_cache/node_modules/puppeteer-core/.local-chromium/linux-848005
1:39:34 PM cli Error: Failed to launch the browser process!
/builds/onepager1/xxx.de/yarn_cache/node_modules/puppeteer-core/.local-chromium/linux-848005/chrome-linux/chrome: error while loading shared libraries: libxshmfence.so.1: cannot open shared object file: No such file or directory

System (please complete the following information):

OS: Linux Debian 10.0 (BUSTER) [docker-image: node:latest]

Additional context I’ve run the deployment-script on gitlab 3 Day’s ago, and everything worked like expected. Today, I re-run the same deployment to check the npx-command again with a as working known version, and its broken with the above error-message.

If I do run the npx command with forcing 4.1.1, it works again:

npx pwa-asset-generator@4.1.1 -n ./public/assets/images/logo.svg ./public/assets/appIcons/ --path-override /assets/appIcons -m ./public/manifest.json -i ./public/assets/appIcons/index.html --padding "10px"

Issue Analytics

State:
Created 2 years ago
Comments:10

Top GitHub Comments

1reaction

xstablecommented, Jul 14, 2021

I’ll give it a try. But anyway, I think it’s important for you to notice this somewhere in your documentations, so that other people know this “known Issues” and can handle them. I’ll come back to report, how I solved it, so you could add this to your docs if you want.

1reaction

xstablecommented, Jul 13, 2021

I do use a docker-image with debian 10 (Buster)

Top Results From Across the Web

Failed to launch chrome #807 - puppeteer/puppeteer - GitHub

chrome: error while loading shared libraries: libXcursor.so.1: cannot open shared object file: No such file or directory.

Can't Use Puppeteer -- Error: Failed to launch chrome

If you encounter E: Unable to locate package errors, run sudo apt-get update . Share.

Internal browser error: Failed to launch the browser process!

Internal browser error: Failed to launch the browser process! ... libnss3.so: cannot open shared object file: No such file or directory.

How To Solve "cannot open shared object file" Error in Ubuntu ...

The full error generally looks like this: error while loading shared libraries: cannot open shared object file: No such file or directory.

puppeteer on Chrome! - Google Groups

(node:19830) UnhandledPromiseRejectionWarning: Error: Failed to launch chrome! ... libX11.so.6: cannot open shared object file: No such file or directory.