-
Notifications
You must be signed in to change notification settings - Fork 56
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
'process has died' while executing openni.launch with Kinect1 #54
Comments
Can you try #52 as mentioned in #18 (comment) and see if that fixes your issue? |
@130s I tried. But I got compile error: |
@130s |
Only based on my assumption below with #52, yes it can/might work on ROS Kinetic:
|
@130s |
@130s |
@130s When I compile the code,I see lots of warning like this |
@130s I've already got the point. |
This issue finally comes to an end. @fmnoori |
@blueeaglex How to uninstall the driver ? Could you please tell me the command |
@TanayaBhave |
@blueeaglex |
我也是,你解决了吗?求教 |
@blueeaglex Thanks for tracking the issue down!
I'm not exactly sure what you mean by this, but IMO the dependency on the proprietary driver is defined in package.xml in this line so that it automatically gets installed by standard installation process (e.g. on Ubuntu, Closing. I see a few people have asked follow-up question but that's not the usage this issue tracker is designed for. Please open a question on http://answers.ros.org/ |
Hardware:1.kinect1.0 for xbox360
2.PC with usb2.0
Software: Ubuntu16.04 LTS, ros-kinetic-desktop-full
I tried to excute openni.launch and get these errors:
I tried the ideas of these links:
http://answers.ros.org/question/53089/ubuntu-1210-groovy-openni-usb30-working/
http://answers.ros.org/question/135266/problem-running-openni_launchlaunch-failed-to-load-nodelet-cameradriver-of-type-openni_cameradriver-could-not-find-library-corresponding-to-plugin/
http://answers.ros.org/question/54863/camera_nodelet_manager-1-process-has-died-error-with-kinect/
But it doesn't work.
I can run the standalone NIViewer with kinect. So I think the kinect driver should be OK on ubuntu 16.04 LTS.
Has anyone found the way to walk through this?
I think this issue may have sth. to do with this one:
#18
The text was updated successfully, but these errors were encountered: