After upgrading ffmpeg from 0.7.1 to 0.7.2, every time I hover the mouse cursor over a video file in dolphin-4.7.0 file manager, I get a KDE crash report that kfilemetadatareader has segfaulted. Kfilemetadatareader seems to be a new strigi frontend in KDE-4.7.0, so it may be that it's actually strigi that is crashing, I'm not quite sure... Video preview in dolphin is enabled, and I use ffmpegthumbs for thumbnails. I've tried recompiling kdelibs-4.7.0 (of which the kfilemetadatareader is part), ffmpegthumbs-4.7.0 and strigi-0.7.5-r1, no luck there, *only* downgrading back to ffmpeg-0.7.1 helps.
Created attachment 281683 [details] emerge --info
Can you see anything of you launch dolphin and so on from shell?
Please try running emerge @preserved-rebuild or revdep-rebuild and see if it wants to reinstall any KDE application.
KDE crash report should already tell where the problem is (it dumps backtrace). Take a look at backtrace and rebuild affected package with build symbols (kdelibs, strigi and maybe some thumbnailer should be sufficient) To set per-package CFLAGS you can use /etc/portage/env feature: http://git.overlays.gentoo.org/gitweb/?p=proj/kde.git;a=tree;f=Documentation/env;hb=master First I'd try disabling ffmpeg thumbnails...
"rebuild affected package with build symbols" should be: "rebuild affected package with *debug* symbols" Anyway this step is optional, if you're unable to identify root cause.
Ok, sorry for the longish delay... First, strigi-0.7.5-r2 didn't - initially - work any better, still crashed. But see below... Just finished rebuilding kdelibs, ffmpegthumbs ans strigi with -ggdb and FEATURES="nostrip" -> Dolphin output in terminal: QPixmap::scaled: Pixmap is a null pixmap [mov,mp4,m4a,3gp,3g2,mj2 @ 0x7df500] moov atom not found KCrash: Application 'mailendanalyzer' crashing... KCrash: Attempting to start /usr/lib64/kde4/libexec/drkonqi from kdeinit QLayout: Attempting to add QLayout "" to PhononWidget "", which already has a layout [mov,mp4,m4a,3gp,3g2,mj2 @ 0x7df500] moov atom not found KCrash: Application 'mailendanalyzer' crashing... KCrash: Attempting to start /usr/lib64/kde4/libexec/drkonqi from kdeinit QProcess: Destroyed while process is still running. QProcess: Destroyed while process is still running. Output of KDE Crash Handler: Application: (kfilemetadatareader), signal: Segmentation fault [KCrash Handler] #6 av_open_input_stream (ic_ptr=0x7fff91d19238, pb=0x7fff91d19000, filename=0x7f3fc68f3dd2 "", fmt=<value optimized out>, ap=<value optimized out>) at libavformat/utils.c:543 #7 0x00007f3fc68f2942 in FFMPEGEndAnalyzer::analyze (this=0x6d7bf0, ar=..., in=0x7be6b0) at /var/tmp/portage/app-misc/strigi-0.7.5-r2/work/strigi-0.7.5/libstreamanalyzer/plugins/endplugins/ffmpegendanalyzer.cpp:328 #8 0x00007f3fd8508427 in Strigi::StreamAnalyzerPrivate::analyze (this=0x6e6450, idx=..., input=0x7be6b0) at /var/tmp/portage/app-misc/strigi-0.7.5-r2/work/strigi-0.7.5/libstreamanalyzer/lib/streamanalyzer.cpp:420 #9 0x00007f3fdaef5953 in KFileMetaInfoPrivate::init (this=<value optimized out>, stream=<value optimized out>, url=<value optimized out>, mtime=1299182439, w=<value optimized out>) at /var/tmp/portage/kde-base/kdelibs-4.7.0/work/kdelibs-4.7.0/kio/kio/kfilemetainfo.cpp:259 #10 0x00007f3fdaef74b0 in KFileMetaInfo::KFileMetaInfo (this=0x7fff91d19650, path=..., w=<value optimized out>) at /var/tmp/portage/kde-base/kdelibs-4.7.0/work/kdelibs-4.7.0/kio/kio/kfilemetainfo.cpp:288 #11 0x00000000004031ae in readFileMetaData (urls=<value optimized out>) at /var/tmp/portage/kde-base/kdelibs-4.7.0/work/kdelibs-4.7.0/kio/kfile/kfilemetadatareaderprocess.cpp:85 #12 0x0000000000403e9c in readFileAndContextMetaData (urls=<value optimized out>) at /var/tmp/portage/kde-base/kdelibs-4.7.0/work/kdelibs-4.7.0/kio/kfile/kfilemetadatareaderprocess.cpp:146 #13 0x000000000040509e in main (argc=<value optimized out>, argv=<value optimized out>) at /var/tmp/portage/kde-base/kdelibs-4.7.0/work/kdelibs-4.7.0/kio/kfile/kfilemetadatareaderprocess.cpp:195 And now comes the fun part: the crashing 'mailendanalyzer' got me thinking. I have just the minimal setup of kdepim libs, installed as a dependency. At some point in the past I anyway installed kde-base/kdepim-strigi-analyzer, and just for testing purposes I removed it now, and - you don't believe this - the crashes disappeared! And after reinstalling kdepim-strigi-analyzer the crashes started again!! WTF kdepim-strigi-analyzer has to do with video files??? And why does it crash only with ffmpeg-0.7.2??? Beats me...
Here's more fun: While the removal of kdepim-strigi-analyzer allowed dolphin to resume its normal operation, I still get reports of kfilemetadatareader segfaults in kernel logs EVERY time I hover the mouse cursor over some video file: Aug 6 10:42:32 wintermute kernel: kfilemetadatare[19035]: segfault at 20 ip 00007f3afc367aa9 sp 00007fff1c4cfdd0 error 4 in libavformat.so.52.110.0[7f3afc2d5000+c0000] Aug 6 10:42:32 wintermute kernel: kfilemetadatare[19037]: segfault at 20 ip 00007fec12282aa9 sp 00007fff349524e0 error 4 in libavformat.so.52.110.0[7fec121f0000+c0000] Aug 6 10:58:24 wintermute kernel: kfilemetadatare[19631]: segfault at 20 ip 00007f23577baaa9 sp 00007fff2cba4cc0 error 4 in libavformat.so.52.110.0[7f2357728000+c0000] Aug 6 10:58:24 wintermute kernel: kfilemetadatare[19634]: segfault at 20 ip 00007f75debc2aa9 sp 00007fff7cfca430 error 4 in libavformat.so.52.110.0[7f75deb30000+c0000] This happens if strigi is compiled with ffmpeg-0.7.2. If I downgrade to ffmpeg-0.7.1 or recompile strigi with ffmpeg support disabled, the segfaults disappear.
Seems that strigi-0.7.6 finally fixed this issue, no more segfaults on any ffmpeg-0.7.x version. As far as I'm concerned you can close this bug.
(In reply to comment #8) > Seems that strigi-0.7.6 finally fixed this issue, no more segfaults on any > ffmpeg-0.7.x version. As far as I'm concerned you can close this bug. OK great. Unintended side effect... :) I've bumped the dependency in kdelibs to require >=0.7.6 now.
