libdbus-1.so.3: no version information available

After installing puppeteer on AWS Elastic Beanstalk in a number of different ways such as via an ebextention script: here or a shell script: here , invoking a new browser always fails. I’ve tried a number of different launch options such as headless mode true/false, no sandbox, executable path etc.

When I run the following command:

ldd chrome | grep not

I get the following response, which is always what follows a failed launch:

./chrome: /lib64/libdbus-1.so.3: no version information available (required by /usr/lib64/libatk-bridge-2.0.so.0)
./chrome: /lib64/libdbus-1.so.3: no version information available (required by /usr/lib64/libatspi.so.0)

Also, from the log on elastic beanstalk, it spits out afterwards:

/var/app/current/node_modules/puppeteer/.local-chromium/linux-722234/chrome-linux/chrome: symbol lookup error: /var/app/current/node_modules/puppeteer/.local-chromium/linux-722234/chrome-linux/chrome: undefined symbol: g_type_class_adjust_private_offset

I have no problems running puppeteer on my local mac os x, but Amazon Linux will not cooperate (as usual).

I should also mention that I’ve tried it on both load balanced and single instance, installation via script or manual via ssh. Always the same issue.

It’s probably dead simple. I just don’t speak Linux. Please help 😦

[eyeb14ck]

Run into the same issue. Fixed it by rolling back to v2.0.0 of Puppeteer. Seems like there’s problems with new Puppeter update from 21d ago. Hope it will be fixed.

[amarinediary]

After extensive research I found a definitive solution.

If you do not enable EPEL and if you continue installing chromium as part of npm install, Puppeteer cannot launch Chromium due to unavailability of libatk-1.0.so.0 and many more packages.

• See @ https://github.com/amarinediary/Puppeteer-AWS-Elastic-Beanstalk-Deployment-Hotfix.

Probably related to:

• #807
• #685
• #6920
• #5379
• #765