ubuntu 16.10 libpng12.so.0: cannot open shared object file
See original GitHub issueRunning on: "image-webpack-loader": "^3.2.0",
I always get these errors:
Error in ./images/chat-sprite.png
Module build failed: Error: /home/capaj/git_projects/be/chat-window/node_modules/pngquant-bin/vendor/pngquant: error while loading shared libraries: libpng12.so.0: cannot open shared object file: No such file or directory
@ ./styles/main.less 6:22437-22473 6:23930-23966 6:28534-28570 6:32673-32709 6:34586-34622 6:36817-36853 6:37912-37948
I researched a bit and tried installing
sudo apt-get install libpng12-0
sudo apt-get install libpng-dev
I eve tried sudo apt install pngquant
but no luck. Has anyone been able to make this work on latest ubuntu?
Issue Analytics
- State:
- Created 7 years ago
- Reactions:4
- Comments:8
Top Results From Across the Web
How to fix "libpng12.so.0: cannot open shared object file: No ...
I'm just starting out with Lubuntu and I've just installed DaVinci Resolve to do my video editing on. But when I click its...
Read more >Fix libpng12-0 Missing In Ubuntu 18.04, 19.10, 20.04 Or 20.10
In this article you'll find a very easy to apply fix that will allow installing and running applications that depend on libpng12-0 in...
Read more >Ubuntu 17.04 libpng12.so.0: cannot open shared object file #95
Ubuntu 17.04 libpng12.so.0: cannot open shared object file #95 ... It looks like mozjpeg-bin was updated to use libpng 16 from 7.1.0.
Read more >Cannot open shared object file libpng12.so.0 - Stack Overflow
I had the same problem with Quartus Prime 18 on Ubuntu. This worked for me (run as sudo): wget -q -O /tmp/libpng12.deb ...
Read more >ubuntu, libpng12 and libpng16 - Google Groups
I use ubuntu 16.10 and there is not libpng12 package but libpng16 exists. ... libpng12.so.0: cannot open shared object file: No such file...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Well. My issue was actually my mistake and might be yours if you are using docker. I was replacing docker’s
node_modules
folder when runningCOPY . /usr/app
so the local binary was linked to this lib that obviously wasn’t available at the docker machine. Simple addingnode_modules
to.dockerignore
fixed it.Closing because this is a yarn issue. So when I did:
it works fine. Seems like yarn is not able to execute the
postinstall
npm script correctly. @timur-orudzhov are also on yarn? or NPM?