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

Bug #763798 reported by Chealdo Ortiga
38
This bug affects 5 people
Affects Status Importance Assigned to Milestone
totem (Ubuntu)
Fix Released
Medium
Unassigned

Bug Description

Binary package hint: totem

just watching some video with totem plugins suddenly it pops...

ProblemType: Crash
DistroRelease: Ubuntu 11.04
Package: totem 2.32.0-0ubuntu10
ProcVersionSignature: Ubuntu 2.6.38-8.42-generic 2.6.38.2
Uname: Linux 2.6.38-8-generic i686
Architecture: i386
Date: Mon Apr 18 01:27:23 2011
ExecutablePath: /usr/lib/totem/totem-plugin-viewer
InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Beta i386 (20110413)
ProcCmdline: /usr/lib/totem/totem-plugin-viewer --plugin-type gmp --user-agent Windows-Media-Player/10.00.00.4019 --referrer http://www.liveleak.com/view?i=9f6_1291549881 --mimetype video/x-msvideo --statusbar
ProcEnviron:
 LANGUAGE=en_PH:en
 LANG=en_PH.UTF-8
 SHELL=/bin/bash
SegvAnalysis:
 Segfault happened at: 0x1d72c4: mov 0x8(%eax),%eax
 PC (0x001d72c4) 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
StacktraceTop:
 ?? ()
 g_cclosure_marshal_VOID__VOID () from /usr/lib/i386-linux-gnu/libgobject-2.0.so.0
 g_closure_invoke () from /usr/lib/i386-linux-gnu/libgobject-2.0.so.0
 ?? () from /usr/lib/i386-linux-gnu/libgobject-2.0.so.0
 g_signal_emit_valist () from /usr/lib/i386-linux-gnu/libgobject-2.0.so.0
Title: totem-plugin-viewer crashed with SIGSEGV in g_cclosure_marshal_VOID__VOID()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare

Revision history for this message
Chealdo Ortiga (scriptwarlock) wrote :
Revision history for this message
Apport retracing service (apport) wrote :

StacktraceTop:
 totem_embedded_play (emb=0x211cd800, error=<value optimized out>) at totem-plugin-viewer.c:479
 g_cclosure_marshal_VOID__VOID (closure=0x212ad1b0, return_value=0x0, n_param_values=1, param_values=0x21293318, invocation_hint=0xbfb544a0, marshal_data=0x0) at /build/buildd/glib2.0-2.28.5/./gobject/gmarshal.c:79
 g_closure_invoke (closure=0x212ad1b0, return_value=0x0, n_param_values=1, param_values=0x21293318, invocation_hint=0xbfb544a0) at /build/buildd/glib2.0-2.28.5/./gobject/gclosure.c:767
 signal_emit_unlocked_R (node=0x20fe59a8, detail=0, instance=0x21111360, emission_return=0x0, instance_and_params=0x21293318) at /build/buildd/glib2.0-2.28.5/./gobject/gsignal.c:3252
 g_signal_emit_valist (instance=0x21111360, signal_id=105, detail=0, var_args=0xbfb5465c "|\r\212") at /build/buildd/glib2.0-2.28.5/./gobject/gsignal.c:2983

Revision history for this message
Apport retracing service (apport) wrote : Stacktrace.txt
Revision history for this message
Apport retracing service (apport) wrote : ThreadStacktrace.txt
Changed in totem (Ubuntu):
importance: Undecided → Medium
tags: removed: need-i386-retrace
Victor Vargas (kamus)
visibility: private → public
Revision history for this message
Victor Vargas (kamus) wrote :

I tried to reproduce this issue with a full updated Ubuntu Natty Narwhal system but it doesn't crash for me, however, I am not able to reproduce that stream which I reckon is another problem. Please could you check again if this problem is still affecting you with a fully updated system?

Changed in totem (Ubuntu):
status: New → Incomplete
Revision history for this message
Launchpad Janitor (janitor) wrote :

[Expired for totem (Ubuntu) because there has been no activity for 60 days.]

Changed in totem (Ubuntu):
status: Incomplete → Expired
Revision history for this message
Don Forigua (ingforigua) wrote :

I have this bug today on oneirc here is my bug report https://bugs.launchpad.net/bugs/862852

Changed in totem (Ubuntu):
status: Expired → New
Revision history for this message
Launchpad Janitor (janitor) wrote :

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in totem (Ubuntu):
status: New → Confirmed
Revision history for this message
Fabio Marconi (fabiomarconi) wrote :

while your symptoms sound similar, you're likely experiencing an unrelated issue. Please file a new bug for it using the command 'ubuntu-bug totem' (and a photo if any corruption is seen).

Changed in totem (Ubuntu):
status: Confirmed → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Duplicates of this bug

Other bug subscribers

Remote bug watches

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