-
Notifications
You must be signed in to change notification settings - Fork 3.9k
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
Lack of libudev.so lib #136
Comments
Update your OS. libudev.so is a part of the newer udev versions (since udev replaced DeviceKit/HAL). If you cannot update your OS for some reason, you can try either re-compiling node-webkit (don't recommend it, the process is slow, takes up a lot of space, and I doubt it would compile with your old OS), or updating your udev - which I doubt is possible, since udev is a crucial system package - it would require a newer kernel, and it would force updating all the other packages on your system - you'll end up with what you'll end up if you just install a newer Ubuntu. |
Close this for the reason @Ivshti gave above. |
What about systems that don't use udev or use a newer version of udev like newer ArchLinux desktops? |
I use archlinux; I believe you've got a hard requirement on old udev version:
|
supporting libudev.so.0 is essential for Linux Desktop distributions. For distributions lacking of that support, before it's fixed in distribution, a special version without the dependency can be built but you'll lose the support for things such as hot plugged USB camera. See http://code.google.com/p/chromium/issues/detail?id=130019 |
No, the problem isn't a system lacking udev, but node-webkit hard-coding the dependency on an older version of udev. As @daurnimator mentioned, his system has [email protected]. He can run chromium 23 just fine on it. |
chrome 23 doesn't have the functionality depends on udev. And the dependency is not an "old" version of udev, but a up-to-date version providing previous version of API, just like Gtk2 and Gtk3. Distributions should ship both, they can't except all gtk2 applications migrated to Gtk3 APIs suddenly. -------- Original Message -------- No, the problem isn't a system lacking udev, but node-webkit hard-coding the dependency on an older version of udev. As @daurnimator mentioned, his system has [email protected]. He can run chromium 23 just fine on it. Reply to this email directly or view it on GitHub: |
btw, we are on the newest chromium version which has the support for hot-plugged devices which depends on udev. chrome 23 doesn't have the feature. |
fyi, the first number after ".so" marks the API version, while the following two mark the code version. |
After using ubuntu to compile and then packaging it up in an rpm, it refuses to install on Fedora 18 due to not having libudev.so.0 Any chance at getting this fixed anytime soon? Fedora 18 comes with libudev-1.2.1 |
@owenc4a4 that is not a fix, and extremely unsafe. The extension ( |
@daurnimator I understand your concern. But it is what Google is doing for Chrome on Linux. We just follow their solution for this. And it's not just a rebuild effort -- code need to be modified since the API changed -- the major version indicates an API change. |
In my Ubuntu 12.10 run the following command via terminal and it worked sudo ln -s /lib/i386-linux-gnu/libudev.so.1 /lib/i386-linux-gnu/libudev.so.0 |
@xavierzhao That is not a proper solution and is highly dangerous, as already noted. |
Got beaten by this bug on fedora 20, libudev.so.0 is not provided nor supported since three releases. I think this bug should be reopened until current version of udev is natively supported by node-webkit. |
While it may be a newer issue, we have #770 currently tracking that. |
fixed it: |
...Also known as the "This might work but I have no idea if it will implode catastrophically because of unknown API incompatibilities" solution. |
@shamun Your solution worked for me , thanks !
|
Downloaded nw_release_linux_x32.tar.gz on ubuntu (8.04) and cannot run 'nw'.
./nw: error while loading shared libraries: libudev.so.0: cannot open shared object file: No such file or directory
The text was updated successfully, but these errors were encountered: