I have encountered two problems on Debian Testing:
1) LeapControlPanel fails to start. It just hangs. I would appreciate any suggestion what I could try to get it working. For now, I try to give some debug information. If I run "strace LeapControlPanel", I see the following message repeated (without leapd running):
poll([{fd=5, events=POLLIN}, {fd=8, events=POLLIN}, {fd=10, events=POLLIN}], 3, 100) = 0 (Timeout)
This poll() repeats few times per second and sometimes instead of "100" I see "99"; according to "ls -l /proc/$(pidof LeapControlPanel)/fd/" fd 10 and 8 are sockets and fd 5 is "anon_inode:[event_fd]". With leapd running these messages are repeated instead (with little variation). I do not know if this is useful information or not. If you need more info to debug the problem or want me to try something else, please let me know. By the way, leapd is working: I can run /usr/bin/Visualizer and see my hands or a tool.
2) "service leapd start" seems to never exit on my system, so installation with "dpkg -i" hangs until I kill leapd manually. Of course, "service leapd stop" does not work properly either. I see Leap package still uses deprecated SysVinit script (creates /etc/init.d/leapd instead of /lib/systemd/system/leapd.service). Today, many distros use systemd by default: Debian (since version 8, current stable version), Arch, Fedora (since 2011), OpenSUSE (since version 13). Unless you have good reason to support SysVinit, I suggest to drop it and use systemd (Ubuntu uses upstart, so it is not affected by this issue). Example of working leapd.service file for systemd.
I have deleted /etc/init/leapd.conf and /etc/init.d/leapd, then created /lib/systemd/system/leapd.service, ran "systemctl daemon-reload" and then "service leapd start" and "stop" begun to work properly. Alternatively, you could either make leapd to demonize by default (then it will work with current /etc/init.d/leapd script) or fix /etc/init.d/leapd script without modifying leapd.