On 4/27/06, Florin Andrei <florin@xxxxxxxxxxxxxxx> wrote:
On Sat, 2006-04-22 at 16:13 -0400, Mike Chalmers wrote: > Kino experienced a segmentation fault. > Dumping stack from the offending thread This seems similar to the way it used to crash on my system, before it got mysteriously fixed recently. There is an easy way to find out if SELinux is the culprit. yum install audit reboot tail -f /var/log/audit/audit.log Prepare everything to crash Kino, but stop short of doing that final single step that makes Kino crash. Hit Enter a couple times in the terminal running tail -f Now do whatever you used to do to crash Kino. After it crashed, hit CTRL-C in the window running tail -f If there are new lines displayed by tail -f when Kino crashed, it's likely they were generated by Kino as a violation of some SELinux policy or flag. Copy those lines and paste them in a reply to this message to the mailing list. -- Florin Andrei http://florin.myip.org/ -- fedora-list mailing list fedora-list@xxxxxxxxxx To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list
Hi, I will try disabling SE Linux and let you know what happened. How do I disable SE Linux? My camera is connected to the computer using a firewire and it takes mini dv tapes. "Until very recently, kino-0.8.0-2.lvn5 used to crash on my FC5 system when opening an existing avi-encapsulated (opendml) DV file captured with dvgrab." This happened to me also. The second I click on the avi file captured by dvgrab Kino immediately closes. "There is an easy way to find out if SELinux is the culprit." What exactly am I doing when I run the commands you listed. Am I disabling SE Linux? Thanks, Mike
