Description of problem: crash at startup of the programm Version-Release number of selected component: libfreenect-0.5.2-5.fc23 Additional info: reporter: libreport-2.6.4 backtrace_rating: 4 cmdline: freenect-cppview crash_function: Freenect::FreenectDevice::FreenectDevice executable: /usr/bin/freenect-cppview global_pid: 3038 kernel: 3.18.17-8.pvops.qubes.x86_64 runlevel: N 3 type: CCpp uid: 1000 Truncated backtrace: Thread no. 1 (3 frames) #6 Freenect::FreenectDevice::FreenectDevice at /usr/src/debug/libfreenect-b2043d02b66c9c59899bbf09cb1a13206e8fa10d/wrappers/cpp/libfreenect.hpp:68 #7 MyFreenectDevice::MyFreenectDevice at /usr/src/debug/libfreenect-b2043d02b66c9c59899bbf09cb1a13206e8fa10d/wrappers/cpp/cppview.cpp:81 #8 Freenect::Freenect::createDevice<MyFreenectDevice> at /usr/src/debug/libfreenect-b2043d02b66c9c59899bbf09cb1a13206e8fa10d/wrappers/cpp/libfreenect.hpp:206
Created attachment 1128866 [details] File: backtrace
Created attachment 1128867 [details] File: cgroup
Created attachment 1128868 [details] File: core_backtrace
Created attachment 1128869 [details] File: dso_list
Created attachment 1128870 [details] File: environ
Created attachment 1128871 [details] File: limits
Created attachment 1128872 [details] File: maps
Created attachment 1128873 [details] File: mountinfo
Created attachment 1128874 [details] File: namespaces
Created attachment 1128875 [details] File: open_fds
Created attachment 1128876 [details] File: proc_pid_status
Created attachment 1128877 [details] File: var_log_messages
So this is "normal" behavior for freenect-cppview if there is no kinect device attached to your PC. The freenect cpp wrapper throws an exception when it can't connect to a kinect device, and the cppview code isn't catching that exception, so abort() is raised and the program "crashes." I can patch cppview to catch the exception and print out the exception message. The more important question is did you actually have a kinect device attached to your PC? If so, cppview should have found it, and if it didn't then there's something wrong with the udev rules or device permissions. I checked freenect-cppview with my kinect and it fired up just fine, so there may be an error with your system's setup.
libfreenect-0.5.3-1.fc23 has been submitted as an update to Fedora 23. https://bodhi.fedoraproject.org/updates/FEDORA-2016-4b13a81dd9
libfreenect-0.5.3-1.fc23 has been pushed to the Fedora 23 testing repository. If problems still persist, please make note of it in this bug report. See https://fedoraproject.org/wiki/QA:Updates_Testing for instructions on how to install test updates. You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2016-4b13a81dd9
(In reply to Rich Mattes from comment #13) > So this is "normal" behavior for freenect-cppview if there is no kinect > device attached to your PC. The freenect cpp wrapper throws an exception > when it can't connect to a kinect device, and the cppview code isn't > catching that exception, so abort() is raised and the program "crashes." I > can patch cppview to catch the exception and print out the exception message. > > The more important question is did you actually have a kinect device > attached to your PC? Yes, a Kinect 360, forgot to connect the power cord for the addional power so only the Kinect motor shows up in lsusb. After connecting the power cord the programm freenect-cppview runs and shows the kinect picture and depthfieldview. > If so, cppview should have found it, and if it didn't > then there's something wrong with the udev rules or device permissions. I > checked freenect-cppview with my kinect and it fired up just fine, so there > may be an error with your system's setup.
libfreenect-0.5.3-1.fc23 has been pushed to the Fedora 23 stable repository. If problems still persist, please make note of it in this bug report.