totem-gstreamer crashed with SIGSEGV

Bug #335595 reported by terry_gardener

This bug report was converted into a question: question #63621: totem-gstreamer crashed with SIGSEGV.

22
This bug affects 2 people
Affects Status Importance Assigned to Milestone
ffmpeg-debian (Ubuntu)
Invalid
Medium
Unassigned
totem (Ubuntu)
Invalid
Undecided
Unassigned

Bug Description

Binary package hint: totem

please link this to my previous bug report (Bug 334519) that i have been advised to raise a new one.

i have updated my system less than 1 hr ago using the update manager and it says that my system is up to date, so all packages are up to date as of now while posting this bug.

the .mkv files work with mplayer and vlc just not in totem.

also i have uploaded a sample file online at http://homepage.ntlworld.com/terry.gardener/test.mkv

i am still getting exactly the same issue and after reading the forums i am not the only one.

description from previous bug report
unable to play .mkv files they are crashing totem. nautilus crashes when
i try to access the properties of the file.

i have posted my problem here
http://ubuntuforums.org/showthread.php?t=1078269

it works in VLC and mplayer but not totem.

codecs of the video file (info from vlc)
video = avc1
audio = mpga

i have also looked at syslogs and it says the following

terry-desktop kernel: [ 68.576720] totem[4085]: segfault at ab36000 ip b7105377 sp b310a828 error 6 in libc-2.9.so[b708c000+15c000]
terry-desktop kernel: [ 122.168247] nautilus[4135]: segfault at aac1000 ip b7309377 sp b6be1838 error 6 in libc-2.9.so[b7290000+15c000]

 i have installed the gstreamer good, bad and ugly. bad and ugly also
have the package from the multiverse installed. also have gstreamer-
ffmpeg

ProblemType: Crash
Architecture: i386
CrashCounter: 1
Disassembly: 0xb6fc7377:
DistroRelease: /usr/bin/lsb_release:81: DeprecationWarning: the sets module is deprecated import sets Ubuntu 9.04
ExecutablePath: /usr/bin/totem-gstreamer
NonfreeKernelModules: nvidia
Package: totem-gstreamer 2.25.91-0ubuntu2
ProcCmdline: totem /media/disk/home/username/Videos/cascada-what_hurts_the_most-x264-2007-se_int.mkv
ProcEnviron:
 LANG=en_GB.UTF-8
 SHELL=/bin/bash
Signal: 11
SourcePackage: totem
Stacktrace:
 #0 0xb6fc7377 in ?? ()
 #1 0x80808080 in ?? ()
StacktraceTop:
 ?? ()
 ?? ()
ThreadStacktrace:

Title: totem-gstreamer crashed with SIGSEGV
Uname: Linux 2.6.28-8-generic i686
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare

Revision history for this message
terry_gardener (terry-gardener) wrote :
Revision history for this message
Remco Hijink (r-hijink-deactivatedaccount) wrote :

I can confirm this bug with almost the same setup

Revision history for this message
Apport retracing service (apport) wrote : Symbolic stack trace

StacktraceTop:?? ()
?? ()

Revision history for this message
Apport retracing service (apport) wrote : Crash report cannot be processed

Thank you for your report!

However, processing it in order to get sufficient information for the
developers failed (it does not generate an useful symbolic stack trace). This
might be caused by some outdated packages which were installed on your system
at the time of the report:

libxrandr2: installed version 2:1.2.99.4-1, latest version: 2:1.2.99.4-2
libpam-runtime: installed version 1.0.1-5ubuntu1, latest version: 1.0.1-5ubuntu2
libcups2: installed version 1.3.9-14ubuntu1, latest version: 1.3.9-14ubuntu2
libpam0g: installed version 1.0.1-5ubuntu1, latest version: 1.0.1-5ubuntu2
libpam-modules: installed version 1.0.1-5ubuntu1, latest version: 1.0.1-5ubuntu2
liblaunchpad-integration1: installed version 0.1.22, latest version: 0.1.23
libtheora0: installed version 1.0~beta3-1, latest version: 1.0-2

Please upgrade your system to the latest package versions. If you still
encounter the crash, please file a new report.

Thank you for your understanding, and sorry for the inconvenience!

Changed in totem:
status: New → Invalid
Revision history for this message
terry_gardener (terry-gardener) wrote :

sorry to reopen this bug but if i raise another bug report then with the pace that ubuntu jaunty is getting updated than i is going to be out of date when the you look at it.

i have made sure the packages mentions above are update to date and then retried and get the same problem.

i have done a backtrace and also valgrind as it is segmentation fault. see attachments

Revision history for this message
terry_gardener (terry-gardener) wrote :
Revision history for this message
terry_gardener (terry-gardener) wrote :

changing it back to new as i dont agreed with the status invalid as this is the second bug report submitted after the problem has occured on a updated system twice.

Changed in totem:
status: Invalid → New
Revision history for this message
Sebastien Bacher (seb128) wrote :

the issue is an invalid read in libavcodec but it lacks debug informations

Changed in totem:
importance: Undecided → Medium
Revision history for this message
Sebastien Bacher (seb128) wrote :

could you add a video example to the bug?

Revision history for this message
Pedro Villavicencio (pedro) wrote :

not a totem issue, rejecting the task.

Changed in totem:
status: New → Invalid
Revision history for this message
Remco Hijink (r-hijink-deactivatedaccount) wrote :

A video example is in the bug report: http://homepage.ntlworld.com/terry.gardener/test.mkv

Revision history for this message
Sebastien Bacher (seb128) wrote :

the video doesn't crash on my jaunty installation

Revision history for this message
terry_gardener (terry-gardener) wrote :

please can you advise how to fix my problem then.

for example what packages do i need installed for it not to crash, etc etc

Revision history for this message
Sebastien Bacher (seb128) wrote :

no idea how to fix your issue I just don't get the bug there and so can't work on it

Changed in ffmpeg-debian:
status: New → Invalid
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

Related questions

Remote bug watches

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