Bug 213676

Summary:	Ark doesn't create archives or crashes
Product:	[Applications] ark	Reporter:	naryalin
Component:	general	Assignee:	Harald Hvaal <metellius>
Status:	RESOLVED WORKSFORME
Severity:	crash	CC:	rakuco
Priority:	NOR	Keywords:	investigated, triaged
Version First Reported In:	unspecified
Target Milestone:	---
Platform:	Unlisted Binaries
OS:	Linux
Latest Commit:		Version Fixed/Implemented In:
Sentry Crash Report:

Description naryalin 2009-11-08 13:19:19 UTC

Application that crashed: ark
Version of the application: 2.13
KDE Version: 4.3.2 (KDE 4.3.2)
Qt Version: 4.5.2
Operating System: Linux 2.6.31-14-generic i686
Distribution: Ubuntu 9.10

What I was doing when the application crashed:
I'm using kubuntu 9.10 but the problem was present since 9.04.
When I create zip archives Ark doesn't complete the operation, the archive has a casual name and I can't open it.
When I create rar archives Ark doesn't complete the operation and hangs till I stop it.

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

Thread 2 (Thread 0xb60a0b70 (LWP 3270)):
#0  0x00aade06 in clock_gettime () from /lib/tls/i686/cmov/librt.so.1
#1  0x03919bf3 in ?? () from /usr/lib/libQtCore.so.4
#2  0x03919de1 in ?? () from /usr/lib/libQtCore.so.4
#3  0x0391a88c in ?? () from /usr/lib/libQtCore.so.4
#4  0x03918210 in ?? () from /usr/lib/libQtCore.so.4
#5  0x0535ef80 in g_main_context_prepare () from /lib/libglib-2.0.so.0
#6  0x0535f341 in ?? () from /lib/libglib-2.0.so.0
#7  0x0535f853 in g_main_context_iteration () from /lib/libglib-2.0.so.0
#8  0x03918067 in QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib/libQtCore.so.4
#9  0x038ebc79 in QEventLoop::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib/libQtCore.so.4
#10 0x038ec0ca in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib/libQtCore.so.4
#11 0x037f9b73 in QThread::exec() () from /usr/lib/libQtCore.so.4
#12 0x00acd0ad in ?? () from /usr/lib/libkerfuffle.so.4
#13 0x037fce32 in ?? () from /usr/lib/libQtCore.so.4
#14 0x0655e80e in start_thread () from /lib/tls/i686/cmov/libpthread.so.0
#15 0x004c17ee in clone () from /lib/tls/i686/cmov/libc.so.6

Thread 1 (Thread 0xb7852700 (LWP 3269)):
[KCrash Handler]
#6  0x03842ac8 in QString::operator=(QString const&) () from /usr/lib/libQtCore.so.4
#7  0x03885c4a in QIODevice::setErrorString(QString const&) () from /usr/lib/libQtCore.so.4
#8  0x038ca816 in ?? () from /usr/lib/libQtCore.so.4
#9  0x0388b2ce in QProcess::waitForFinished(int) () from /usr/lib/libQtCore.so.4
#10 0x00adaa4e in Kerfuffle::CliInterface::doKill() () from /usr/lib/libkerfuffle.so.4
#11 0x00aca95e in Kerfuffle::Job::doKill() () from /usr/lib/libkerfuffle.so.4
#12 0x077154b2 in KJob::kill(KJob::KillVerbosity) () from /usr/lib/libkdecore.so.5
#13 0x00db0497 in KUiServerJobTracker::Private::_k_killJob() () from /usr/lib/libkdeui.so.5
#14 0x00db0509 in KUiServerJobTracker::qt_metacall(QMetaObject::Call, int, void**) () from /usr/lib/libkdeui.so.5
#15 0x03903263 in QMetaObject::activate(QObject*, int, int, void**) () from /usr/lib/libQtCore.so.4
#16 0x03903ec2 in QMetaObject::activate(QObject*, QMetaObject const*, int, void**) () from /usr/lib/libQtCore.so.4
#17 0x00f225a7 in ?? () from /usr/lib/libkdeui.so.5
#18 0x00f229a3 in ?? () from /usr/lib/libkdeui.so.5
#19 0x00a1a7b4 in ?? () from /usr/lib/libQtDBus.so.4
#20 0x00a22197 in ?? () from /usr/lib/libQtDBus.so.4
#21 0x038fd5fe in QObject::event(QEvent*) () from /usr/lib/libQtCore.so.4
#22 0x01095f54 in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /usr/lib/libQtGui.so.4
#23 0x0109d67c in QApplication::notify(QObject*, QEvent*) () from /usr/lib/libQtGui.so.4
#24 0x00db5bfa in KApplication::notify(QObject*, QEvent*) () from /usr/lib/libkdeui.so.5
#25 0x038ed6cb in QCoreApplication::notifyInternal(QObject*, QEvent*) () from /usr/lib/libQtCore.so.4
#26 0x038ee2b2 in QCoreApplicationPrivate::sendPostedEvents(QObject*, int, QThreadData*) () from /usr/lib/libQtCore.so.4
#27 0x038ee47d in QCoreApplication::sendPostedEvents(QObject*, int) () from /usr/lib/libQtCore.so.4
#28 0x039183ff in ?? () from /usr/lib/libQtCore.so.4
#29 0x0535be78 in g_main_context_dispatch () from /lib/libglib-2.0.so.0
#30 0x0535f720 in ?? () from /lib/libglib-2.0.so.0
#31 0x0535f853 in g_main_context_iteration () from /lib/libglib-2.0.so.0
#32 0x0391802c in QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib/libQtCore.so.4
#33 0x01136be5 in ?? () from /usr/lib/libQtGui.so.4
#34 0x038ebc79 in QEventLoop::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib/libQtCore.so.4
#35 0x038ec0ca in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib/libQtCore.so.4
#36 0x038ee53f in QCoreApplication::exec() () from /usr/lib/libQtCore.so.4
#37 0x01095dd7 in QApplication::exec() () from /usr/lib/libQtGui.so.4
#38 0x08050184 in _start ()

Reported using DrKonqi

Comment 1 naryalin 2009-11-08 13:32:14 UTC

More in depth:
This happens only with datas on a SD card.

Comment 2 Raphael Kubo da Costa 2009-11-08 17:26:35 UTC

Do you mean the archive is being created on an SD card or the files you're trying to add to a new archive are stored on an SD card, but the archive itself is in a regular directory?

Regarding zip files: what do you mean by a casual name?

Can you please do the following things:
 * Install the debug packages for your distribution and paste a more detailed backtrace
 * Paste here the output of the command-line zip program when you try to create an archive (zip -r /path/to/your/archive.zip file1 file2 ... fileN)
 * Paste here the output of the command-line rar program when you try to create an archive (rar a /path/to/your/archive.rar file1 file2 ... fileN)

Thanks!

Comment 3 Raphael Kubo da Costa 2009-11-22 18:19:23 UTC

Closing as the reporter seems to have vanished.

Comment 4 Andrew Crouthamel 2018-09-20 03:09:16 UTC

Dear Bug Submitter,

This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days, the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information.

For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

If you have already provided the requested information, please set the bug status as REPORTED so that the KDE team knows that the bug is ready to be confirmed.

Thank you for helping us make KDE software even better for everyone!

Comment 5 Andrew Crouthamel 2018-10-21 05:01:30 UTC

This bug has been in NEEDSINFO status with no change for at least
30 days. The bug is now closed as RESOLVED > WORKSFORME
due to lack of needed information.

For more information about our bug triaging procedures please read the
wiki located here:
https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

Thank you for helping us make KDE software even better for everyone!