Package Details: leap-motion-driver 2.3.1-7

Git Clone URL: (read-only, click to copy)
Package Base: leap-motion
Description: The Leap Motion Developer SDK
Upstream URL:
Licenses: custom
Submitter: robertfoster
Maintainer: rigred
Last Packager: rigred
Votes: 31
Popularity: 0.000001
First Submitted: 2017-04-16 17:28
Last Updated: 2019-01-31 23:15

Latest Comments

1 2 3 4 5 Next › Last »

parkerlreed commented on 2019-02-01 16:32

@rigred Thanks

rigred commented on 2019-01-31 23:10

@parkerlreed - fixed with the appropriate systemd syntax.

rigred commented on 2019-01-31 21:51

This package is a bit klunky - and includes a good few workarounds to the strange choices made by leap motion.

I'll have to take a look at things and iron out some of it's naughty behaviour.

parkerlreed commented on 2019-01-31 15:49

A suggestion for the leapd.service


ExecStop=/usr/bin/killall -9 leapd

Since leapd does not respond to SIGINT (^C)

More times than not my shutdown hangs because it doesn't exit properly.

parkerlreed commented on 2019-01-29 20:34

Thanks for keeping this up to date! Such a fun device to play with.

rigred commented on 2018-12-28 18:48

That is correct

I've run run ldd over all the binaries & libraries to check and currently only /usr/bin/LeapControlPanel appears to have been linked against /usr/bin/ but also works with the included arch sqlite library.

The upstream leap-motion uses a very windows-like packaging for the included Mono code.

I'm going to test with preloading the included libs to be sure.

robertfoster commented on 2018-12-28 18:22


Acccording to POSIX standard and to your observations, you should move not only the previously highlighted libs but also the Playground data folder (now under /usr/bin and that should be moved under /usr/share or /opt). So I humbly suggest to review and check the paths created by this package and use symlinks to static binaries. Maybe after you have to check if these binaries are executed correctly or if LD_LIBRARY_PRELOAD env variable is needed.

rigred commented on 2018-12-28 17:16

Ok wow - sorry Did not mean any offense by this. I just wanted an explanation.

I don't have an issue taking over the package.

robertfoster commented on 2018-12-28 17:09

@rigred Your attitude is not constructive. This is voluntary work and put a simple and critic "this is BAD" is not something that can help to advance in maintaining packages especially if the criticism come from someone that maintain one only package (rocm-smi) and have no past experiences on AUR. The explaination is based on the fact that the original debs distributed by Leap Motion have this folder structure and, until now, I don't realized that. So thanks for your observations on this kind of shitty proprietary software. I abandon it. Take care of it, if you want, and keep calm

rigred commented on 2018-12-28 16:25

Why does this package include /usr/bin/ ?

This is just breaking plenty of other sqlite dependencies particularly when compiling things with cmake - as cmake finds sqlite in /usr/bin/ instead of /usr/lib/

Can you please explain the reasoning for placing these here?

leap-motion-driver /usr/bin/
leap-motion-driver /usr/bin/
leap-motion-driver /usr/bin/
leap-motion-driver /usr/bin/
leap-motion-driver /usr/bin/
leap-motion-driver /usr/bin/
leap-motion-driver /usr/bin/
leap-motion-driver /usr/bin/

This is BAD