totem-video-thumbnailer crashed with SIGSEGV in gst_type_find_factory_call_function()

[Taylor Raack]

Not sure exactly how this crash happened - i was just browsing a video and got this crash.

ProblemType: Crash
DistroRelease: Ubuntu 11.10
Package: totem 3.0.1-0ubuntu7.1
ProcVersionSignature: Ubuntu 3.0.0-14.23-generic-pae 3.0.9
Uname: Linux 3.0.0-14-generic-pae i686
ApportVersion: 1.23-0ubuntu4
Architecture: i386
Date: Sat Dec 10 21:35:39 2011
EcryptfsInUse: Yes
ExecutablePath: /usr/bin/totem-video-thumbnailer
InstallationMedia: Ubuntu-Netbook 10.04 "Lucid Lynx" - Release i386 (20100429.4)
ProcCmdline: /usr/bin/totem-video-thumbnailer -s 128 file:///media/THE_FLY_SE_D1/VIDEO_TS/VIDEO_TS.VOB /tmp/.gnome_desktop_thumbnail.9XP75V
ProcEnviron:
 SHELL=/bin/bash
 PATH=(custom, no user)
 LANG=en_US.UTF-8
SegvAnalysis:
 Segfault happened at: 0xb5a928f9: movzbl (%eax),%edx
 PC (0xb5a928f9) ok
 source "(%eax)" (0x00000000) not located in a known VMA region (needed readable region)!
 destination "%edx" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: totem
StacktraceTop:
 ?? () from /usr/lib/gstreamer-0.10/libgsttypefindfunctions.so
 gst_type_find_factory_call_function () from /usr/lib/libgstreamer-0.10.so.0
 gst_type_find_helper_get_range_ext () from /usr/lib/libgstbase-0.10.so.0
 ?? () from /usr/lib/gstreamer-0.10/libgstcoreelements.so
 gst_pad_set_active () from /usr/lib/libgstreamer-0.10.so.0
Title: totem-video-thumbnailer crashed with SIGSEGV in gst_type_find_factory_call_function()
UpgradeStatus: Upgraded to oneiric on 2011-12-03 (13 days ago)
UserGroups: fuse mail sudo www-data

[Apport retracing service (apport)]

Thank you for taking the time to report this crash and helping to make this software better. This particular crash has already been reported and is a duplicate of bug #812838, so is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Please continue to report any other bugs you may find.