GNOME Bugzilla – Bug 319359
v4l2src error when trying to get device norm + segmentation fault
Last modified: 2006-01-14 13:23:01 UTC
gst-launch-0.8 v4l2src device=/dev/video0 ! fakesinc v4l2_calls.c(483): gst_v4l2_get_norm Faild to get the current norm for device /dev/video0: Invalid argument Segmentation fault. I'm using a webcam with the sn9c102 driver (1.0.24) from the 2.6.13 kernel.
Can you please get a backtrace? (see http://live.gnome.org/GettingTraces) thanks
Lowering to major as it's been a month without reply. Another month and the bug gets closed.
Sorry for the late response. Here is the backtrace (gdb) run Starting program: /usr/bin/gst-launch-0.8 v4l2src device=/dev/video0 [Thread debugging using libthread_db enabled] [New Thread -1213696336 (LWP 26143)] RUNNING pipeline ... Program received signal SIGSEGV, Segmentation fault. [Switching to Thread -1213696336 (LWP 26143)] 0xb7f97020 in gst_v4l2_set_defaults (v4l2element=0x806e488) at v4l2_calls.c:348 348 v4l2_calls.c: No such file or directory. in v4l2_calls.c (gdb) thread apply all bt
+ Trace 64338
Thread 1 (Thread -1213696336 (LWP 26143))
Hope this is what you wanted. I'm very new to this all :(
Thanks for the bug report. This particular bug has already been reported into our bug tracking system, but please feel free to report any further bugs you find. *** This bug has been marked as a duplicate of 314160 ***