Bug 254228 - Ark crash
Summary: Ark crash
Status: RESOLVED DUPLICATE of bug 222392
Alias: None
Product: ark
Classification: Applications
Component: general (show other bugs)
Version: 2.15
Platform: Ubuntu Linux
: NOR crash
Target Milestone: ---
Assignee: Raphael Kubo da Costa
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2010-10-15 06:16 UTC by kazmafrost
Modified: 2011-05-11 23:35 UTC (History)
2 users (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments
Action for crash (638.23 KB, image/jpeg)
2010-10-18 04:29 UTC, kazmafrost
Details
Reproduce crash for backtrace (6.04 KB, text/plain)
2010-10-21 04:09 UTC, kazmafrost
Details

Note You need to log in before you can comment on or make changes to this bug.
Description kazmafrost 2010-10-15 06:16:02 UTC
Application: ark (2.15)
KDE Platform Version: 4.5.2 (KDE 4.5.2)
Qt Version: 4.7.0
Operating System: Linux 2.6.35-22-generic i686
Distribution: Ubuntu 10.10

-- Information about the crash:
- What I was doing when the application crashed:
At Kubuntu 10.10(32bit) compressed some music files to 7zip format.
Ark crash occurred after the completion.

-- Backtrace:
Application: Ark (ark), signal: Segmentation fault
[Current thread is 1 (Thread 0xb7835710 (LWP 6872))]

Thread 2 (Thread 0xb3fc9b70 (LWP 6877)):
#0  0x00caf416 in __kernel_vsyscall ()
#1  0x003e1de6 in poll () from /lib/libc.so.6
#2  0x0736ea1b in g_poll () from /lib/libglib-2.0.so.0
#3  0x0736143c in ?? () from /lib/libglib-2.0.so.0
#4  0x07361848 in g_main_context_iteration () from /lib/libglib-2.0.so.0
#5  0x0661659f in QEventDispatcherGlib::processEvents (this=0x85e4420, flags=...) at kernel/qeventdispatcher_glib.cpp:417
#6  0x065e6609 in QEventLoop::processEvents (this=0xb3fc9290, flags=) at kernel/qeventloop.cpp:149
#7  0x065e6a8a in QEventLoop::exec (this=0xb3fc9290, flags=...) at kernel/qeventloop.cpp:201
#8  0x064e2b7e in QThread::exec (this=0x85e7a90) at thread/qthread.cpp:490
#9  0x065c535b in QInotifyFileSystemWatcherEngine::run (this=0x85e7a90) at io/qfilesystemwatcher_inotify.cpp:248
#10 0x064e5df9 in QThreadPrivate::start (arg=0x85e7a90) at thread/qthread_unix.cpp:266
#11 0x00257cc9 in start_thread () from /lib/libpthread.so.0
#12 0x003f06ae in clone () from /lib/libc.so.6

Thread 1 (Thread 0xb7835710 (LWP 6872)):
[KCrash Handler]
#7  QString::operator= (this=0x54, other=...) at tools/qstring.cpp:1324
#8  0x06576bba in QIODevice::setErrorString (this=0xafd00cd8, str=...) at io/qiodevice.cpp:1602
#9  0x065c11d6 in QProcessPrivate::waitForFinished (this=0xafd01058, msecs=30000) at io/qprocess_unix.cpp:1107
#10 0x0657ba1e in QProcess::waitForFinished (this=0xafd00cd8, msecs=30000) at io/qprocess.cpp:1742
#11 0x0063d9be in Kerfuffle::CliInterface::doKill (this=0x870cb78) at ../../../ark/kerfuffle/cliinterface.cpp:621
#12 0x006314c4 in Kerfuffle::Job::doKill (this=0x8730280) at ../../../ark/kerfuffle/jobs.cpp:116
#13 0x00756bb2 in KJob::kill (this=0x8730280, verbosity=KJob::EmitResult) at ../../kdecore/jobs/kjob.cpp:106
#14 0x00f6a167 in KUiServerJobTracker::Private::_k_killJob (this=0x84a7218) at ../../kdeui/jobs/kuiserverjobtracker.cpp:59
#15 0x00f6a1d9 in KUiServerJobTracker::qt_metacall (this=0x84908d8, _c=QMetaObject::InvokeMetaMethod, _id=25, _a=0xbfb8fd5c) at ./kuiserverjobtracker.moc:100
#16 0x065ed8ca in QMetaObject::metacall (object=0x84908d8, cl=2949647576, idx=25, argv=0xbfb8fd5c) at kernel/qmetaobject.cpp:237
#17 0x066006ad in QMetaObject::activate (sender=0x88508b8, m=0x11493e4, local_signal_index=0, argv=0xafd00530) at kernel/qobject.cpp:3280
#18 0x010f26e7 in OrgKdeJobViewV2Interface::cancelRequested (this=0x88508b8) at jobviewifacev2.moc:122
#19 0x010f2ccb in OrgKdeJobViewV2Interface::qt_metacall (this=0x88508b8, _c=QMetaObject::InvokeMetaMethod, _id=0, _a=0xbfb9004c) at jobviewifacev2.moc:98
#20 0x0059d9dc in QDBusConnectionPrivate::deliverCall (this=0x8424ca0, object=0x88508b8, msg=..., metaTypes=..., slotIdx=5) at qdbusintegrator.cpp:919
#21 0x005a91f7 in QDBusCallDeliveryEvent::placeMetaCall (this=0x8827f10, object=0x88508b8) at qdbusintegrator_p.h:103
#22 0x065fa6a2 in QObject::event (this=0x88508b8, e=0xbfb8f901) at kernel/qobject.cpp:1219
#23 0x03410fdc in QApplicationPrivate::notify_helper (this=0x83eb9c8, receiver=0x88508b8, e=0x8827f10) at kernel/qapplication.cpp:4396
#24 0x0341704e in QApplication::notify (this=0xbfb9091c, receiver=0x88508b8, e=0x8827f10) at kernel/qapplication.cpp:3798
#25 0x00f6fcfa in KApplication::notify (this=0xbfb9091c, receiver=0x88508b8, event=0x8827f10) at ../../kdeui/kernel/kapplication.cpp:310
#26 0x065e7b3b in QCoreApplication::notifyInternal (this=0xbfb9091c, receiver=0x88508b8, event=0x8827f10) at kernel/qcoreapplication.cpp:732
#27 0x065ead8b in sendEvent (receiver=0x0, event_type=0, data=0x83d4ea0) at ../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:215
#28 QCoreApplicationPrivate::sendPostedEvents (receiver=0x0, event_type=0, data=0x83d4ea0) at kernel/qcoreapplication.cpp:1373
#29 0x065eaf4d in QCoreApplication::sendPostedEvents (receiver=0x0, event_type=0) at kernel/qcoreapplication.cpp:1266
#30 0x06616a74 in sendPostedEvents (s=0x83edd10) at ../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:220
#31 postEventSourceDispatch (s=0x83edd10) at kernel/qeventdispatcher_glib.cpp:277
#32 0x0735d855 in g_main_context_dispatch () from /lib/libglib-2.0.so.0
#33 0x07361668 in ?? () from /lib/libglib-2.0.so.0
#34 0x07361848 in g_main_context_iteration () from /lib/libglib-2.0.so.0
#35 0x06616565 in QEventDispatcherGlib::processEvents (this=0x83d4b60, flags=...) at kernel/qeventdispatcher_glib.cpp:415
#36 0x034d2be5 in QGuiEventDispatcherGlib::processEvents (this=0x83d4b60, flags=...) at kernel/qguieventdispatcher_glib.cpp:204
#37 0x065e6609 in QEventLoop::processEvents (this=0xbfb90874, flags=) at kernel/qeventloop.cpp:149
#38 0x065e6a8a in QEventLoop::exec (this=0xbfb90874, flags=...) at kernel/qeventloop.cpp:201
#39 0x065eb00f in QCoreApplication::exec () at kernel/qcoreapplication.cpp:1009
#40 0x0340fe07 in QApplication::exec () at kernel/qapplication.cpp:3672
#41 0x080539f9 in main (argc=5, argv=0xbfb90cb4) at ../../../ark/app/main.cpp:209

Reported using DrKonqi
Comment 1 Raphael Kubo da Costa 2010-10-16 05:48:15 UTC
From the backtrace, it looks like you canceled the creation of the archive. Is this correct?

Are you able to reproduce this crash?
Comment 2 kazmafrost 2010-10-16 06:28:48 UTC
Yes.
I first task cancel, and immediately try again. Then crash.
But, in spite of crashed generated compressed file that has been made successfully.
Comment 3 Raphael Kubo da Costa 2010-10-16 19:50:28 UTC
And what steps did you follow to cancel the archive creation?
Comment 4 kazmafrost 2010-10-17 03:03:51 UTC
I was cancel in the notification area. (stop button)
Comment 5 Raphael Kubo da Costa 2010-10-17 12:29:15 UTC
Hmm, the weird thing is that I get no notification when compressing an archive here. Can you tell me what text is shown in the notification for you?
Comment 6 kazmafrost 2010-10-18 04:29:05 UTC
Created attachment 52631 [details]
Action for crash

I screenshot attached.
Perhaps, only kubuntu problem? hmm..
Comment 7 Raphael Kubo da Costa 2010-10-18 05:42:47 UTC
Thanks for the screenshots -- I was creating a new archive from Ark instead of compressing via the context menus.

I got a crash when I stopped Ark here too, but the backtrace was different. They might all be related to bug 193908. Do you always get the same backtrace when you do this?
Comment 8 kazmafrost 2010-10-18 07:58:05 UTC
Uncertain but, backtrace seems to be the other.

And I have a same problem as bug 193908.
But the difference, regardless of file size. Just close Ark with windows x button before the file loaded.
Comment 9 Raphael Kubo da Costa 2010-10-21 01:06:02 UTC
Can you post another (or some other) backtrace(s) you get?

As for bug 193908, yes, that happens regardless of the size of the file.
Comment 10 kazmafrost 2010-10-21 04:09:37 UTC
Created attachment 52711 [details]
Reproduce crash for backtrace

Reproduced the crash on .zip format.
Strangely, this backtrace appears to be related with bug 222392.
Comment 11 Raphael Kubo da Costa 2010-12-08 02:19:44 UTC
Changing the default assignee in the currently open Ark bug reports to me.
Comment 12 Raphael Kubo da Costa 2011-05-11 23:35:40 UTC
OK, I think this is a duplicate of bug 222392 indeed.

*** This bug has been marked as a duplicate of bug 222392 ***