Bug 250222

Summary:	Ark crashes with unrar-free
Product:	[Applications] ark	Reporter:	prasmal <prasmal>
Component:	general	Assignee:	Harald Hvaal <metellius>
Status:	RESOLVED DUPLICATE
Severity:	crash	CC:	rakuco
Priority:	NOR
Version:	2.14
Target Milestone:	---
Platform:	Compiled Sources
OS:	Linux
Latest Commit:		Version Fixed In:
Sentry Crash Report:

Description prasmal 2010-09-04 23:59:47 UTC

Application: ark (2.14)
KDE Platform Version: 4.4.5 (KDE 4.4.5) (Compiled from sources)
Qt Version: 4.6.3
Operating System: Linux 2.6.32-5-686 i686
Distribution: Debian GNU/Linux testing (squeeze)

-- Information about the crash:
I tried to unrar the folder, but the ark could not open the folder. I have this situation every time you want to unrar

The crash can be reproduced every time.

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

Thread 2 (Thread 0xb3131b70 (LWP 14467)):
[KCrash Handler]
#6  QBasicAtomicInt::ref (this=0xb3130538, t=..., date=0x0, time=0xb3130708) at ../../include/QtCore/../../src/corelib/arch/qatomic_i386.h:120
#7  QString (this=0xb3130538, t=..., date=0x0, time=0xb3130708) at ../../include/QtCore/../../src/corelib/tools/qstring.h:715
#8  QDateTimeParser::fromString (this=0xb3130538, t=..., date=0x0, time=0xb3130708) at tools/qdatetime.cpp:5499
#9  0xb632a328 in QTime::fromString (string=..., format=...) at tools/qdatetime.cpp:1980
#10 0xb3134c2e in ?? () from /usr/lib/kde4/kerfuffle_clirar.so
#11 0xb78c12b0 in Kerfuffle::CliInterface::handleLine(QString const&) () from /usr/lib/libkerfuffle.so.4
#12 0xb78c1896 in Kerfuffle::CliInterface::readStdout(bool) () from /usr/lib/libkerfuffle.so.4
#13 0xb78c1b83 in Kerfuffle::CliInterface::qt_metacall(QMetaObject::Call, int, void**) () from /usr/lib/libkerfuffle.so.4
#14 0xb31347d2 in ?? () from /usr/lib/kde4/kerfuffle_clirar.so
#15 0xb641280a in QMetaObject::metacall (object=0x83c3808, cl=3055190785, idx=0, argv=0x83c3808) at kernel/qmetaobject.cpp:237
#16 0xb64211db in QMetaObject::activate (sender=0x83e3990, m=0xb651f848, local_signal_index=5, argv=0x0) at kernel/qobject.cpp:3295
#17 0xb63a3657 in QProcess::readyReadStandardOutput (this=0x83e3990) at .moc/release-shared/moc_qprocess.cpp:162
#18 0xb63a899f in QProcessPrivate::_q_canReadStandardOutput (this=0x83e3e98) at io/qprocess.cpp:897
#19 0xb63a8e16 in QProcess::qt_metacall (this=0x83e3990, _c=QMetaObject::InvokeMetaMethod, _id=9, _a=0xb3130bb8) at .moc/release-shared/moc_qprocess.cpp:107
#20 0xb709acea in KProcess::qt_metacall (this=0x83e3990, _c=QMetaObject::InvokeMetaMethod, _id=17, _a=0xb3130bb8) at ./kprocess.moc:69
#21 0xb641280a in QMetaObject::metacall (object=0x83e3990, cl=3055190785, idx=17, argv=0xb3130bb8) at kernel/qmetaobject.cpp:237
#22 0xb64211db in QMetaObject::activate (sender=0x83e3a48, m=0xb65216d0, local_signal_index=0, argv=0xb3130bb8) at kernel/qobject.cpp:3295
#23 0xb6473673 in QSocketNotifier::activated (this=0x83e3a48, _t1=15) at .moc/release-shared/moc_qsocketnotifier.cpp:89
#24 0xb6428397 in QSocketNotifier::event (this=0x83e3a48, e=0xb3131044) at kernel/qsocketnotifier.cpp:317
#25 0xb667d5cc in QApplicationPrivate::notify_helper (this=0x816e1a0, receiver=0x83e3a48, e=0xb3131044) at kernel/qapplication.cpp:4302
#26 0xb668415e in QApplication::notify (this=0xbfbfa31c, receiver=0x83e3a48, e=0xb3131044) at kernel/qapplication.cpp:3706
#27 0xb73ffc5a in KApplication::notify (this=0xbfbfa31c, receiver=0x83e3a48, event=0xb3131044) at ../../kdeui/kernel/kapplication.cpp:302
#28 0xb640d52b in QCoreApplication::notifyInternal (this=0xbfbfa31c, receiver=0x83e3a48, event=0xb3131044) at kernel/qcoreapplication.cpp:726
#29 0xb643946a in QCoreApplication::sendEvent (source=0x83dd958) at ../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:215
#30 socketNotifierSourceDispatch (source=0x83dd958) at kernel/qeventdispatcher_glib.cpp:110
#31 0xb59b92f5 in g_main_context_dispatch () from /lib/libglib-2.0.so.0
#32 0xb59bcfd8 in ?? () from /lib/libglib-2.0.so.0
#33 0xb59bd1b8 in g_main_context_iteration () from /lib/libglib-2.0.so.0
#34 0xb6439095 in QEventDispatcherGlib::processEvents (this=0x81ec000, flags=...) at kernel/qeventdispatcher_glib.cpp:412
#35 0xb640bb49 in QEventLoop::processEvents (this=0xb3131290, flags=) at kernel/qeventloop.cpp:149
#36 0xb640bf9a in QEventLoop::exec (this=0xb3131290, flags=...) at kernel/qeventloop.cpp:201
#37 0xb630e619 in QThread::exec (this=0x83dd9a0) at thread/qthread.cpp:487
#38 0xb78afff2 in ?? () from /usr/lib/libkerfuffle.so.4
#39 0xb6310fae in QThreadPrivate::start (arg=0xb31312e8) at thread/qthread_unix.cpp:248
#40 0xb5a63955 in start_thread (arg=0xb3131b70) at pthread_create.c:300
#41 0xb613010e in clone () at ../sysdeps/unix/sysv/linux/i386/clone.S:130

Thread 1 (Thread 0xb5639a10 (LWP 14463)):
#0  0xb78e1424 in __kernel_vsyscall ()
#1  0xb6122916 in *__GI___poll (fds=0xb61a6ff4, nfds=1, timeout=-1) at ../sysdeps/unix/sysv/linux/poll.c:87
#2  0xb57090f0 in ?? () from /usr/lib/libxcb.so.1
#3  0xb570b761 in xcb_wait_for_reply () from /usr/lib/libxcb.so.1
#4  0xb5c867a6 in _XReply () from /usr/lib/libX11.so.6
#5  0xb5c64569 in XGetSelectionOwner () from /usr/lib/libX11.so.6
#6  0xb755ce81 in KWindowSystem::compositingActive () at ../../kdeui/windowmanagement/kwindowsystem_x11.cpp:765
#7  0xb53d9fff in ?? () from /usr/lib/kde4/plugins/styles/oxygen.so
#8  0xb53eae67 in ?? () from /usr/lib/kde4/plugins/styles/oxygen.so
#9  0xb640c7ca in QCoreApplicationPrivate::sendThroughObjectEventFilters (this=0x816e1a0, receiver=0x83c1a40, event=0xbfbfa0c8) at kernel/qcoreapplication.cpp:841
#10 0xb667d5a9 in QApplicationPrivate::notify_helper (this=0x816e1a0, receiver=0x83c1a40, e=0xbfbfa0c8) at kernel/qapplication.cpp:4298
#11 0xb66841f9 in QApplication::notify (this=0xbfbfa31c, receiver=0x83c1a40, e=0xbfbfa0c8) at kernel/qapplication.cpp:4267
#12 0xb73ffc5a in KApplication::notify (this=0xbfbfa31c, receiver=0x83c1a40, event=0xbfbfa0c8) at ../../kdeui/kernel/kapplication.cpp:302
#13 0xb640d52b in QCoreApplication::notifyInternal (this=0xbfbfa31c, receiver=0x83c1a40, event=0xbfbfa0c8) at kernel/qcoreapplication.cpp:726
#14 0xb66da719 in QCoreApplication::sendEvent (this=0x83cb4d0, recursive=false, disableUpdates=false) at ../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:215
#15 QWidgetPrivate::sendPendingMoveAndResizeEvents (this=0x83cb4d0, recursive=false, disableUpdates=false) at kernel/qwidget.cpp:7112
#16 0xb66e1399 in QWidgetPrivate::show_helper (this=0x83cb4d0) at kernel/qwidget.cpp:7163
#17 0xb66e16e3 in QWidgetPrivate::show_recursive (this=0x83cb4d0) at kernel/qwidget.cpp:7093
#18 0xb66e17dc in QWidgetPrivate::showChildren (this=0x81dc488, spontaneous=false) at kernel/qwidget.cpp:7530
#19 0xb66e13c1 in QWidgetPrivate::show_helper (this=0x81dc488) at kernel/qwidget.cpp:7169
#20 0xb66e396b in QWidget::setVisible (this=0x81daad8, visible=true) at kernel/qwidget.cpp:7444
#21 0x08050b60 in _start ()

Possible duplicates by query: bug 244100, bug 212925.

Reported using DrKonqi

Comment 1 Raphael Kubo da Costa 2010-09-05 01:47:19 UTC

How long have you had this crash? Do you use unrar or unrar-free?

Comment 2 prasmal 2010-09-05 16:35:02 UTC

Dnia niedziela 05 wrzesień 2010 o 01:47:22 Raphael Kubo da Costa 
napisał(a):
> https://bugs.kde.org/show_bug.cgi?id=250222
> 
> 
> 
> 
> 
> --- Comment #1 from Raphael Kubo da Costa <kubito gmail com>  
2010-09-05
> 01:47:19 --- How long have you had this crash? Do you use unrar or
> unrar-free?
I use unrar-free. Last week I tried to unrar the three folders (using the 
ark, and the console, but could not unpack. Yesterday you get an error 
when I used the ark. Today I tried to unrar the in console and unpacked. 
This problem occurs when I use ark.

Comment 3 prasmal 2010-09-05 17:41:30 UTC

Dnia niedziela 05 wrzesień 2010 o 16:35:06 prasmal napisał(a):
> https://bugs.kde.org/show_bug.cgi?id=250222
> 
> 
> 
> 
> 
> --- Comment #2 from prasmal <prasmal googlemail com>  
2010-09-05 16:35:02
> --- Dnia niedziela 05 wrzesień 2010 o 01:47:22 Raphael Kubo da 
Costa
> 
> napisał(a):
> > https://bugs.kde.org/show_bug.cgi?id=250222
> > 
> > 
> > 
> > 
> > 
> > --- Comment #1 from Raphael Kubo da Costa <kubito gmail com>
> 
> 2010-09-05
> 
> > 01:47:19 --- How long have you had this crash? Do you use unrar 
or
> > unrar-free?
> 
> I use unrar-free. Last week I tried to unrar the three folders (using 
the
> ark, and the console, but could not unpack. Yesterday you get an 
error
> when I used the ark. Today I tried to unrar the in console and 
unpacked.
> This problem occurs when I use ark.
sorry, Unrar created a folder. I checked that folder unrar in the 
console and is empty. So the console and the ark can not unpack.

Comment 4 Raphael Kubo da Costa 2010-09-05 19:47:52 UTC

Ark has not been working with unrar-free for some time, so I'm marking this report as a duplicate of the original one.

As for this specific case, if unrar itself can't unpack your archive either, then there's some problem with the archive (or you might need to use unrar instead of unrar-free).

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