Bug 928741 - Totem crashes when I try to play ogv (ogg)
Summary: Totem crashes when I try to play ogv (ogg)
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Fedora
Classification: Fedora
Component: totem
Version: 19
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Bastien Nocera
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks: F19Blocker, F19FinalBlocker
TreeView+ depends on / blocked
 
Reported: 2013-03-28 11:00 UTC by Petr Schindler
Modified: 2013-05-29 19:03 UTC (History)
12 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2013-05-29 19:03:59 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)

Description Petr Schindler 2013-03-28 11:00:52 UTC
Description of problem:
when I run `totem video.ogv` totem crashes with segmentation fault

Version-Release number of selected component (if applicable):
totem-3.7.93-1
Fedora-19-Alpha-TC2-x86_64-Live-Desktop

How reproducible:
always (tried with two different og* video files)

Steps to Reproduce:
1. in terminal, run `totem video.ogv`
  
Actual results:
Segmentation fault

Expected results:
video is played

Additional info:

Comment 1 Fedora Blocker Bugs Application 2013-03-28 11:05:13 UTC
Proposed as a Blocker for 19-final by Fedora user pschindl using the blocker tracking app because:

 This bug violates criterion:
Menu sanity - the following criteria refer to both a live image and default installed system, and to all release-blocking desktops  -
* All applications listed under the Applications menu or category must withstand a basic functionality test and not crash after a few minutes of normal use.

Comment 2 Jeff Bastian 2013-04-23 19:33:15 UTC
abrt popped up when totem crashed for me and claimed it was tracker-extract that crashed when it tried to read the metadata from the ogg video.  See bug 926352.

Comment 3 Alicja Kario 2013-04-24 15:08:07 UTC
when run with under environment with 
ulimit -c unlimited
the generated core dump has zero size

when run under gdb it generates following backtrace:

Program received signal SIGSEGV, Segmentation fault.
[Switching to Thread 0x7fffabffe700 (LWP 3556)]
0x00007fffab3c454b in th_decode_alloc () from /lib64/libtheoradec.so.1
(gdb) bt
#0  0x00007fffab3c454b in th_decode_alloc () from /lib64/libtheoradec.so.1
#1  0x00007fffbc18c3ab in theora_dec_decode_buffer () from /usr/lib64/gstreamer-1.0/libgsttheora.so
#2  0x00007fffbc18c7b8 in theora_dec_handle_frame () from /usr/lib64/gstreamer-1.0/libgsttheora.so
#3  0x00007ffff6b791d6 in gst_video_decoder_decode_frame () from /lib64/libgstvideo-1.0.so.0
#4  0x00007ffff6b7e8db in gst_video_decoder_have_frame () from /lib64/libgstvideo-1.0.so.0
#5  0x00007ffff6b7950a in gst_video_decoder_chain_forward () from /lib64/libgstvideo-1.0.so.0
#6  0x00007ffff6b7b407 in gst_video_decoder_chain () from /lib64/libgstvideo-1.0.so.0
#7  0x00007ffff645fe1a in gst_pad_push_data () from /lib64/libgstreamer-1.0.so.0
#8  0x00007fffd482f461 in gst_multi_queue_loop () from /usr/lib64/gstreamer-1.0/libgstcoreelements.so
#9  0x00007ffff648c899 in gst_task_func () from /lib64/libgstreamer-1.0.so.0
#10 0x00007ffff1c64c56 in g_thread_pool_thread_proxy () from /lib64/libglib-2.0.so.0
#11 0x00007ffff1c64295 in g_thread_proxy () from /lib64/libglib-2.0.so.0
#12 0x00007ffff19e3c53 in start_thread () from /lib64/libpthread.so.0
#13 0x00007ffff1710ecd in clone () from /lib64/libc.so.6

Comment 4 Matthias Clasen 2013-05-15 00:12:04 UTC
totem http://upload.wikimedia.org/wikipedia/commons/6/65/Examplevideo.ogv

works fine here, with totem-3.8.2-1.fc19.x86_64 and tracker-0.16.1-1.fc19.x86_64

Comment 5 Vojtěch Boček 2013-05-24 10:23:35 UTC
Works okay with totem-3.8.2-1.fc19.x86_64, using testing video from #4.

Comment 6 Adam Williamson 2013-05-29 19:03:59 UTC
I played an ogv with totem just today and it worked okay too. So we have multiple tests indicating it's working OK with current stable totem: let's close this, please re-open *and attach the problem video* (assuming no copyright issues) if you're still seeing this. thanks!


Note You need to log in before you can comment on or make changes to this bug.