Bug 189142

Summary: Ark crashed on unpacking
Product: [Applications] ark Reporter: xcojack <xcojack>
Component: generalAssignee: Harald Hvaal <metellius>
Status: RESOLVED INTENTIONAL    
Severity: crash CC: abhixecutor, rakuco
Priority: NOR    
Version: unspecified   
Target Milestone: ---   
Platform: Arch Linux   
OS: Linux   
Latest Commit: Version Fixed In:
Sentry Crash Report:
Attachments: Logs from crashed.

Description xcojack@gmail.com 2009-04-08 19:01:31 UTC
Version:            (using KDE 4.2.2)
OS:                Linux
Installed from:    Unspecified Linux

When I select from menu unpack here and auto dectect folder, and try to unpack *.rar, gzip, tar, whatever file Ark crashed, backtrace in attechmed file.
Comment 1 xcojack@gmail.com 2009-04-08 19:01:57 UTC
Created attachment 32703 [details]
Logs from crashed.
Comment 2 Raphael Kubo da Costa 2009-04-08 19:07:29 UTC
Please paste the backtrace in the comments or your bug description, it makes easier to find similar bug reports and merge them.

Program: Ark (ark), sygnaƂ SIGSEGV
[Current thread is 0 (LWP 15607)]

Thread 3 (Thread 0xb4899b90 (LWP 15608)):
#0  0xb65a1f0c in clock_gettime () from /lib/librt.so.1
#1  0xb6efdeab in ?? () from /usr/lib/libQtCore.so.4
#2  0x00000001 in ?? ()
#3  0xb48988a8 in ?? ()
#4  0x090ed4e8 in ?? ()
#5  0xb6da1ff4 in ?? () from /usr/lib/libstdc++.so.6
#6  0x00000000 in ?? ()

Thread 2 (Thread 0xb4098b90 (LWP 15609)):
#0  0xb7feb424 in __kernel_vsyscall ()
#1  0xb6c3aab1 in select () from /lib/libc.so.6
#2  0xb6eb70e7 in ?? () from /usr/lib/libQtCore.so.4
#3  0x00000007 in ?? ()
#4  0xb40982a8 in ?? ()
#5  0x00000000 in ?? ()

Thread 1 (Thread 0xb611a700 (LWP 15607)):
[KCrash Handler]
#6  0xb6e32eec in QString::indexOf () from /usr/lib/libQtCore.so.4
#7  0xb48d120c in RARInterface::processListLine () from /usr/lib/kde4/kerfuffle_rar.so
#8  0xb48d2c6e in RARInterface::readStdout () from /usr/lib/kde4/kerfuffle_rar.so
#9  0xb48cd5bb in RARInterface::qt_metacall () from /usr/lib/kde4/kerfuffle_rar.so
#10 0xb6ee238b in QMetaCallEvent::placeMetaCall () from /usr/lib/libQtCore.so.4
#11 0xb6ee4120 in QObject::event () from /usr/lib/libQtCore.so.4
#12 0xb70a201c in QApplicationPrivate::notify_helper () from /usr/lib/libQtGui.so.4
#13 0xb70a9a9e in QApplication::notify () from /usr/lib/libQtGui.so.4
#14 0xb7b7c77d in KApplication::notify () from /usr/lib/libkdeui.so.5
#15 0xb6ed4c1b in QCoreApplication::notifyInternal () from /usr/lib/libQtCore.so.4
#16 0xb6ed5543 in QCoreApplicationPrivate::sendPostedEvents () from /usr/lib/libQtCore.so.4
#17 0xb6ed56dd in QCoreApplication::sendPostedEvents () from /usr/lib/libQtCore.so.4
#18 0xb6efc83f in ?? () from /usr/lib/libQtCore.so.4
#19 0x00000000 in ?? ()
Comment 3 Raphael Kubo da Costa 2009-04-08 19:09:34 UTC
What distro are you using? Were you using Dolphin, right-clicked a file and chose "Extract here, autodetect sub-folder"?

Can you please attach one or more files that caused this crash?

Besides, you need debug symbols for your backtrace to be useful. Please see http://techbase.kde.org/Development/Tutorials/Debugging/How_to_create_useful_crash_reports
Comment 4 xcojack@gmail.com 2009-04-08 19:15:00 UTC
Im using archlinux, and konqueror ;) Yeas I use from the right-clicked a file and
chose "Extract here, autodetect sub-folder".

This logs it's from gdb.
Comment 5 Raphael Kubo da Costa 2009-04-08 19:18:59 UTC
I could not reproduce this problem with a random RAR file in trunk. Can you attach any file that triggered this behaviour for you?
Comment 6 xcojack@gmail.com 2009-04-08 19:24:18 UTC
I can't becouse It's very hevy around 300mb, but now I has at last unpack it, without any errors... It's diferent, this ark work like he wants. Random working? :) Sory if this logs it's not helpfull, but I don't compile kde and don't knwo what was the flags in pkgbuild for debuging tools, I have hope its FULL DEBUG.
Comment 7 Raphael Kubo da Costa 2009-04-08 19:26:51 UTC
(In reply to comment #6)
> I can't becouse It's very hevy around 300mb, but now I has at last unpack it,
> without any errors...
You said it would crash on many files and extensions. Isn't there a smaller one you can attach here?

> It's diferent, this ark work like he wants. Random working? :)
It shouldn't :)
Comment 8 xcojack@gmail.com 2009-04-08 23:17:15 UTC
I sometimes reports a bug, not always, but ark has nervous me ;) becouse, he works like he wants :P Okey, I promise, If I have ever again this same accident with ark I'll raport it here. And tell with extension (.*)\.[a-zA-Z0-9]{1,6} it is.

Regards ;)
Comment 9 Abhinav 2009-05-11 11:08:38 UTC
for me also ark crashes after unpacking
The application Ark (ark) crashed and caused the signal 11 (SIGSEGV).
Please help us improve the software you use by filing a report at http://bugs.kde.org. Useful details include how to reproduce the error, documents that were loaded, etc.
Details
This backtrace appears to be of no use.
This is probably because your packages are built in a way which prevents creation of proper backtraces, or the stack frame was seriously corrupted in the crash.

(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread 0x7fb7cc347810 (LWP 12430)]
[New Thread 0x7fb7c307a950 (LWP 12436)]
[New Thread 0x7fb7c2679950 (LWP 12433)]
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
0x00000039b1a0b309 in pthread_cond_wait@@GLIBC_2.3.2 ()
   from /lib64/libpthread.so.0
[Current thread is 1 (Thread 0x7fb7cc347810 (LWP 12430))]

Thread 3 (Thread 0x7fb7c2679950 (LWP 12433)):
#0  0x00000039b0edeaa2 in select () from /lib64/libc.so.6
#1  0x0000003e53521d66 in ?? () from /usr/lib64/libQtCore.so.4
#2  0x0000003e5345a6d2 in ?? () from /usr/lib64/libQtCore.so.4
#3  0x00000039b1a073da in start_thread () from /lib64/libpthread.so.0
#4  0x00000039b0ee62bd in clone () from /lib64/libc.so.6

Thread 2 (Thread 0x7fb7c307a950 (LWP 12436)):
#0  0x00000039b0ea7f81 in nanosleep () from /lib64/libc.so.6
#1  0x00000039b0ea7da7 in sleep () from /lib64/libc.so.6
#2  0x0000003e94c6918f in ?? () from /usr/lib64/libkdeui.so.5
#3  0x0000003e94c69aea in KCrash::defaultCrashHandler () from /usr/lib64/libkdeui.so.5
#4  <signal handler called>
#5  0x0000003e5355a43d in QObject::~QObject () from /usr/lib64/libQtCore.so.4
#6  0x0000003e5355ddde in QSocketNotifier::~QSocketNotifier () from /usr/lib64/libQtCore.so.4
#7  0x0000003e534e4092 in ?? () from /usr/lib64/libQtCore.so.4
#8  0x0000003e534e991b in ?? () from /usr/lib64/libQtCore.so.4
#9  0x0000003e534e9a01 in QProcess::qt_metacall () from /usr/lib64/libQtCore.so.4
#10 0x0000003e934d99ed in KProcess::qt_metacall () from /usr/lib64/libkdecore.so.5
#11 0x0000003e535590a2 in QMetaObject::activate () from /usr/lib64/libQtCore.so.4
#12 0x0000003e5359034e in QSocketNotifier::activated () from /usr/lib64/libQtCore.so.4
#13 0x0000003e5355dd03 in QSocketNotifier::event () from /usr/lib64/libQtCore.so.4
#14 0x0000003e9298e73d in QApplicationPrivate::notify_helper () from /usr/lib64/libQtGui.so.4
#15 0x0000003e9299692a in QApplication::notify () from /usr/lib64/libQtGui.so.4
#16 0x0000003e94c06c7b in KApplication::notify () from /usr/lib64/libkdeui.so.5
#17 0x0000003e5354360c in QCoreApplication::notifyInternal () from /usr/lib64/libQtCore.so.4
#18 0x0000003e5356cf99 in ?? () from /usr/lib64/libQtCore.so.4
#19 0x0000003e504377bb in g_main_context_dispatch () from /lib64/libglib-2.0.so.0
#20 0x0000003e5043af8d in ?? () from /lib64/libglib-2.0.so.0
#21 0x0000003e5043b14b in g_main_context_iteration () from /lib64/libglib-2.0.so.0
#22 0x0000003e5356cd3e in QEventDispatcherGlib::processEvents () from /usr/lib64/libQtCore.so.4
#23 0x0000003e53541eb2 in QEventLoop::processEvents () from /usr/lib64/libQtCore.so.4
#24 0x0000003e5354227d in QEventLoop::exec () from /usr/lib64/libQtCore.so.4
#25 0x00007fb7c308041c in ?? () from /usr/lib64/kde4/kerfuffle_rar.so
#26 0x00007fb7c30825fa in ?? () from /usr/lib64/kde4/kerfuffle_rar.so
#27 0x0000003e93e1469b in Kerfuffle::ExtractJob::doWork () from /usr/lib64/libkerfuffle.so.4
#28 0x0000003e93e10965 in Kerfuffle::Job::qt_metacall () from /usr/lib64/libkerfuffle.so.4
#29 0x0000003e535590a2 in QMetaObject::activate () from /usr/lib64/libQtCore.so.4
#30 0x0000003e5355e3df in ?? () from /usr/lib64/libQtCore.so.4
#31 0x0000003e53553383 in QObject::event () from /usr/lib64/libQtCore.so.4
#32 0x0000003e9298e73d in QApplicationPrivate::notify_helper () from /usr/lib64/libQtGui.so.4
#33 0x0000003e9299692a in QApplication::notify () from /usr/lib64/libQtGui.so.4
#34 0x0000003e94c06c7b in KApplication::notify () from /usr/lib64/libkdeui.so.5
#35 0x0000003e5354360c in QCoreApplication::notifyInternal () from /usr/lib64/libQtCore.so.4
#36 0x0000003e535706a9 in ?? () from /usr/lib64/libQtCore.so.4
#37 0x0000003e5356cdbd in ?? () from /usr/lib64/libQtCore.so.4
#38 0x0000003e504377bb in g_main_context_dispatch () from /lib64/libglib-2.0.so.0
#39 0x0000003e5043af8d in ?? () from /lib64/libglib-2.0.so.0
#40 0x0000003e5043b14b in g_main_context_iteration () from /lib64/libglib-2.0.so.0
#41 0x0000003e5356cd1f in QEventDispatcherGlib::processEvents () from /usr/lib64/libQtCore.so.4
#42 0x0000003e53541eb2 in QEventLoop::processEvents () from /usr/lib64/libQtCore.so.4
#43 0x0000003e5354227d in QEventLoop::exec () from /usr/lib64/libQtCore.so.4
#44 0x0000003e53457738 in QThread::exec () from /usr/lib64/libQtCore.so.4
#45 0x0000003e5345a6d2 in ?? () from /usr/lib64/libQtCore.so.4
#46 0x00000039b1a073da in start_thread () from /lib64/libpthread.so.0
#47 0x00000039b0ee62bd in clone () from /lib64/libc.so.6

Thread 1 (Thread 0x7fb7cc347810 (LWP 12430)):
#0  0x00000039b1a0b309 in pthread_cond_wait@@GLIBC_2.3.2 () from /lib64/libpthread.so.0
#1  0x0000003e5345b6b9 in QWaitCondition::wait () from /usr/lib64/libQtCore.so.4
#2  0x0000003e5345a87c in QThread::wait () from /usr/lib64/libQtCore.so.4
#3  0x0000003e53524c91 in ?? () from /usr/lib64/libQtCore.so.4
#4  0x0000003e53525155 in ?? () from /usr/lib64/libQtCore.so.4
#5  0x00000039b0e3659d in exit () from /lib64/libc.so.6
#6  0x0000003e929ebdd8 in ?? () from /usr/lib64/libQtGui.so.4
#7  0x0000003e94c06698 in KApplication::xioErrhandler () from /usr/lib64/libkdeui.so.5
#8  0x0000003e8e045564 in _XIOError () from /usr/lib64/libX11.so.6
#9  0x0000003e8e04cfa8 in ?? () from /usr/lib64/libX11.so.6
#10 0x0000003e8e04d726 in _XEventsQueued () from /usr/lib64/libX11.so.6
#11 0x0000003e8e035d53 in XEventsQueued () from /usr/lib64/libX11.so.6
#12 0x0000003e92a254fc in ?? () from /usr/lib64/libQtGui.so.4
#13 0x0000003e5043a51a in g_main_context_check () from /lib64/libglib-2.0.so.0
#14 0x0000003e5043ae71 in ?? () from /lib64/libglib-2.0.so.0
#15 0x0000003e5043b14b in g_main_context_iteration () from /lib64/libglib-2.0.so.0
#16 0x0000003e5356cd3e in QEventDispatcherGlib::processEvents () from /usr/lib64/libQtCore.so.4
#17 0x0000003e92a2533f in ?? () from /usr/lib64/libQtGui.so.4
#18 0x0000003e53541eb2 in QEventLoop::processEvents () from /usr/lib64/libQtCore.so.4
#19 0x0000003e5354227d in QEventLoop::exec () from /usr/lib64/libQtCore.so.4
#20 0x0000003e53544544 in QCoreApplication::exec () from /usr/lib64/libQtCore.so.4
#21 0x000000000040b600 in _start ()
Comment 10 Raphael Kubo da Costa 2009-05-12 18:22:07 UTC
In order to help us understand the problem, please tell us what version of KDE you were using, what distribution and follow the instructions in http://techbase.kde.org/Development/Tutorials/Debugging/How_to_create_useful_crash_reports
Comment 11 Abhinav 2009-05-13 06:00:40 UTC
sorry .. i am using fedora 10 .. kde 4.2
Comment 12 Raphael Kubo da Costa 2009-05-13 06:02:11 UTC
4.2.2 or 4.2.3? Are you able to install debug packages?
Comment 13 Abhinav 2009-05-14 04:11:35 UTC
4.2.2 
wat debug packages???
Comment 14 Raphael Kubo da Costa 2009-05-14 04:14:17 UTC
As the backtrace you've pasted said, it's of no use, because it doesn't have debug symbols. Take a look at the link I've pasted in comment 10 - there are instructions about installing debug packages for Fedora that contain symbols useful for us to know the cause of the crash.
Comment 15 Abhinav 2009-05-14 04:21:47 UTC
well an update was performed .. and now the problem seems to have vanished :)
and the debug packages are already installed
Comment 16 Raphael Kubo da Costa 2009-05-14 04:31:46 UTC
Were you experiencing this crash every time before the update? The initial reporter mentioned it happened randomly.
Comment 17 Abhinav 2009-05-14 04:46:29 UTC
yeah, since the last 3 times i have been using ark .. it crashed after extraction .....but now its fine
Thank you !
Comment 18 Raphael Kubo da Costa 2009-05-14 06:13:26 UTC
Changing the status to WONTFIX as rarplugin has been deprecated in 4.3 in favour of clirarplugin. And the problem seems to have been fixed with it.