Version: 1.0.5 (using KDE 4.1.3) Compiler: gcc version 4.3.2 20081105 (Red Hat 4.3.2-7) (GCC) OS: Linux Installed from: Fedora RPMs A Fatal Error Occurred The application unknown (k3b) crashed and caused the signal 11 (SIGSEGV). Steps to reproduce: launch k3b from the kicker menu, wait for the splash screen to disappear and for the timed "No problems found in system configuration." message to go away, then exit k3b: the crash happens by choosing File/Quit from the menu, or by closing the window from the standard control at the top right corner (either way). The backtraces mention libselinux.so.1 which is temporarily disabled in /etc/selinux/config: #SELINUX=enforcing SELINUX=disabled SELINUXTYPE=targeted System config: Fedora: 10 (final) kernel: 2.6.27.5-117.fc10.x86_64 KDE: 4.1.3 k3b: 1.0.5 libselinux-2.0.73-1.fc10.src.rpm Logs with debug packages installed... From Kcrash: Application: unknown (k3b), signal SIGSEGV [Thread debugging using libthread_db enabled] [New Thread 0x7fb80f444750 (LWP 6609)] [KCrash handler] #5 0x00007fb80655d57d in fini_context_translations () at setrans_client.c:217 #6 0x00007fb80654ffef in __do_global_dtors_aux () from /lib64/libselinux.so.1 #7 0x000000000044e7b0 in K3bDoc::URL () #8 0x00007fff1747a9d0 in ?? () #9 0x00007fb80655f0f1 in _fini () from /lib64/libselinux.so.1 #10 0x00007fff1747a9d0 in ?? () #11 0x0000003ac5e0f1d4 in _dl_fini () at dl-fini.c:248 Backtrace stopped: previous frame inner to this frame (corrupt stack?) From valgrind backtrace: ==6514== Invalid read of size 8 ==6514== at 0xF1AF57D: fini_context_translations (setrans_client.c:217) ==6514== by 0xF1A1FEE: (within /lib64/libselinux.so.1) ==6514== by 0xF1B10F0: (within /lib64/libselinux.so.1) ==6514== by 0x3AC723656C: exit (exit.c:75) ==6514== by 0x3AC721E54C: (below main) (libc-start.c:252) ==6514== Address 0x78 is not stack'd, malloc'd or (recently) free'd
Created attachment 28936 [details] full kcrash and valgrind backtraces
See also downstream report: https://bugzilla.rpmfusion.org/show_bug.cgi?id=213 As far as we can tell atm, it's some sort of interaction between k3b's ffmpeg support and selinux (perhaps leaked file descriptors).
In an attempt to clean up old bugs that are not valid for K3b 2.0 (=KDE SC 4.x port) anymore, this is now being marked as UNMAINTAINED. If this bug is still valid for 2.0, please reopen it.