shotwell-0.13.1-r2 segfaults with installed gst-plugins-libav-1.1.0_pre20130128 after opening the picture db on (~amd64) unmerging gst-plugins-libav-1.1.0_pre20130128 fixes this problem. Reproducible: Always Steps to Reproduce: 1. start shotwell-0.13.1-r2 with installed media-plugins/gst-plugins-libav-1.1.0_pre20130128 (an existing picture db probably has to exist) Actual Results: shotwell segfaults after opening the db. if you unmerge media-plugins/gst-plugins-libav-1.1.0_pre20130128 shotwell works as it should. To workaround this issue I added a =media-plugins/gst-plugins-meta-1.0-r1 -ffmpeg to my package.use/ to prevent gst-plugins-libav-1.1.0_pre20130128 from being pulled in again
Could you please try to get some meaningfull backtrace (http://www.gentoo.org/proj/en/qa/backtraces.xml)? And could you please run SHOTWELL_LOG=1 shotwell from a terminal and attach ~/.cache/shotwell/shotwell.log
Created attachment 341022 [details] shotwell gdb backtrace thx for interest. gdb backtrace with debugging symbols in media-video/ffmpeg-1.0.5 media-gfx/shotwell-0.13.1-r2 media-plugins/gst-plugins-libav-1.1.0_pre20130128
Created attachment 341024 [details] shotwell log and the log
What happens if media-plugins/gst-plugins-ffmpeg is installed?
(In reply to comment #4) > What happens if media-plugins/gst-plugins-ffmpeg is installed? It is already installed. Uninstalling it doesn't fix the problem. gst-plugins-ffmpeg is for gstreamer-0.10 though and gst-plugins-libav is for gstreamer-1.0.
fyi: still an issue with =gst-plugins-libav-1.1.0_pre20130128 and =media-gfx/shotwell-0.14.0
with todays gstreamer updates (no idea which one fixed it, maybe media-libs/gstreamer-1.0.6 or media-libs/gst-plugins-base-1.0.6 or whatever) this is no longer an issue and (my) shotwell (db) works with media-plugins/gst-plugins-libav-1.1.0_pre20130128 installed. I guess this bug can be closed then...
OKay, thanks for testing. Please reopen if it appears again.