1) The Ni-UserTracker program starts.
> [New Thread 0x7ffff198b700 (LWP 2489)]
2) The first user is detected. His calibration starts.
> 1325852879 New User 1
> 1325852879 Calibration started for user 1
3) It calibrates successfully and OpenNI starts tracking it.
> 1325852881 Calibration complete, start tracking user 1
4) The second user is detected. His calibration starts.
> 1325852890 New User 2
> 1325852890 Calibration started for user 2
5) BOOM!
> [Thread 0x7ffff198b700 (LWP 2489) exited]
> Program received signal SIGSEGV, Segmentation fault.
Anyway, in the first crash, the problem comes from NITE itself,
(libXnVFeatures_1_5_2.so) but in the second, the crash happens at the
FGLRX graphics driver --so it's not unexpected it gets removed when the
image is not displayed.
I'll try to reproduce and tell you something --I also have FGLRX.
Regards,
Xavier Mendez
* The first crash is originated in the NITE-middleware,
not OpenNI itself.
> I also got a new bug from the java wrapper:
>
> org.OpenNI.StatusException: A timeout has occurred when waiting for
> new data!
* That's an OpenNI bug it sometimes starts appearing in *any* program
(not only Java).
On my system, it doesn't disappear until I restart the PC.
BUT, I've made a lot of programs with Java+OpenNI and my own programs
don't crash; the OpenNI samples do.
Anyway, I think that's a minor importance bug,
because it occurs at exit only.
--
You received this message because you are subscribed to the Google Groups "OpenNI" group.
To post to this group, send email to openn...@googlegroups.com.
To unsubscribe from this group, send email to openni-dev+...@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/openni-dev?hl=en.
I tried to reproduce the crash you are describing but to no avail.
I used Ubuntu 10.10 64Bit with the latest stable release 20.4.2.20 on a Dell XPS M1530 laptop.
I installed all the packages on a "fresh" OS and everything just worked perfectly.
Can you please share some more information on the crash? E.g., activate the client and server logging mechanism and publish the logs for review.
In order to turn on the log mechanism:
1) Turning on the log of the OpenNI client:
Please make the highlighted change below into OpenNI_Installtion_Path\OpenNI\Data\SamplesConfig.xml file (or if you are using your own XML, please perform the changes to it). Then please re-run your application and send back the log file (name is composed of date and hour) created under Log folder in your working folder.
<Log writeToConsole="true" writeToFile="true">
<LogLevel value="0" />
<Mask name="ALL" on="true" />
2) Turning on the log of the OpenNI server:
Please make the highlighted change below into Sensor_Installtion_Path\Sensor\Config\GlobalDefaults.ini file. Then please re-run your application and send back the log file (name is composed of date and hour) created under Log folder: Sensor_Installtion_Path\Sensor\Bin\Log.
[Core]
; 0 - Verbose, 1 - Info, 2 - Warning, 3 - Error (default)
LogLevel=0
; leave empty for nothing (default). ALL - all masks
LogMasks=ALL
; 0 - No (default), 1 - Yes
;LogWriteToConsole=1
; 0 - No (default), 1 - Yes
LogWriteToFile=1
Thank you,
Regards,
Lior C.
hi,
OpenNI 1.5.2.23
NITE 1.5.2.21
...
--
I notice that you are using Ubuntu 11.10. PrimeSense package is currently supported on 10.10. I've tried everything on this version and it worked great for me. Please send us some logs if you experience same issue on 10.10.
Thanks,
Regards,
Lior C.
Hi,
--
It is mentioned in my preview post:
Client Logs: "created under Log folder in your working folder."
Server Logs: "created under Log folder: Sensor_Installtion_Path\Sensor\Bin\Log."
--
You received this message because you are subscribed to the Google Groups "OpenNI" group.
To view this discussion on the web visit https://groups.google.com/d/msg/openni-dev/-/xaNnN3EHuY0J.