-
-
Notifications
You must be signed in to change notification settings - Fork 2.6k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
在服务器上不能启动 #1515
Comments
If you are using Ubuntu Linux, try to run:
|
Merge to #1152 |
centos的用户可以安装这些依赖 1.yum install libXScrnSaver* 2.yum install epel-release 3.yum install libappindicator-gtk3 原文:https://blog.csdn.net/f1370335844/article/details/80460071 |
I use ubuntu in Windows. And igot the same erro. But after i running "apt-get install libxss1" i still get these errors.----> |
node bot.js TROUBLESHOOTING: https://github.com/GoogleChrome/puppeteer/blob/master/docs/troubleshooting.md 23:40:07 ERR PuppetPuppeteer initBridge() exception: Error: Failed to launch chrome! TROUBLESHOOTING: https://github.com/GoogleChrome/puppeteer/blob/master/docs/troubleshooting.md 23:40:07 ERR PuppetPuppeteer initBridge() this.bridge.stop() rejection: Error: no page TROUBLESHOOTING: https://github.com/GoogleChrome/puppeteer/blob/master/docs/troubleshooting.md Error: Error: Error: Error: Failed to launch chrome! TROUBLESHOOTING: https://github.com/GoogleChrome/puppeteer/blob/master/docs/troubleshooting.md
23:40:07 ERR Wechaty start() exception: Error: Error: Error: Failed to launch chrome! TROUBLESHOOTING: https://github.com/GoogleChrome/puppeteer/blob/master/docs/troubleshooting.md (node:95) UnhandledPromiseRejectionWarning: Error: Error: Error: Error: Failed to launch chrome! TROUBLESHOOTING: https://github.com/GoogleChrome/puppeteer/blob/master/docs/troubleshooting.md
(node:95) 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(). (rejection id: 2) |
i still get these errors too. |
i guess maybe it doesn’t support ubuntu so perfect as i followed every
step of its instructions.
matrixhome <notifications@github.com>于2019年6月12日 周三17:02写道:
… I use ubuntu in Windows. And igot the same erro. But after i running
"apt-get install libxss1" i still get these errors.---->
i still get these errors too.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
<#1515>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AJKLXCN6ZAKEH6P5IAWMLWTP2C3Q3ANCNFSM4FM6VY4Q>
.
|
sudo apt-get install gconf-service libasound2 libatk1.0-0 libatk-bridge2.0-0 libc6 libcairo2 libcups2 libdbus-1-3 libexpat1 libfontconfig1 libgcc1 libgconf-2-4 libgdk-pixbuf2.0-0 libglib2.0-0 libgtk-3-0 libnspr4 libpango-1.0-0 libpangocairo-1.0-0 libstdc++6 libx11-6 libx11-xcb1 libxcb1 libxcomposite1 libxcursor1 libxdamage1 libxext6 libxfixes3 libxi6 libxrandr2 libxrender1 libxss1 libxtst6 ca-certificates fonts-liberation libappindicator1 libnss3 lsb-release xdg-utils wget |
i’ll try later,thanks
Tim Qian <notifications@github.com>于2019年6月19日 周三08:57写道:
… libxss1 seems not enough, try install all the following libs(works for me)
sudo apt-get install gconf-service libasound2 libatk1.0-0 libatk-bridge2.0-0 libc6 libcairo2 libcups2 libdbus-1-3 libexpat1 libfontconfig1 libgcc1 libgconf-2-4 libgdk-pixbuf2.0-0 libglib2.0-0 libgtk-3-0 libnspr4 libpango-1.0-0 libpangocairo-1.0-0 libstdc++6 libx11-6 libx11-xcb1 libxcb1 libxcomposite1 libxcursor1 libxdamage1 libxext6 libxfixes3 libxi6 libxrandr2 libxrender1 libxss1 libxtst6 ca-certificates fonts-liberation libappindicator1 libnss3 lsb-release xdg-utils wget
ref: puppeteer/puppeteer#3443 (comment)
<puppeteer/puppeteer#3443 (comment)>
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
<#1515>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AJKLXCMMUH4SI2T67ERJLC3P3F77LANCNFSM4FM6VY4Q>
.
|
It does't work.My linux version is CentOS Linux release 7.6.1810 (Core) |
Have you resulved this problems now ? My linux is CentOS also,I tried to figure out this problems two days ,but noting can work!!!! |
Have you resulved this problems now ? My linux is CentOS also |
Please try installing |
npm WARN config init.module Use npm ERR! A complete log of this run can be found in: |
docker err |
14:22:07 INFO Wechaty start() v0.18.5 is starting...
14:22:07 INFO Wechaty initPuppet() using puppet: default
14:22:07 INFO Wechaty initPuppet() inited puppet: Puppet#0(default)
14:22:07 ERR PuppetPuppeteerBridge start() exception: Error: Failed to launch chrome!
/home/webgame/nodeSever/hongbao/node_modules/_wechaty@0.18.5@wechaty/node_modules/puppeteer/.local-chromium/linux-575458/chrome-linux/chrome: error while loading shared libraries: libXss.so.1: cannot open shared object file: No such file or directory
TROUBLESHOOTING: https://github.com/GoogleChrome/puppeteer/blob/master/docs/troubleshooting.md
14:22:07 ERR PuppetPuppeteer initBridge() exception: Error: Failed to launch chrome!
/home/webgame/nodeSever/hongbao/node_modules/_wechaty@0.18.5@wechaty/node_modules/puppeteer/.local-chromium/linux-575458/chrome-linux/chrome: error while loading shared libraries: libXss.so.1: cannot open shared object file: No such file or directory
TROUBLESHOOTING: https://github.com/GoogleChrome/puppeteer/blob/master/docs/troubleshooting.md
Error: no page
at Bridge. (/home/webgame/nodeSever/hongbao/node_modules/_wechaty@0.18.5@wechaty/node_modules/wechaty-puppet-puppeteer/dist/src/bridge.js:253:23)
at Generator.next ()
at /home/webgame/nodeSever/hongbao/node_modules/_wechaty@0.18.5@wechaty/node_modules/wechaty-puppet-puppeteer/dist/src/bridge.js:26:71
at new Promise ()
at __awaiter (/home/webgame/nodeSever/hongbao/node_modules/_wechaty@0.18.5@wechaty/node_modules/wechaty-puppet-puppeteer/dist/src/bridge.js:22:12)
at Bridge.stop (/home/webgame/nodeSever/hongbao/node_modules/_wechaty@0.18.5@wechaty/node_modules/wechaty-puppet-puppeteer/dist/src/bridge.js:250:16)
at PuppetPuppeteer. (/home/webgame/nodeSever/hongbao/node_modules/_wechaty@0.18.5@wechaty/node_modules/wechaty-puppet-puppeteer/dist/src/puppet-puppeteer.js:219:35)
at Generator.throw ()
at rejected (/home/webgame/nodeSever/hongbao/node_modules/_wechaty@0.18.5@wechaty/node_modules/wechaty-puppet-puppeteer/dist/src/puppet-puppeteer.js:23:65)
at
at process._tickDomainCallback (internal/process/next_tick.js:228:7)
14:22:07 ERR PuppetPuppeteer start() exception: Error: Error: Error: Failed to launch chrome!
/home/webgame/nodeSever/hongbao/node_modules/_wechaty@0.18.5@wechaty/node_modules/puppeteer/.local-chromium/linux-575458/chrome-linux/chrome: error while loading shared libraries: libXss.so.1: cannot open shared object file: No such file or directory
TROUBLESHOOTING: https://github.com/GoogleChrome/puppeteer/blob/master/docs/troubleshooting.md
Error: Error: Error: Error: Failed to launch chrome!
/home/webgame/nodeSever/hongbao/node_modules/_wechaty@0.18.5@wechaty/node_modules/puppeteer/.local-chromium/linux-575458/chrome-linux/chrome: error while loading shared libraries: libXss.so.1: cannot open shared object file: No such file or directory
TROUBLESHOOTING: https://github.com/GoogleChrome/puppeteer/blob/master/docs/troubleshooting.md
14:22:07 ERR Wechaty start() exception: Error: Error: Error: Failed to launch chrome!
/home/webgame/nodeSever/hongbao/node_modules/_wechaty@0.18.5@wechaty/node_modules/puppeteer/.local-chromium/linux-575458/chrome-linux/chrome: error while loading shared libraries: libXss.so.1: cannot open shared object file: No such file or directory
TROUBLESHOOTING: https://github.com/GoogleChrome/puppeteer/blob/master/docs/troubleshooting.md
Error: Error: Error: Error: Failed to launch chrome!
/home/webgame/nodeSever/hongbao/node_modules/_wechaty@0.18.5@wechaty/node_modules/puppeteer/.local-chromium/linux-575458/chrome-linux/chrome: error while loading shared libraries: libXss.so.1: cannot open shared object file: No such file or directory
TROUBLESHOOTING: https://github.com/GoogleChrome/puppeteer/blob/master/docs/troubleshooting.md
The text was updated successfully, but these errors were encountered: