Since it's not entirely obvious, and really just an artifact of running chrome, it would be nice if the readme would indicate that x11 libs must be present else chrome will not run.
I only found this out by enabling stdout/stderr when chrome is spawned which showed
error while loading shared libraries: libX11-xcb.so.1: cannot open shared object file: No such file or directory
Additionally, after fixing this, the following other libs are missing
libXcomposite.so.1
,
libXdamage.so.1
,
libXi.so.6
,
libXtst.so.6
,
libXcursor.so.1
,
libXss.so.1
,
libXrandr.so.2
,
libatk-1.0.so.0
,
libatk-bridge-2.0.so.0
,
libgtk-3-0
, and
libnss3.so
are also required.
File "/usr/local/lib/python3.8/dist-packages/pyppeteer/launcher.py", line 307, in launch
return await Launcher(options, **kwargs).launch()
File "/usr/local/lib/python3.8/dist-packages/pyppeteer/launcher.py", line 168, in launch
self.browserWSEndpoint = get_ws_endpoint(self.url)
File "/usr/local/lib/python3.8/dist-packages/pyppeteer/launcher.py", line 227, in get_ws_endpoint
raise BrowserError('Browser closed unexpectedly:\n')
pyppeteer.errors.BrowserError: Browser closed unexpectedly:
On debian, one must install the libx11-xcb1, libxcursor1, libxdamage1, libxi6, libxtst6, libxcomposite1, libxss1,libxrandr2, libatk1.0-0, libatk-bridge2.0-0, libgtk-3.so.0, libgtk-3-0, and libnss3 packages. I was running in a container which typically doesn't typically have x11 libs present.
Or at least it's here in an issue that can be found later on.
Cheers
