Application: gwenview (2.4.3) KDE Platform Version: 4.4.5 (KDE 4.4.5) Qt Version: 4.6.2 Operating System: Linux 2.6.32-38-generic i686 Distribution: Ubuntu 10.04.4 LTS -- Information about the crash: Activity that caused crash: moving image files on a Windows XP shared USB drive across wireless network. OS in use: Kubuntu 10.04 LTS -- Backtrace: Application: Gwenview (gwenview), signal: Aborted [Current thread is 1 (Thread 0xb77cfaa0 (LWP 2839))] Thread 2 (Thread 0xb3d2bb70 (LWP 2996)): [KCrash Handler] #6 0x00dbd422 in __kernel_vsyscall () #7 0x045b5651 in raise () from /lib/tls/i686/cmov/libc.so.6 #8 0x045b8a82 in abort () from /lib/tls/i686/cmov/libc.so.6 #9 0x045ec49d in ?? () from /lib/tls/i686/cmov/libc.so.6 #10 0x045f6591 in ?? () from /lib/tls/i686/cmov/libc.so.6 #11 0x045f9395 in ?? () from /lib/tls/i686/cmov/libc.so.6 #12 0x045faf9c in malloc () from /lib/tls/i686/cmov/libc.so.6 #13 0x0057eb8d in qMalloc (size=1044) at global/qmalloc.cpp:55 #14 0x00586b66 in QByteArray (this=0xb3d2aabc, size=0, ch=0 '\000') at tools/qbytearray.cpp:1313 #15 0x0057b749 in qt_error_string (errorCode=22) at global/qglobal.cpp:2125 #16 0x005835ff in report_error (code=0, where=0x6ef66b "QMutex::lock", what=0x6ef649 "mutex lock") at thread/qmutex_unix.cpp:61 #17 0x00583780 in QMutexPrivate::wait (this=0x9b81028, timeout=-1) at thread/qmutex_unix.cpp:80 #18 0x0057f052 in QMutex::lock (this=0x9a8afc4) at thread/qmutex.cpp:167 #19 0x002643d3 in ?? () from /usr/lib/libgwenviewlib.so.4 #20 0x0058432e in QThreadPrivate::start (arg=0x9a8afc4) at thread/qthread_unix.cpp:248 #21 0x007c296e in start_thread () from /lib/tls/i686/cmov/libpthread.so.0 #22 0x04658a4e in clone () from /lib/tls/i686/cmov/libc.so.6 Thread 1 (Thread 0xb77cfaa0 (LWP 2839)): #0 0x00dbd422 in __kernel_vsyscall () #1 0x04665d33 in ?? () from /lib/tls/i686/cmov/libc.so.6 #2 0x045fc697 in ?? () from /lib/tls/i686/cmov/libc.so.6 Backtrace stopped: previous frame identical to this frame (corrupt stack?) Possible duplicates by query: bug 267202. Reported using DrKonqi
*** This bug has been marked as a duplicate of bug 267202 ***