gstreamer-properties crashed with SIGSEGV in gst_plugin_feature_type_name_filter()

[Hazim Gazov]

Binary package hint: gnome-media

happened when I clicked the test button for the webcam

ProblemType: Crash
Architecture: amd64
CrashCounter: 1
Date: Sun Jan 20 09:13:35 2008
DistroRelease: Ubuntu 8.04
ExecutablePath: /usr/bin/gstreamer-properties
NonfreeKernelModules: nvidia
Package: gnome-media 2.20.1-1ubuntu1
PackageArchitecture: amd64
ProcCmdline: gstreamer-properties
ProcCwd: /home/tumbleweed
ProcEnviron:
 SHELL=/bin/bash
 PATH=/usr/local/distcc/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games
 LANG=C
Signal: 11
SourcePackage: gnome-media
StacktraceTop:
 gst_plugin_feature_type_name_filter ()
 gst_filter_run ()
 gst_registry_feature_filter ()
 gst_registry_find_feature ()
 gst_element_factory_find ()
Title: gstreamer-properties crashed with SIGSEGV in gst_plugin_feature_type_name_filter()
Uname: Linux tumbleweed 2.6.24-4-generic #1 SMP Mon Jan 14 18:19:11 UTC 2008 x86_64 GNU/Linux
UserGroups: adm admin audio cdrom dialout dip floppy fuse lpadmin netdev plugdev powerdev scanner video

[Apport retracing service (apport)]

StacktraceTop:gst_plugin_feature_type_name_filter () from /usr/lib/libgstreamer-0.10.so.0
gst_filter_run () from /usr/lib/libgstreamer-0.10.so.0
gst_registry_feature_filter () from /usr/lib/libgstreamer-0.10.so.0
gst_registry_find_feature () from /usr/lib/libgstreamer-0.10.so.0
gst_element_factory_find () from /usr/lib/libgstreamer-0.10.so.0

[Pedro Villavicencio (pedro)]

Thanks for the report, that's more like a gstreamer bug, re assigning.

[bjoern (bes-schiessle)]

I have the same problem.
Beside my amd64 system i also have a 32bit system. For me the problem only occurs on the amd64 system so it is probably a special problem of the amd64 architecture.

[Sebastien Bacher (seb128)]

Thank you for your bug report. Do you still get the issue using the current hardy or intrepid versions?

[Hazim Gazov (hazim-gazov)]

Nope, everything works fine now! Seems to have been fixed since the release of Gnome 2.22.

[Sebastien Bacher (seb128)]

closing the bug since that works correctly now