totem crashed with SIGSEGV in submit_packet() while playing vide

Bug #1346188 reported by Wade Menard
14
This bug affects 2 people
Affects Status Importance Assigned to Milestone
totem (Ubuntu)
Expired
Medium
Unassigned

Bug Description

While playing an RMVB video, totem crashed.

ProblemType: Crash
DistroRelease: Ubuntu 14.10
Package: totem 3.10.1-1ubuntu6
ProcVersionSignature: Ubuntu 3.16.0-4.9-generic 3.16.0-rc5
Uname: Linux 3.16.0-4-generic x86_64
ApportVersion: 2.14.4-0ubuntu2
Architecture: amd64
CurrentDesktop: Unity
Date: Mon Jul 21 06:30:53 2014
ExecutablePath: /usr/bin/totem
InstallationDate: Installed on 2014-07-04 (17 days ago)
InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Alpha amd64 (20140520)
ProcCmdline: totem /storage/username/Videos/coco/MUM-116/MUM-116.rmvb
ProcEnviron:
 LANGUAGE=en_US
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=<set>
 LANG=en_US.UTF-8
 SHELL=/bin/bash
Signal: 11
SourcePackage: totem
StacktraceTop:
 ?? () from /usr/lib/x86_64-linux-gnu/libavcodec.so.54
 avcodec_decode_video2 () from /usr/lib/x86_64-linux-gnu/libavcodec.so.54
 ?? () from /usr/lib/x86_64-linux-gnu/gstreamer-1.0/libgstlibav.so
 ?? () from /usr/lib/x86_64-linux-gnu/gstreamer-1.0/libgstlibav.so
 ?? () from /usr/lib/x86_64-linux-gnu/gstreamer-1.0/libgstlibav.so
Title: totem crashed with SIGSEGV in avcodec_decode_video2()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm audio cdrom dip lpadmin plugdev pulse pulse-access sambashare sudo vboxusers

Revision history for this message
Wade Menard (wade-ezri) wrote :
information type: Private → Public
Revision history for this message
Apport retracing service (apport) wrote :

StacktraceTop:
 submit_packet (avpkt=0x7fbfa37fc1e0, p=0x7fbf8c0061c8) at /build/buildd/libav-9.11/libavcodec/pthread.c:573
 ff_thread_decode_frame (avctx=0x7fbf9804ea60, picture=0x7fbf98053140, got_picture_ptr=0x7fbfa37fc1dc, avpkt=0x7fbfa37fc1e0) at /build/buildd/libav-9.11/libavcodec/pthread.c:609
 avcodec_decode_video2 (avctx=0x7fbf9804ea60, picture=0x7fbf98053140, got_picture_ptr=got_picture_ptr@entry=0x7fbfa37fc1dc, avpkt=avpkt@entry=0x7fbfa37fc1e0) at /build/buildd/libav-9.11/libavcodec/utils.c:1301
 gst_ffmpegviddec_video_frame (ffmpegdec=ffmpegdec@entry=0x7fbf9804c1f0, data=<optimized out>, data@entry=0x7fbf8ce89a10 "\030\001", size=29993, frame=frame@entry=0x7fbf980885e0, ret=ret@entry=0x7fbfa37fc6ac) at gstavviddec.c:1210
 gst_ffmpegviddec_frame (ffmpegdec=ffmpegdec@entry=0x7fbf9804c1f0, data=data@entry=0x7fbf8ce89a10 "\030\001", size=size@entry=29993, got_data=got_data@entry=0x7fbfa37fc6a8, frame=frame@entry=0x7fbf980885e0, ret=ret@entry=0x7fbfa37fc6ac) at gstavviddec.c:1384

Revision history for this message
Apport retracing service (apport) wrote : Stacktrace.txt
Revision history for this message
Apport retracing service (apport) wrote : StacktraceSource.txt
Revision history for this message
Apport retracing service (apport) wrote : ThreadStacktrace.txt
Changed in totem (Ubuntu):
importance: Undecided → Medium
summary: - totem crashed with SIGSEGV in avcodec_decode_video2() while playing vide
+ totem crashed with SIGSEGV in submit_packet() while playing vide
tags: removed: need-amd64-retrace
Revision history for this message
Carlos Luna (caralu1974) wrote :

I have the same trouble, when I try to open a .rmvb file, totem starts but immediately crash. The apport daemon has been sending this report continuously ( and automatically)

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
Carlos Luna (caralu1974) wrote :

I only could have this:

totem --debug Video.rmvb

(totem:5230): GStreamer-CRITICAL **: gst_structure_new_empty: assertion 'gst_structure_validate_name (name)' failed
Violación de segmento (`core' generado)

Revision history for this message
Carlos Luna (caralu1974) wrote :

This is the crash report

Revision history for this message
Paul White (paulw2u) wrote :

We are sorry that we do not always have the capacity to review all reported bugs in a timely manner.

Ubuntu 14.10 (utopic) reached end-of-life on July 23, 2015.

Do you still see a problem related to the one that you reported in a currently supported version of Ubuntu? Please let us know if you do and in which version of Ubuntu otherwise this report can be left to expire in approximately 60 days time.

Thank you for helping make Ubuntu better.

Paul White
[Ubuntu Bug Squad]

Changed in totem (Ubuntu):
status: Confirmed → 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
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.