Version: 2.12 (using KDE 4.2.2) OS: Linux Installed from: Ubuntu Packages Backtrace follows: =================== Application: Ark (ark), signal SIGSEGV [Current thread is 0 (LWP 21839)] Thread 2 (Thread 0xb4377b90 (LWP 21841)): #0 0xb61650ac in clock_gettime () from /lib/tls/i686/cmov/librt.so.1 #1 0xb6a3406b in ?? () from /usr/lib/libQtCore.so.4 #2 0xb6a34241 in ?? () from /usr/lib/libQtCore.so.4 #3 0xb6a35e2c in ?? () from /usr/lib/libQtCore.so.4 #4 0xb6a3261a in ?? () from /usr/lib/libQtCore.so.4 #5 0xb62019c0 in g_main_context_prepare () from /usr/lib/libglib-2.0.so.0 #6 0xb6201dda in ?? () from /usr/lib/libglib-2.0.so.0 #7 0xb6202268 in g_main_context_iteration () from /usr/lib/libglib-2.0.so.0 #8 0xb6a32457 in QEventDispatcherGlib::processEvents () from /usr/lib/libQtCore.so.4 #9 0xb6a0506a in QEventLoop::processEvents () from /usr/lib/libQtCore.so.4 #10 0xb6a054aa in QEventLoop::exec () from /usr/lib/libQtCore.so.4 #11 0xb690f639 in QThread::exec () from /usr/lib/libQtCore.so.4 #12 0xb7fefdc7 in ?? () from /usr/lib/libkerfuffle.so.4 #13 0xb691296e in ?? () from /usr/lib/libQtCore.so.4 #14 0xb63774ff in start_thread () from /lib/tls/i686/cmov/libpthread.so.0 #15 0xb671849e in clone () from /lib/tls/i686/cmov/libc.so.6 Thread 1 (Thread 0xb5f51700 (LWP 21839)): [KCrash Handler] #6 0xb690d27f in QMutex::unlock () from /usr/lib/libQtCore.so.4 #7 0xb7ff5fd1 in Kerfuffle::Query::setResponse () from /usr/lib/libkerfuffle.so.4 #8 0xb7ff6b66 in Kerfuffle::OverwriteQuery::execute () from /usr/lib/libkerfuffle.so.4 #9 0xb48d0f30 in ?? () from /usr/lib/kde4/libarkpart.so #10 0xb48c2217 in ?? () from /usr/lib/kde4/libarkpart.so #11 0xb6a158fb in QMetaCallEvent::placeMetaCall () from /usr/lib/libQtCore.so.4 #12 0xb6a173a0 in QObject::event () from /usr/lib/libQtCore.so.4 #13 0xb6ed7e9c in QApplicationPrivate::notify_helper () from /usr/lib/libQtGui.so.4 #14 0xb6ee019e in QApplication::notify () from /usr/lib/libQtGui.so.4 #15 0xb7afb94d in KApplication::notify () from /usr/lib/libkdeui.so.5 #16 0xb6a06a3b in QCoreApplication::notifyInternal () from /usr/lib/libQtCore.so.4 #17 0xb6a07695 in QCoreApplicationPrivate::sendPostedEvents () from /usr/lib/libQtCore.so.4 #18 0xb6a0788d in QCoreApplication::sendPostedEvents () from /usr/lib/libQtCore.so.4 #19 0xb6a327ef in ?? () from /usr/lib/libQtCore.so.4 #20 0xb61feb88 in g_main_context_dispatch () from /usr/lib/libglib-2.0.so.0 #21 0xb62020eb in ?? () from /usr/lib/libglib-2.0.so.0 #22 0xb6202268 in g_main_context_iteration () from /usr/lib/libglib-2.0.so.0 #23 0xb6a32438 in QEventDispatcherGlib::processEvents () from /usr/lib/libQtCore.so.4 #24 0xb6f79365 in ?? () from /usr/lib/libQtGui.so.4 #25 0xb6a0506a in QEventLoop::processEvents () from /usr/lib/libQtCore.so.4 #26 0xb6a054aa in QEventLoop::exec () from /usr/lib/libQtCore.so.4 #27 0xb6a07959 in QCoreApplication::exec () from /usr/lib/libQtCore.so.4 #28 0xb6ed7d17 in QApplication::exec () from /usr/lib/libQtGui.so.4 #29 0x0805231f in _start () ============== This happens when extracting a file tree from a .zip archive onto an existing file tree and requesting to overwrite existing files. I first, selected "Overwrite all" but it treated it as a simple "overwrite", asking about what to do with the very next file. After choosing "Overwrite all" about 4 times it segfaulted. I tried again and the fault occurred after the first "Overwrite all" attempt, providing the above backtrace. I saw some closed reports that mentioned crashing during exit after extracting an archive. I chose to open this task because none of them mentioned failing during overwriting files. Ark is able to extract the archive with no problem if the destination is an empty directory (no overwrites). Expected behavior: In the past, ark has properly overwritten all existing files. I recently upgraded the kernel to 2.6.28-13, but have no idea whether this has any effect or not. I can try to boot into the previous version of the kernel and see if this problem remains.
According to bug 195985 / bug 190192 / bug 173979, this was fixed both on 4.3trunk and 4.2branch. Thanks *** This bug has been marked as a duplicate of bug 173979 ***