Mike Chalmers <mikechalmers70 <at> gmail.com> writes: > Kino experienced a segmentation fault. > Dumping stack from the offending thread > > Obtained 10 stack frames. > kino [0x8070d38] > [0x493420] > /usr/lib/libavcodec.so.51(avcodec_default_execute+0x18) [0xda8948] This is the Kino lead developer. We are receiving a bunch of bug reports from FC5 users (and only FC5 users) just like this. I do not use FC5 and can not reproduce it. One user reported disabling SELinux worked for him. I would like to know if this workaround works for others as well. Please send email to dan@xxxxxxxxxxx if it did. Also, for a Red Hat developer, if this workaround is the case, what does that mean? Is SELinux detecting some memory violation in ffmpeg/libavcodec?
