totem crashed with SIGSEGV

Bug #545220 reported by TVC15
12
This bug affects 1 person
Affects Status Importance Assigned to Milestone
gst-plugins-base
Expired
Critical
gst-plugins-base0.10 (Ubuntu)
Invalid
Medium
Unassigned

Bug Description

Binary package hint: totem

I opened a folder with mp3 files by right-clicking and choosing "Open with" -> Movie player.
After a few songs Totem first stopped playing, then quit completely.

ProblemType: Crash
Architecture: i386
Date: Tue Mar 23 17:41:33 2010
DistroRelease: Ubuntu 10.04
ExecutablePath: /usr/bin/totem
Package: totem 2.29.92-0ubuntu3
ProcCmdline: totem /home/username/Music/Cranberries
ProcEnviron:
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcVersionSignature: Ubuntu 2.6.32-16.25-generic
SegvAnalysis:
 Segfault happened at: 0x8d42c6c: mov 0x3c(%eax),%edx
 PC (0x08d42c6c) ok
 source "0x3c(%eax)" (0x0000003c) not located in a known VMA region (needed readable region)!
 destination "%edx" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: totem
StacktraceTop:
 ?? () from /usr/lib/gstreamer-0.10/libgstximagesink.so
 ?? () from /usr/lib/gstreamer-0.10/libgstximagesink.so
 ?? () from /usr/lib/libgstbase-0.10.so.0
 ?? () from /usr/lib/libgstreamer-0.10.so.0
 ?? () from /usr/lib/libgstreamer-0.10.so.0
Title: totem crashed with SIGSEGV
Uname: Linux 2.6.32-16-generic i686
UserGroups: adm admin cdrom dialout lpadmin netdev plugdev sambashare
XsessionErrors: (polkit-gnome-authentication-agent-1:2044): GLib-CRITICAL **: g_once_init_leave: assertion `initialization_value != 0' failed

Revision history for this message
TVC15 (johan-vanhoren) wrote :
Revision history for this message
Apport retracing service (apport) wrote :

StacktraceTop:
 gst_ximagesink_ximage_new (ximagesink=0x9c88aa0,
 gst_ximagesink_buffer_alloc (bsink=0x9c88aa0,
 gst_base_sink_pad_buffer_alloc (pad=0x9c80008,
 gst_pad_alloc_buffer_full (pad=0x9c7cb68,
 gst_proxy_pad_do_bufferalloc (pad=0xae51a010,

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
Revision history for this message
Pedro Villavicencio (pedro) wrote :

the backtrace is good and it looks like a gst-plugins-base crash, reassigning and will send it upstream.

visibility: private → public
affects: totem (Ubuntu) → gst-plugins-base0.10 (Ubuntu)
Revision history for this message
Pedro Villavicencio (pedro) wrote :

Thank you for your bug report. This bug has been reported to the developers of the software. You can track it and make comments at:
 https://bugzilla.gnome.org/show_bug.cgi?id=615851

Changed in gst-plugins-base0.10 (Ubuntu):
status: New → Triaged
Changed in gst-plugins-base:
status: Unknown → New
Changed in gst-plugins-base:
status: New → Incomplete
Revision history for this message
Pedro Villavicencio (pedro) wrote :

this should be fixed with commit http://cgit.freedesktop.org/gstreamer/gst-plugins-base/commit/?id=df5c772c44ef798b5d4b56b4b860f064e61ae243 which is already included in Maverick package, may you please test and comment back? Thanks in advance.

Changed in gst-plugins-base0.10 (Ubuntu):
status: Triaged → Incomplete
Revision history for this message
Pedro Villavicencio (pedro) wrote :

We are closing this bug report because it lacks the information we need to investigate the problem, as described in the previous comments. Please reopen it if you can give us the missing information, and don't hesitate to submit bug reports in the future. To reopen the bug report you can click on the current status, under the Status column, and change the Status back to New. Thanks again!.

Changed in gst-plugins-base:
status: Incomplete → Invalid
Changed in gst-plugins-base0.10 (Ubuntu):
status: Incomplete → Invalid
Changed in gst-plugins-base:
status: Invalid → Fix Released
Changed in gst-plugins-base:
status: Fix Released → Invalid
Changed in gst-plugins-base:
importance: Unknown → Critical
status: Invalid → Expired
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.