Bug 1369893

The crash generated lot of files in two directories in /var/spool/abrt/, ccpp-2016-08-24-13:06:27-3672 and Python3-2016-08-24-16:19:19-6782. Which files are relevant for debugging this bug?

Ignore Python3-2016-08-24-16:19:19-6782 in Comment 1. It has nothing to do with this bug :-(

I have now tested shotwell on other of my machines where it DOES NOT crash.

Both are Fedora 24 with kernel 4.6.7-300.fc24.x86_64 and updated to day.
The one that shotwell is crashing on is  AMD Athlon(tm) 64 X2 Dual Core Processor 4800+ while the other is AMD Athlon(tm) 64 Dual Core Processor 5200B

I'm also seeing this segfault on Fedora 24 (4.6.7-300.fc24.x86_64) with an Intel processor (Intel(R) Core(TM) i7-4790), FWIW.

I ran a backtrace as follows,

SHOTWELL_LOG=1 gdb shotwell 2>&1 | tee shotwell.gdb
(gdb) run
(gdb) backtrace full
#0  0x00007fff907c3930 in av_fifo_reset () at /lib64/libavutil.so.55
#1  0x00007fff90e4a2e0 in ff_qsv_decode_reset () at /lib64/libavcodec.so.57
#2  0x00007fff90ee04c5 in avcodec_flush_buffers () at /lib64/libavcodec.so.57
#3  0x00007fff925decab in gst_ffmpegviddec_finish () at /usr/lib64/gstreamer-1.0/libgstlibav.so
#4  0x00007fffee769704 in gst_video_decoder_drain_out () at /lib64/libgstvideo-1.0.so.0
#5  0x00007fffee76f435 in gst_video_decoder_sink_event_default () at /lib64/libgstvideo-1.0.so.0
#6  0x00007ffff6f94417 in gst_pad_send_event_unchecked () at /lib64/libgstreamer-1.0.so.0
#7  0x00007ffff6f948de in gst_pad_push_event_unchecked () at /lib64/libgstreamer-1.0.so.0
#8  0x00007ffff6f94cf0 in push_sticky () at /lib64/libgstreamer-1.0.so.0
#9  0x00007ffff6f9299f in events_foreach () at /lib64/libgstreamer-1.0.so.0
#10 0x00007ffff6f9eb41 in gst_pad_push_event () at /lib64/libgstreamer-1.0.so.0
#11 0x00007ffff74a0f6f in gst_base_parse_sink_event_default () at /lib64/libgstbase-1.0.so.0
#12 0x00007ffff6f94417 in gst_pad_send_event_unchecked () at /lib64/libgstreamer-1.0.so.0
#13 0x00007ffff6f948de in gst_pad_push_event_unchecked () at /lib64/libgstreamer-1.0.so.0
#14 0x00007ffff6f94cf0 in push_sticky () at /lib64/libgstreamer-1.0.so.0
#15 0x00007ffff6f9299f in events_foreach () at /lib64/libgstreamer-1.0.so.0
#16 0x00007ffff6f9eb41 in gst_pad_push_event () at /lib64/libgstreamer-1.0.so.0
#17 0x00007fffc162c717 in gst_multi_queue_loop () at /usr/lib64/gstreamer-1.0/libgstcoreelements.so
#18 0x00007ffff6fc81b1 in gst_task_func () at /lib64/libgstreamer-1.0.so.0
#19 0x00007ffff03006ee in g_thread_pool_thread_proxy () at /lib64/libglib-2.0.so.0
#20 0x00007ffff02ffcf5 in g_thread_proxy () at /lib64/libglib-2.0.so.0
#21 0x00007fffefe4d5ca in start_thread () at /lib64/libpthread.so.0
#22 0x00007fffefb86f6d in clone () at /lib64/libc.so.6

I moved this library out of the way and managed to start shotwell, albeit without video thumbnails, apparently,

cd /usr/lib64
sudo mkdir foo
sudo mv libavutil.so.55* foo

after starting shotwell I see the following messages at the console,

(shotwell-video-thumbnailer:16461): GStreamer-WARNING **: Failed to load plugin '/usr/lib64/gstreamer-1.0/libgstlibav.so': libavutil.so.55: cannot open shared object file: No such file or directory

repeated many many times.

The issue was solved in my case by just removing gstreamer1-libav.

e.g.


# dnf remove gstreamer1-libav-1.8.3-1.fc24.x86_64

(In reply to Kapoios Kanenas from comment #6)
> The issue was solved in my case by just removing gstreamer1-libav.
> 
> e.g.
> 
> 
> # dnf remove gstreamer1-libav-1.8.3-1.fc24.x86_64

This seems to have solve the problem, but I have to see if it affect handbrake since it was installed from the handbrake repo.

FYI, 

I've got the same issue and removing gstreamer1-libav also solved the problem.

The application does not crash anymore but I've got the following warning message in the console:

Failed to play the file: couldn't get state

This message is a reminder that Fedora 24 is nearing its end of life.
Approximately 2 (two) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 24. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as EOL if it remains open with a Fedora  'version'
of '24'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version'
to a later Fedora version.

Thank you for reporting this issue and we are sorry that we were not
able to fix it before Fedora 24 is end of life. If you would still like
to see this bug fixed and are able to reproduce it against a later version
of Fedora, you are encouraged  change the 'version' to a later Fedora
version prior this bug is closed as described in the policy above.

Although we aim to fix as many bugs as possible during every release's
lifetime, sometimes those efforts are overtaken by events. Often a
more recent Fedora release includes newer upstream software that fixes
bugs or makes them obsolete.

Fedora 24 changed to end-of-life (EOL) status on 2017-08-08. Fedora 24 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this
bug.

Thank you for reporting this bug and we are sorry it could not be fixed.