Error: spawn EACCES on ArchLinux

[adrfantini]

Using decktape from the ArchLinux AUR, I get this error when trying to convert anything:

Error: spawn EACCES
    at ChildProcess.spawn (internal/child_process.js:330:11)
    at Object.exports.spawn (child_process.js:500:9)
    at Function.launch (/usr/lib/node_modules/decktape/node_modules/puppeteer/lib/Launcher.js:100:40)
    at <anonymous>

With any command. Also trying some of the example presentations in https://github.com/astefanutti/decktape, no difference.

[pat-s]

At a first glance this seems like an issue of puppeteer: alekzonder/docker-puppeteer#9

I can replicate your issue but its strange as nothing has changed since the creation of the AUR package.

Can you replicate the problem when installing decktape using npm?

[adrfantini]

Yep, the problem is there even if using decktape from npm!

[astefanutti]

I've been able to reproduce (using the base/archlinux Docker image).

Unfortunately, there is not much that can be done on DeckTape side. This is a Puppeteer install step issue where the Chromium binary (/usr/lib/node_modules/decktape/node_modules/puppeteer/.local-chromium/) hasn't the needed permissions.

For some reasons, permissions for
/usr/lib/node_modules/decktape/node_modules/puppeteer/.local-chromium/linux-508693/chrome-linux/chrome is only -rwx------.

Running:

$ chmod a+r /usr/lib/node_modules/decktape/node_modules/puppeteer/.local-chromium/linux-508693/chrome-linux/*
$ chmod a+x /usr/lib/node_modules/decktape/node_modules/puppeteer/.local-chromium/linux-508693/chrome-linux/chrome

Fixes things. I would suggest to create an issue in Puppeteer to follow this up.

[adrfantini]

Done.

[pat-s]

Thanks guys. I could also manually fix it in the PGKBUILD but let's first see if there is a response from the puppeteer guys.

[astefanutti]

puppeteer/puppeteer#2283 has just been fixed. Let me upgrade to Puppeteer 1.3.0 to have this fixed in DeckTape.

[pat-s]

decktape v2.8.1. does not yet include the puppeteer fix right? Release notes say that you only upgraded to v1.1.1.

[astefanutti]

@pat-s right. I'm still holding the Puppeteer upgrade because of puppeteer/puppeteer#2411. If you could vote it up, that'd be great.

[astefanutti]

I've just released version 2.8.3 that contains upstream fix. Let me close this and do not hesitate to re-open if you still face the issue.

[adrfantini]

Thanks!

[JJK96]

I have this issue:

events.js:167
      throw er; // Unhandled 'error' event
      ^

Error: spawn /usr/lib/node_modules/decktape/node_modules/puppeteer/.local-chromium/linux-508693/chrome-linux/chrome EACCES
    at Process.ChildProcess._handle.onexit (internal/child_process.js:229:19)
    at onErrorNT (internal/child_process.js:406:16)
    at process._tickCallback (internal/process/next_tick.js:63:19)
Emitted 'error' event at:
    at Process.ChildProcess._handle.onexit (internal/child_process.js:235:12)
    at onErrorNT (internal/child_process.js:406:16)
    at process._tickCallback (internal/process/next_tick.js:63:19)

[astefanutti]

@JJK96 what version of DeckTape are you using and what on OS?

[JJK96]

The arch linux aur package nodejs-decktape, which is version 2.8.0-1.
However, by installing via npm I could get it to work, I did have to add the --no-sandbox flag though.

[astefanutti]

OK, the nodejs-decktape package may not have been updated yet to contain the fix for the spawn EACCES error.

[pat-s]

@JJK96
I cannot get the AUR package to build since 2.8.0.
Maybe with the next release of decktape. See the issue about the AUR package in this repo.

[JJK96]

Yeah, I forgot that I had to edit the pkgbuild to make it work, I believe it was removing a rmdir line.