IIRC, this has been fixed in trunk and backported to 4.2.3.

Can you test this with trunk? Does it happen to any zip file?

Closing since the reporter seems to have vanished.

I got a similar crash with a gz-file.

Application that crashed: ark
Version of the application: 2.13
KDE Version: 4.3.00 (KDE 4.3.0)
Qt Version: 4.5.2
Operating System: Linux 2.6.28-15-generic i686
Distribution: Ubuntu 9.04

What I was doing when the application crashed:
nothing special. ark just crashed while closing it.

 -- Backtrace:
Application: Ark (ark), signal: Segmentation fault
[KCrash Handler]
#6  QWidget::setEnabled (this=0x6e6f6974, enable=true) at ../../include/QtGui/../../src/gui/kernel/qwidget.h:144
#7  0xb49249c5 in Part::setReadyGui (this=0x8164b30) at /build/buildd/kdeutils-4.3.0/ark/part/part.cpp:425
#8  0xb4924cfe in Part::slotPreviewExtracted (this=0x8164b30, job=0x838a998) at /build/buildd/kdeutils-4.3.0/ark/part/part.cpp:475
#9  0xb491d8f7 in Part::qt_metacall (this=0x8164b30, _c=QMetaObject::InvokeMetaMethod, _id=7, _a=0x839dca0) at /build/buildd/kdeutils-4.3.0/obj-i486-linux-gnu/ark/part/moc_part.cpp:121
#10 0xb6a348cb in QMetaCallEvent::placeMetaCall (this=0x83f0058, object=0x8164b30) at kernel/qobject.cpp:477
#11 0xb6a363b0 in QObject::event (this=0x8164b30, e=0x83f0058) at kernel/qobject.cpp:1111
#12 0xb6ee5d3c in QApplicationPrivate::notify_helper (this=0x80b4420, receiver=0x8164b30, e=0x83f0058) at kernel/qapplication.cpp:4056
#13 0xb6eee03e in QApplication::notify (this=0xbf842614, receiver=0x8164b30, e=0x83f0058) at kernel/qapplication.cpp:3603
#14 0xb7adf5cd in KApplication::notify (this=0xbf842614, receiver=0x8164b30, event=0x83f0058) at /build/buildd/kde4libs-4.3.0/kdeui/kernel/kapplication.cpp:302
#15 0xb6a25bcb in QCoreApplication::notifyInternal (this=0xbf842614, receiver=0x8164b30, event=0x83f0058) at kernel/qcoreapplication.cpp:610
#16 0xb6a26825 in QCoreApplicationPrivate::sendPostedEvents (receiver=0x0, event_type=0, data=0x809d470) at ../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:213
#17 0xb6a26a1d in QCoreApplication::sendPostedEvents (receiver=0x0, event_type=0) at kernel/qcoreapplication.cpp:1140
#18 0xb6a516af in postEventSourceDispatch (s=0x80b70c0) at ../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:218
#19 0xb622ab88 in IA__g_main_context_dispatch (context=0x80b6698) at /build/buildd/glib2.0-2.20.1/glib/gmain.c:1814
#20 0xb622e0eb in g_main_context_iterate (context=0x80b6698, block=1, dispatch=1, self=0x80b4538) at /build/buildd/glib2.0-2.20.1/glib/gmain.c:2448
#21 0xb622e268 in IA__g_main_context_iteration (context=0x80b6698, may_block=1) at /build/buildd/glib2.0-2.20.1/glib/gmain.c:2511
#22 0xb6a512f8 in QEventDispatcherGlib::processEvents (this=0x809cfa8, flags={i = -1081858856}) at kernel/qeventdispatcher_glib.cpp:327
#23 0xb6f87a75 in QGuiEventDispatcherGlib::processEvents (this=0x809cfa8, flags={i = -1081858808}) at kernel/qguieventdispatcher_glib.cpp:202
#24 0xb6a241fa in QEventLoop::processEvents (this=0xbf842580, flags={i = -1081858744}) at kernel/qeventloop.cpp:149
#25 0xb6a24642 in QEventLoop::exec (this=0xbf842580, flags={i = -1081858680}) at kernel/qeventloop.cpp:201
#26 0xb6a26ae9 in QCoreApplication::exec () at kernel/qcoreapplication.cpp:888
#27 0xb6ee5bb7 in QApplication::exec () at kernel/qapplication.cpp:3525
#28 0x08050308 in main (argc=4, argv=0xbf8429d4) at /build/buildd/kdeutils-4.3.0/ark/app/main.cpp:215

Report to https://bugs.kde.org

Hmm. Did you close the preview dialog before closing Ark? Were you extracting anything while you closed it?

Yes, I think, I had started the preview dialog for a text file before, but had closed it already. (At least the window of the preview dialog had gone. Whether the previewing task had been completely stopped too, I don't know.) There was just ark still running, but had no task to do (like i.e. extracting). As I closed ark, the error appeared.

I can't reproduce it here, but I'm reopening the report anyway. Are you able to reproduce this crash at will?

No, I haven't encountered it again. Perhaps it was just a single incident. But anyway.

Well, for now I'll close it again as WORKSFORME then.