totem-plugin-viewer crashed with SIGSEGV in dbus_glib_marshal_totem_embedded_BOOLEAN__STRING_POINTER()

[ngsupb]

It happens when I open this page: http://www.maximum.ru/maximumtvonline/ first time

after restarting usually it starts to work fine and play music.

ProblemType: Crash
DistroRelease: Ubuntu 11.10
Package: libgstreamer0.10-0 0.10.35-1
ProcVersionSignature: Ubuntu 3.0.0-12.20-generic 3.0.4
Uname: Linux 3.0.0-12-generic x86_64
ApportVersion: 1.23-0ubuntu2
Architecture: amd64
CrashCounter: 1
Date: Sat Oct 8 21:34:58 2011
ExecutablePath: /usr/lib/totem/totem-plugin-viewer
InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Beta amd64 (20110901)
ProcCmdline: /usr/lib/totem/totem-plugin-viewer --plugin-type gmp --user-agent Windows-Media-Player/10.00.00.4019 --referrer http://www.maximum.ru/maximumtvonline/ --mimetype video/x-msvideo --hidden
SegvAnalysis:
 Segfault happened at: 0x7f0de5d3c477: mov 0x8(%rax),%rcx
 PC (0x7f0de5d3c477) ok
 source "0x8(%rax)" (0x00000008) not located in a known VMA region (needed readable region)!
 destination "%rcx" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: gstreamer0.10
StacktraceTop:
 ?? ()
 dbus_glib_marshal_totem_embedded_BOOLEAN__STRING_POINTER ()
 ?? () from /usr/lib/x86_64-linux-gnu/libdbus-glib-1.so.2
 ?? () from /lib/x86_64-linux-gnu/libdbus-1.so.3
 dbus_connection_dispatch () from /lib/x86_64-linux-gnu/libdbus-1.so.3
Title: totem-plugin-viewer crashed with SIGSEGV in dbus_glib_marshal_totem_embedded_BOOLEAN__STRING_POINTER()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare

[Apport retracing service (apport)]

Thank you for taking the time to report this crash and helping to make Ubuntu better. This particular crash has already been reported and is a duplicate of bug #752957, 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.