Roslaunch leap_motion sensor_sender.launch not working

[juantelo95]

Hi guys, I'm trying to implement the leap motion with ROS indigo and I used the tutorials and have set up everything as they say, however, whenever I try to execute the command line:

roslaunch leap_motion sensor_sender.launch

this shows up

... logging to /home/juantelo/.ros/log/73513fa2-be34-11e7-86a9-1c394718bbbd/roslaunch-JuanTelo-11993.log
    Checking log directory for disk usage. This may take awhile.
    Press Ctrl-C to interrupt
    Done checking log file disk usage. Usage is <1GB.

    started roslaunch server http://JuanTelo:42806/ 

    SUMMARY
    ========

    PARAMETERS
    * /rosdistro: indigo
    * /rosversion: 1.11.21

    NODES
      /
        sender_freq (leap_motion/sender.py)

     ROS_MASTER_URI=http://localhost:11311

    core service [/rosout] found
    process[sender_freq-1]: started with pid [12011]
    [sender_freq-1] process has died [pid 12011, exit code -11, cmd /home/juantelo/catkin_ws/src/leap_motion/scripts/sender.py _freq:=0.01 __name:=sender_freq __log:=/home/juantelo/.ros/log/73513fa2-be34-11e7-86a9-1c394718bbbd/sender_freq-1.log].
    log file: /home/juantelo/.ros/log/73513fa2-be34-11e7-86a9-1c394718bbbd/sender_freq-1*.log
    all processes on machine have died, roslaunch will exit
    shutting down processing monitor...
    ... shutting down processing monitor complete
    done

and it closes.

Anyone knows how I Can solve this?

[jdonald]

Exit code -11 is a segmentation fault. The instructions for that ROS package do appear a bit error-prone, manually setting one's PYTHONPATH and all. Linking to the wrong library or a change in Python version could potentially cause a segmentation fault. Have you confirmed that the Leap Motion Python API sample program works on your system?

If Python + Leap Motion normally works on your system, the next step would be to debug the cause of the segmentation fault. Here are some instructions for attaching gdb when running roslaunch.