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

Bug #1011348 reported by gogo
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
totem (Ubuntu)
New
Undecided
Unassigned

Bug Description

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

ProblemType: Crash
DistroRelease: Ubuntu 12.10
Package: totem 3.4.2-1ubuntu3
ProcVersionSignature: Ubuntu 3.4.0-5.11-generic 3.4.0
Uname: Linux 3.4.0-5-generic x86_64
ApportVersion: 2.1.1-0ubuntu2
Architecture: amd64
Date: Mon Jun 11 00:59:54 2012
ExecutablePath: /usr/lib/totem/totem-plugin-viewer
InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Alpha amd64 (20120606.2)
ProcCmdline: /usr/lib/totem/totem-plugin-viewer --plugin-type gmp --user-agent Windows-Media-Player/10.00.00.4019 --referrer http://mp-cdn.choopa.net/movies/extremeassociates/gofuckyerselfagain/02/gofuckyerselfagain_02_0800.wmv?sid=de06aff7bb217d39542e66ae696964c1 --mimetype video/x-ms-wmv
SegvAnalysis:
 Segfault happened at: 0x416103: mov 0x8(%rax),%rcx
 PC (0x00416103) 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: totem
StacktraceTop:
 ?? ()
 ?? () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
 g_signal_emit_valist () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
 g_signal_emit () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
 ?? () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0
Title: totem-plugin-viewer crashed with SIGSEGV in g_signal_emit_valist()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

Revision history for this message
gogo (trebelnik-stefina) wrote :
Revision history for this message
Apport retracing service (apport) wrote : This bug is a duplicate

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 #981089, 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.

tags: removed: need-amd64-retrace
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.