openNI_camera compiling problem

edit

Your program is failing at runtime because it cannot find libusb. The most likely answer is that you are using a build from a few days ago that had a bug, see this question: http://answers.ros.org/question/162/building-ni-on-ubuntu-1010-and-diamondback-cant

and Tully responded:

There was a missing export of -lusb in the openni_camera. I've patched it in the master branch of ni.

However, if you have already updated and are still getting this problem, then you need to be sure that you have libusb installed (Check synaptic package manager) and a path to it. Along those lines, plug in your kinect and use lsusb to be sure it is recognized.

Although, this is not directly related to your problem, if you are having trouble with libusb, then it is possible you have not used usb devices with Linux much, so you may want to look at how to set up permissions for that. This was covered in the kinect Getting Started tutorial but, unfortunately, when WG decided to go with the OpenNi driver, the older kinect tutorial was deprecated and the Getting Started tutorial eliminated. That's too bad because it told how to set up USB permissions that you need to do to get the kinect to work. It also listed the sort of results you should see from lsusb if the kinect is recognized correctly. The good news is that google has that paged cached. So look at look at the cache result of the first hit on google with this search: ros kinect getting started

and, in case the cache is lost, here are the pertinent lines:

Setup Port

1. Plug in Kinect to USB port

2. Open up permissions on usb port

   sudo chmod 777 -R /dev/bus/usb

udev way

Using udev rules, your computer will always be setup to use the kinect. This only needs to be done once. In Lucid, paste the following into /etc/udev/rules.d/53-kinect.rules Hint: use sudo.

SUBSYSTEM=="usb", ATTR{idVendor}=="045e", ATTR{idProduct}=="02b0", MODE="0666" SUBSYSTEM=="usb", ATTR{idVendor}=="045e", ATTR{idProduct}=="02ad", MODE="0666" SUBSYSTEM=="usb", ATTR{idVendor}=="045e", ATTR{idProduct}=="02ae", MODE="0666"

Make sure the kinect is disconnected from your computer and run:

sudo service udev reload

Then reconnect your kinect - permissions should be normal (read/write).