Skip to content
This repository has been archived by the owner on Nov 2, 2018. It is now read-only.

Some OS's use libudev.so.1 and not libudev.so.0 #1

Closed
JBKahn opened this issue Dec 15, 2014 · 7 comments
Closed

Some OS's use libudev.so.1 and not libudev.so.0 #1

JBKahn opened this issue Dec 15, 2014 · 7 comments
Labels

Comments

@JBKahn
Copy link

JBKahn commented Dec 15, 2014

The proposed solution worked for me. Perhaps an addition to the README if you're interested in adding that.

http://askubuntu.com/questions/330935/error-while-loading-shared-libraries-libudev-so-0-brackets

Otherwise it just gave me this message when I went to run it

./resources/node-webkit/Linux64/nw: error while loading shared libraries: libudev.so.0: cannot open shared object file: No such file or directory

@wlaurance
Copy link
Contributor

Awesome! thanks.

wlaurance added a commit that referenced this issue Dec 15, 2014
@JBKahn
Copy link
Author

JBKahn commented Dec 15, 2014

np 👍

@wlaurance
Copy link
Contributor

I've changed the install procedure. @JBKahn If you don't mind can you try

npm install slack-for-linux -g
slack-for-linux

and see if you get the same issue?

Thanks

@JBKahn
Copy link
Author

JBKahn commented Dec 17, 2014

Just had an exam today, I'll give it a shot tomorrow night.

@dambrisco
Copy link

I ran into the same issue and using the npm install didn't work. I ended up copying libudev.so.1 to libudev.so.0 and it works fine.

@wlaurance
Copy link
Contributor

OK thanks. I'll look into the underlying grunt builder and see if we can
check for the existence of 0 or 1 and properly link the shared object.
On Dec 17, 2014 3:28 AM, "Dan Ambrisco" notifications@github.com wrote:

I ran into the same issue and using the npm install didn't work. I ended
up copying the files to the .0 names and it seems to run fine.


Reply to this email directly or view it on GitHub
#1 (comment)
.

@wlaurance
Copy link
Contributor

Until there is an official fix in node-webkit, I think we should add some logic to the install script to check for the existence of the proper lib.

See #16

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Projects
None yet
Development

No branches or pull requests

4 participants