krusader fails epically while unpacking zip files (KIO::FileCopyJob::~FileCopyJob ; ~KJob)

Bug #393124 reported by LimCore on 2009-06-28
12
This bug affects 2 people
Affects Status Importance Assigned to Milestone
krusader
Unknown
Unknown
krusader (Ubuntu)
Undecided
Unassigned

Bug Description

When unpacking .zip files I get error about protocol dying, and sometimes a crash.
krusader 2.0~svn6078-1ubuntu1 on Ubuntu 8.10 amd64

I unpack by:

1. entering the .zip file in right tab
2. copy from the right tab to left tab (where my home dir was opened)

I am getting error:
"The process for the krarc protocol died unexpectedly "
around 50% of the tries (other times it worked fully, even when it failed it seem the file was unpacked correctly, only the error message was there)

After trying several time (last time I managed to get a confirmation dialog to overwrite file, and afair I deleted the file)
it crashed also:

To crash:
unpack once and get the error about dying protocol, so that a .part file is there
unpack again, then a confirmation box appears to overwrite
ignore the box and click in the krusader main windo
close the confirmation box

This backtrace appears to be of no use.
This is probably because your packages are built in a way which prevents creation of proper backtraces, or the stack frame was seriously corrupted in the crash.

[Thread debugging using libthread_db enabled]
[New Thread 0x7fdf063ba6f0 (LWP 7208)]
[New Thread 0x4098a950 (LWP 7216)]
0x00007fdf028c46e1 in nanosleep () from /lib/libc.so.6
[Current thread is 0 (LWP 7208)]

Thread 2 (Thread 0x4098a950 (LWP 7216)):
#0 0x00007fdf028fb4b2 in select () from /lib/libc.so.6
#1 0x00007fdf045b8006 in ?? () from /usr/lib/libQtCore.so.4
#2 0x00007fdf044ef362 in ?? () from /usr/lib/libQtCore.so.4
#3 0x00007fdf008b33ea in start_thread () from /lib/libpthread.so.0
#4 0x00007fdf02902cbd in clone () from /lib/libc.so.6
#5 0x0000000000000000 in ?? ()

Thread 1 (Thread 0x7fdf063ba6f0 (LWP 7208)):
#0 0x00007fdf028c46e1 in nanosleep () from /lib/libc.so.6
#1 0x00007fdf028c4507 in sleep () from /lib/libc.so.6
#2 0x00007fdf057c2b0f in ?? () from /usr/lib/libkdeui.so.5
#3 0x00007fdf057c344a in KCrash::defaultCrashHandler () from /usr/lib/libkdeui.so.5
#4 <signal handler called>
#5 0x0000000000000020 in ?? ()
#6 0x00000000017d1d30 in ?? ()
#7 0x00007fdf05e7860d in KJob::~KJob () from /usr/lib/libkdecore.so.5
#8 0x00007fdf049abde7 in KIO::FileCopyJob::~FileCopyJob () from /usr/lib/libkio.so.5
#9 0x00007fdf045e6dc5 in QObject::event () from /usr/lib/libQtCore.so.4
#10 0x00007fdf03889c3d in QApplicationPrivate::notify_helper () from /usr/lib/libQtGui.so.4
#11 0x00007fdf038919ba in QApplication::notify () from /usr/lib/libQtGui.so.4
#12 0x00007fdf0576013b in KApplication::notify () from /usr/lib/libkdeui.so.5
#13 0x00007fdf045d7d61 in QCoreApplication::notifyInternal () from /usr/lib/libQtCore.so.4
#14 0x00007fdf045d89fa in QCoreApplicationPrivate::sendPostedEvents () from /usr/lib/libQtCore.so.4
#15 0x00007fdf046004d3 in ?? () from /usr/lib/libQtCore.so.4
#16 0x00007fdeff97bd5b in g_main_context_dispatch () from /usr/lib/libglib-2.0.so.0
#17 0x00007fdeff97f52d in ?? () from /usr/lib/libglib-2.0.so.0
#18 0x00007fdeff97f6eb in g_main_context_iteration () from /usr/lib/libglib-2.0.so.0
#19 0x00007fdf0460015f in QEventDispatcherGlib::processEvents () from /usr/lib/libQtCore.so.4
#20 0x00007fdf0391ba6f in ?? () from /usr/lib/libQtGui.so.4
#21 0x00007fdf045d6682 in QEventLoop::processEvents () from /usr/lib/libQtCore.so.4
#22 0x00007fdf045d680d in QEventLoop::exec () from /usr/lib/libQtCore.so.4
#23 0x00007fdf045d8cbd in QCoreApplication::exec () from /usr/lib/libQtCore.so.4
#24 0x0000000000458c51 in main (argc=4, argv=0x7fff0e3f7268) at /build/buildd/krusader-2.0~svn6078/krusader/main.cpp:264
#0 0x00007fdf028c46e1 in nanosleep () from /lib/libc.so.6

LimCore (limcore) wrote :
Changed in krusader (Ubuntu):
status: New → Confirmed
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.