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

[Yoshee]

don't know more

ProblemType: Crash
DistroRelease: Ubuntu 14.04
Package: totem 3.10.1-1ubuntu3
ProcVersionSignature: Ubuntu 3.13.0-16.36-generic 3.13.5
Uname: Linux 3.13.0-16-generic i686
ApportVersion: 2.13.3-0ubuntu1
Architecture: i386
CrashCounter: 1
CurrentDesktop: Unity
Date: Sat Mar 8 17:35:12 2014
ExecutablePath: /usr/bin/totem-video-thumbnailer
InstallationDate: Installed on 2012-12-05 (458 days ago)
InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Release i386 (20121017.2)
ProcCmdline: /usr/bin/totem-video-thumbnailer -s 256 file:///media/username/FreeAgent%20Drive/Sammlung/Neue%20Filme/Doku/Geschichte/Nordamerika/Wir.bleiben.bestehen.E02.Die.Vision.des.H%C3%A4uptlings.Tecumseh.GERMAN.DOKU.WS.dTV.mkv /tmp/.gnome_desktop_thumbnail.0BKGCX
SegvAnalysis:
 Segfault happened at: 0xb6d0ff12 <gst_mini_object_replace+50>: mov 0x0(%ebp),%edi
 PC (0xb6d0ff12) ok
 source "0x0(%ebp)" (0x00000034) not located in a known VMA region (needed readable region)!
 destination "%edi" ok
 Stack memory exhausted (SP below stack segment)
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: totem
StacktraceTop:
 gst_mini_object_replace () from /usr/lib/i386-linux-gnu/libgstreamer-1.0.so.0
 ?? () from /usr/lib/i386-linux-gnu/gstreamer-1.0/libgstlibav.so
 ?? () from /usr/lib/i386-linux-gnu/gstreamer-1.0/libgstlibav.so
 ?? () from /usr/lib/i386-linux-gnu/gstreamer-1.0/libgstlibav.so
 ?? () from /usr/lib/i386-linux-gnu/libgstvideo-1.0.so.0
Title: totem-video-thumbnailer crashed with SIGSEGV in gst_mini_object_replace()
UpgradeStatus: Upgraded to trusty on 2014-03-03 (4 days ago)
UserGroups: sudo

[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 #1288758, 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.