totem-plugin-viewer crashed with SIGSEGV

[Gvozdik Artem]

Binary package hint: totem

Beta 1
crashed on firefox page : http://www.montecarlo.ru/onlineradio.asp -> http://station.ru/OnlyFMPlayer.aspx?station=montecarlo&play=1&play=1

ProblemType: Crash
DistroRelease: Ubuntu 11.04
Package: totem 2.32.0-0ubuntu10
ProcVersionSignature: Ubuntu 2.6.38-7.39-generic 2.6.38
Uname: Linux 2.6.38-7-generic i686
NonfreeKernelModules: nvidia
Architecture: i386
Date: Mon Apr 4 20:02:41 2011
ExecutablePath: /usr/lib/totem/totem-plugin-viewer
InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Beta i386 (20110330)
ProcCmdline: /usr/lib/totem/totem-plugin-viewer --plugin-type gmp --user-agent Windows-Media-Player/10.00.00.4019 --referrer http://station.ru/OnlyFMPlayer.aspx?station=montecarlo&play=1 --mimetype video/x-msvideo --hidden
ProcEnviron:
 LANGUAGE=en_US:en
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SegvAnalysis:
 Segfault happened at: 0xd0e2c4: mov 0x8(%eax),%eax
 PC (0x00d0e2c4) ok
 source "0x8(%eax)" (0x00000008) not located in a known VMA region (needed readable region)!
 destination "%eax" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: totem
Stacktrace:
 #0 0x00d0e2c4 in ?? ()
 No symbol table info available.
 Cannot access memory at address 0xbf9f3cfc
StacktraceTop: ?? ()
Title: totem-plugin-viewer crashed with SIGSEGV
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare

[Apport retracing service (apport)]

Stacktrace:
 #0 0x00d0e2c4 in totem_embedded_play (emb=0x2283d000, error=<value optimized out>) at totem-plugin-viewer.c:479
         err = <error reading variable err (Cannot access memory at address 0xbf9f3cec)>
 Cannot access memory at address 0xbf9f3cfc
StacktraceTop: totem_embedded_play (emb=0x2283d000, error=<value optimized out>) at totem-plugin-viewer.c:479

[Walter Garcia-Fontes (walter-garcia)]

Thank you for taking the time to report this bug and helping to make Ubuntu better. This particular bug has already been reported and is a duplicate of bug 732706 , so it 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. Feel free to continue to report any other bugs you may find.