djcas9/komanda

Linux libudev link issue / General Linux Startup Issues

Open

#32 opened on Jun 16, 2014

View on GitHub
 (11 comments) (0 reactions) (0 assignees)JavaScript (1,790 stars) (75 forks)batch import
bughelp wanted

Description

Running results in following error:

./Komanda: error while loading shared libraries: libudev.so.0: cannot open shared object file: No such file or directory

I believe the issue is related to this but putting symbolic links anywhere doesn't work, no matter where I put them. Since this is all built rather than running node-webkit manually, I don't know how to work around this.

Contributor guide

Tech stack
javascriptelectron
Domain
desktop
Issue type
bug
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
3
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
1-3 hours
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
stale
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
clear
Prerequisites
Linux command linesymbolic linkslibudev
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
45
Research direction
Investigate the libudev linking error by checking the system's libudev version and using `ldd ./Komanda` to see missing libraries. Refer to the linked node webkit wiki for symlink solutions, but note that the user tried symlinks without success. Consider installing the correct libudev version or creating a symlink from libudev.so.1 to libudev.so.0. Also check if the application needs a specific build of node webkit.