Note that what crashed was ark, not kpackagekit.

Is this crash always reproducible? If so, can you attach or post a link to the specific extension that causes this crash?

One more thing: were you browsing the extension in Dolphin, clicked and previewed it in Dolphin itself, extracted it and then everything crashed automatically?

First of all: thankyou for correcting mi post, it was Ark, not KPackageKit.

> Is this crash always reproducible? If so, can you attach or post a link to the
> specific extension that causes this crash?

I'm not sure, I have had the same problem with Ark, which I've already reported (bug 240919). Then this bug was marked as a duplicate of bug 237728.

But that time, it was a TAR file, and this one was a "chrome extension" CRX file, which it's supossed to be a ZIP file

> One more thing: were you browsing the extension in Dolphin, clicked and
> previewed it in Dolphin itself, extracted it and then everything crashed
> automatically?

I was browsing in Dolphin, yes, but I use de option "Open with..." and then I chose Ark, not "extract here". Ark asked me the correct tipe of compressed file, I chose ZIP, and Ark was able to open it correctly. I extract the files in a foldet, detecting the path. The extraction was succesfull but then Ark crashed.

Well, I suposse this is what I should specify before, sorry.

(In reply to comment #3)
> > Is this crash always reproducible? If so, can you attach or post a link to the
> > specific extension that causes this crash?
> 
> I'm not sure, I have had the same problem with Ark, which I've already reported
> (bug 240919). Then this bug was marked as a duplicate of bug 237728.

Interesting. The problem with this report and the ones you've mentioned is that I haven't been able to reproduce this crash here yet.

> But that time, it was a TAR file, and this one was a "chrome extension" CRX
> file, which it's supossed to be a ZIP file

Does it always happen to all CRX files and TAR files? If not, can you point me to a specific file that causes Ark to crash?
 
> > One more thing: were you browsing the extension in Dolphin, clicked and
> > previewed it in Dolphin itself, extracted it and then everything crashed
> > automatically?
> 
> I was browsing in Dolphin, yes, but I use de option "Open with..." and then I
> chose Ark, not "extract here". Ark asked me the correct tipe of compressed
> file, I chose ZIP, and Ark was able to open it correctly. I extract the files
> in a foldet, detecting the path. The extraction was succesfull but then Ark
> crashed.
> 
> Well, I suposse this is what I should specify before, sorry.

What other options have you checked in the extraction dialog? "Close Ark after extraction", "preserve paths"? Did you extract it to a normal folder, such as /tmp?

> Interesting. The problem with this report and the ones you've mentioned is that > I haven't been able to reproduce this crash here yet.

> Does it always happen to all CRX files and TAR files? If not, can you point me > to a specific file that causes Ark to crash?

No, it doesn't happen with every CRX file, I remember I have uncompressed some of them before.
In fact, I did it again but with my laptop (which also has KDE 4.4.5) intead of my PC (which now has KDE 4.5.0) and it didn't happen.

But let me tell you that, a problem like this, has happended to me before, not only once with Ark, with different tipes of files, and not only with KDE applications... many apps use to crash after closing them from the "X" button, Ark, Kalzium, KPackageKit, KSpread... and even OpenOffice on my Kubuntu instalation so... I'm starting to think this is a Kubuntu problem... more than KDE problem

> What other options have you checked in the extraction dialog? "Close Ark after
> extraction", "preserve paths"? Did you extract it to a normal folder, such as
> /tmp?

Yes, I just extracted it in the same folder where the original file was, preserving the paths.

Well, since neither of us can reproduce it at will, I'm closing the report for now. If you find a way to reproduce this issue again, please reopen the report with more information. Thanks!

I have had, again, the same error, twice... so I suppose I have been able to reproduce it.

1) Kubuntu 10.04 with KDE 4.5


Application: Ark (ark), signal: Segmentation fault
[Current thread is 1 (Thread 0x7f8bd3249760 (LWP 7299))]

Thread 2 (Thread 0x7f8bbda8b710 (LWP 7300)):
#0  0x00007f8bd01eef83 in *__GI___poll (fds=<value optimized out>, nfds=<value optimized out>, timeout=-1) at ../sysdeps/unix/sysv/linux/poll.c:87
#1  0x00007f8bcbe374a9 in ?? () from /lib/libglib-2.0.so.0
#2  0x00007f8bcbe378fc in g_main_context_iteration () from /lib/libglib-2.0.so.0
#3  0x00007f8bd0945bd6 in QEventDispatcherGlib::processEvents (this=0x1a440b0, flags=<value optimized out>) at kernel/qeventdispatcher_glib.cpp:414
#4  0x00007f8bd09187b2 in QEventLoop::processEvents (this=<value optimized out>, flags=) at kernel/qeventloop.cpp:149
#5  0x00007f8bd0918b9c in QEventLoop::exec (this=0x7f8bbda8adb0, flags=) at kernel/qeventloop.cpp:201
#6  0x00007f8bd082423d in QThread::exec (this=<value optimized out>) at thread/qthread.cpp:490
#7  0x00007f8bd08f86d8 in QInotifyFileSystemWatcherEngine::run (this=0x1a5ca20) at io/qfilesystemwatcher_inotify.cpp:248
#8  0x00007f8bd08271be in QThreadPrivate::start (arg=0x1a5ca20) at thread/qthread_unix.cpp:266
#9  0x00007f8bce05a9ca in start_thread (arg=<value optimized out>) at pthread_create.c:300
#10 0x00007f8bd01fb6fd in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:112
#11 0x0000000000000000 in ?? ()

Thread 1 (Thread 0x7f8bd3249760 (LWP 7299)):
[KCrash Handler]
#6  QItemSelectionModel::hasSelection (this=0x1c069f0) at itemviews/qitemselectionmodel.cpp:1398
#7  0x00007f8bbbc31fb1 in DolphinView::statusBarText (this=0x1b552f0) at ../../../../apps/dolphin/src/dolphinview.cpp:484
#8  0x00007f8bbbe77bbd in DolphinPart::updateStatusBar (this=0x1b30b60) at ../../../../apps/dolphin/src/dolphinpart.cpp:611
#9  0x00007f8bbbe7a69d in DolphinPart::qt_metacall (this=0x1b30b60, _c=QMetaObject::InvokeMetaMethod, _id=<value optimized out>, _a=0x7fffbdfabc20) at ./dolphinpart.moc:144
#10 0x00007f8bd09317a7 in QMetaObject::activate (sender=0x1b3e530, m=<value optimized out>, local_signal_index=<value optimized out>, argv=0x7fffbdfabc20) at kernel/qobject.cpp:3280
#11 0x00007f8bd2570506 in KDirListerCache::forgetDirs (this=0x1b4d780, lister=0x1b552f0) at ../../kio/kio/kdirlister.cpp:452
#12 0x00007f8bd25738b8 in ~KDirLister (this=0x1b3e530, __in_chrg=<value optimized out>) at ../../kio/kio/kdirlister.cpp:1949
#13 0x00007f8bbbe7773a in ~DolphinPart (this=0x1b30b60, __in_chrg=<value optimized out>, __vtt_parm=<value optimized out>) at ../../../../apps/dolphin/src/dolphinpart.cpp:150
#14 0x00007f8bd29424d0 in KParts::Part::slotWidgetDestroyed (this=0x1b30b60) at ../../kparts/part.cpp:354
#15 0x00007f8bd29425cc in KParts::Part::qt_metacall (this=0x1b30b60, _c=QMetaObject::InvokeMetaMethod, _id=<value optimized out>, _a=0x7fffbdfabf10) at ./part.moc:82
#16 0x00007f8bd29434b5 in KParts::ReadOnlyPart::qt_metacall (this=0x1c069f0, _c=28660464, _id=-2815, _a=0x7fffbdfabc20) at ./part.moc:166
#17 0x00007f8bbbe7a435 in DolphinPart::qt_metacall (this=0x1c069f0, _c=28660464, _id=-2815, _a=0x7fffbdfabc20) at ./dolphinpart.moc:120
#18 0x00007f8bd09317a7 in QMetaObject::activate (sender=0x1b552f0, m=<value optimized out>, local_signal_index=<value optimized out>, argv=0x7fffbdfabc20) at kernel/qobject.cpp:3280
#19 0x00007f8bd0931cef in QObject::destroyed (this=0x1c069f0, _t1=0x1b552f0) at .moc/release-shared/moc_qobject.cpp:149
#20 0x00007f8bd0932c57 in ~QObject (this=<value optimized out>, __in_chrg=<value optimized out>) at kernel/qobject.cpp:842
#21 0x00007f8bd13438ca in ~QWidget (this=0x1b552f0, __in_chrg=<value optimized out>) at kernel/qwidget.cpp:1579
#22 0x00007f8bbbc2e7ef in ~DolphinView (this=0x1b552f0, __in_chrg=<value optimized out>) at ../../../../apps/dolphin/src/dolphinview.cpp:168
#23 0x00007f8bd092b9ff in QObjectPrivate::deleteChildren (this=0x1b26fa0) at kernel/qobject.cpp:1957
#24 0x00007f8bd1343838 in ~QWidget (this=0x1a72300, __in_chrg=<value optimized out>) at kernel/qwidget.cpp:1559
#25 0x00007f8bd2154161 in ~KVBox (this=0x1c069f0, __in_chrg=<value optimized out>) at ../../kdeui/widgets/kvbox.cpp:29
#26 0x00007f8bd092b9ff in QObjectPrivate::deleteChildren (this=0x1b28bb0) at kernel/qobject.cpp:1957
#27 0x00007f8bd1343838 in ~QWidget (this=0x1b26f50, __in_chrg=<value optimized out>) at kernel/qwidget.cpp:1559
#28 0x00007f8bc2618d6a in ~ArkViewer (this=0x1b26f50, __in_chrg=<value optimized out>) at ../../../ark/part/arkviewer.cpp:57
#29 0x00007f8bd092b9ff in QObjectPrivate::deleteChildren (this=0x184a210) at kernel/qobject.cpp:1957
#30 0x00007f8bd1343838 in ~QWidget (this=0x18213c0, __in_chrg=<value optimized out>) at kernel/qwidget.cpp:1559
#31 0x00007f8bd1762338 in ~QSplitter (this=0x18213c0, __in_chrg=<value optimized out>) at widgets/qsplitter.cpp:1056
#32 0x00007f8bd2942acd in ~Part (this=0x181ac40, __vtt_parm=0x7f8bc282b838, __in_chrg=<value optimized out>) at ../../kparts/part.cpp:208
#33 0x00007f8bc260d61b in ~Part (this=0x181ac40, __in_chrg=<value optimized out>, __vtt_parm=<value optimized out>) at ../../../ark/part/part.cpp:133
#34 0x000000000040eceb in ~MainWindow (this=0x1793500, __in_chrg=<value optimized out>, __vtt_parm=<value optimized out>) at ../../../ark/app/mainwindow.cpp:74
#35 0x00007f8bd092b8a8 in QObject::event (this=0x1793500, e=0x1b552f0) at kernel/qobject.cpp:1202
#36 0x00007f8bd133dd2f in QWidget::event (this=0x1793500, event=0x1b3d210) at kernel/qwidget.cpp:8616
#37 0x00007f8bd171e7cb in QMainWindow::event (this=0x1793500, event=0x1b3d210) at widgets/qmainwindow.cpp:1417
#38 0x00007f8bd215a103 in KXmlGuiWindow::event (this=0x1c069f0, ev=0x1b552f0) at ../../kdeui/xmlgui/kxmlguiwindow.cpp:130
#39 0x00007f8bd12e8cdc in QApplicationPrivate::notify_helper (this=0x16ec950, receiver=0x1793500, e=0x1b3d210) at kernel/qapplication.cpp:4389
#40 0x00007f8bd12ee7cd in QApplication::notify (this=0x7fffbdfad220, receiver=0x1793500, e=0x1b3d210) at kernel/qapplication.cpp:4270
#41 0x00007f8bd203deb6 in KApplication::notify (this=0x7fffbdfad220, receiver=0x1793500, event=0x1b3d210) at ../../kdeui/kernel/kapplication.cpp:310
#42 0x00007f8bd0919a8c in QCoreApplication::notifyInternal (this=0x7fffbdfad220, receiver=0x1793500, event=0x1b3d210) at kernel/qcoreapplication.cpp:732
#43 0x00007f8bd091c9b2 in QCoreApplication::sendEvent (receiver=0x0, event_type=<value optimized out>, data=0x16d1a60) at ../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:215
#44 QCoreApplicationPrivate::sendPostedEvents (receiver=0x0, event_type=<value optimized out>, data=0x16d1a60) at kernel/qcoreapplication.cpp:1373
#45 0x00007f8bd0946043 in QCoreApplication::sendPostedEvents (s=<value optimized out>) at ../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:220
#46 postEventSourceDispatch (s=<value optimized out>) at kernel/qeventdispatcher_glib.cpp:276
#47 0x00007f8bcbe338c2 in g_main_context_dispatch () from /lib/libglib-2.0.so.0
#48 0x00007f8bcbe37748 in ?? () from /lib/libglib-2.0.so.0
#49 0x00007f8bcbe378fc in g_main_context_iteration () from /lib/libglib-2.0.so.0
#50 0x00007f8bd0945b83 in QEventDispatcherGlib::processEvents (this=0x16d1560, flags=<value optimized out>) at kernel/qeventdispatcher_glib.cpp:412
#51 0x00007f8bd139a7ee in QGuiEventDispatcherGlib::processEvents (this=0x1c069f0, flags=<value optimized out>) at kernel/qguieventdispatcher_glib.cpp:204
#52 0x00007f8bd09187b2 in QEventLoop::processEvents (this=<value optimized out>, flags=) at kernel/qeventloop.cpp:149
#53 0x00007f8bd0918b9c in QEventLoop::exec (this=0x7fffbdfad170, flags=) at kernel/qeventloop.cpp:201
#54 0x00007f8bd091cc4b in QCoreApplication::exec () at kernel/qcoreapplication.cpp:1009
#55 0x000000000040e0f7 in main (argc=<value optimized out>, argv=<value optimized out>) at ../../../ark/app/main.cpp:209

So what steps have you followed to reproduce the crash? Can you reproduce it at will now?

(In reply to comment #8)
> So what steps have you followed to reproduce the crash? Can you reproduce it at
> will now?

The spteps were the same I told before. It was a again a chromium theme (.CRX) which I was modifying and no, I can't reproduce it at will. It just happens sometimes but it happend twice with the same file... 

The problem is that I really don't remember which file was. But 100 % for sure it was a Chromium theme, there' no doubt about it.