Bug 196318 - Finished copy operation from CD to CIFS mounted drive, with permission change errors, and moving the dolphin window to another desktop!
Summary: Finished copy operation from CD to CIFS mounted drive, with permission change...
Status: RESOLVED DUPLICATE of bug 191589
Alias: None
Product: dolphin
Classification: Applications
Component: general (show other bugs)
Version: 16.12.2
Platform: Unlisted Binaries Linux
: NOR crash
Target Milestone: ---
Assignee: Peter Penz
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2009-06-13 12:17 UTC by Michael Liddle
Modified: 2009-07-17 21:33 UTC (History)
2 users (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Michael Liddle 2009-06-13 12:17:04 UTC
Application that crashed: dolphin
Version of the application: 1.2.80
KDE Version: 4.2.88 (KDE 4.2.88 (KDE 4.3 >= 20090527)) "release 127"
Qt Version: 4.5.1
Operating System: Linux 2.6.25.20-0.4-default i686

What I was doing when the application crashed:
A bit of a complicated set of circumstances sorry:

I was copying files from a CD to a CIFS mounted disk. During this copy there are a number of warnings about not being able to change permissions on the destination files (these are not really that useful as the destination file-system doesn't support permissions, and a user either knows this, or probably doesn't care).

At the end of the copy, I moved the dolphin window to another desktop via a key combination. At somepoint the dolphin wondow disappeared, and when I stopped the desktop move I dismissed the final message-box (about the permissions thing), and _then_ dolphin crashed.



 -- Backtrace:
Application: Dolphin (dolphin), signal: Segmentation fault
[Current thread is 0 (LWP 1948)]

Thread 2 (Thread 0xb37fab90 (LWP 4825)):
#0  0xffffe430 in __kernel_vsyscall ()
#1  0xb660af42 in pthread_cond_timedwait@@GLIBC_2.3.2 () from /lib/libpthread.so.0
#2  0xb2b596d1 in ?? () from /usr/lib/libxine.so.1

Thread 1 (Thread 0xb5c739a0 (LWP 1948)):
[KCrash Handler]
#6  0xb7e9428d in KIO::Slave::deref () from /usr/lib/libkio.so.5
#7  0xb7e94a7c in KIO::Slave::gotInput () from /usr/lib/libkio.so.5
#8  0xb7e96f03 in KIO::Slave::qt_metacall () from /usr/lib/libkio.so.5
#9  0xb6772d68 in QMetaObject::activate () from /usr/lib/libQtCore.so.4
#10 0xb67744f2 in QMetaObject::activate () from /usr/lib/libQtCore.so.4
#11 0xb7da0057 in KIO::Connection::readyRead () from /usr/lib/libkio.so.5
#12 0xb7da19c3 in ?? () from /usr/lib/libkio.so.5
#13 0xb7da1da6 in KIO::Connection::qt_metacall () from /usr/lib/libkio.so.5
#14 0xb676b95b in QMetaCallEvent::placeMetaCall () from /usr/lib/libQtCore.so.4
#15 0xb676d448 in QObject::event () from /usr/lib/libQtCore.so.4
#16 0xb697255c in QApplicationPrivate::notify_helper () from /usr/lib/libQtGui.so.4
#17 0xb697a88e in QApplication::notify () from /usr/lib/libQtGui.so.4
#18 0xb76b193d in KApplication::notify () from /usr/lib/libkdeui.so.5
#19 0xb675c9cb in QCoreApplication::notifyInternal () from /usr/lib/libQtCore.so.4
#20 0xb675d615 in QCoreApplicationPrivate::sendPostedEvents () from /usr/lib/libQtCore.so.4
#21 0xb675d80d in QCoreApplication::sendPostedEvents () from /usr/lib/libQtCore.so.4
#22 0xb678892f in ?? () from /usr/lib/libQtCore.so.4
#23 0xb5fb92f9 in g_main_context_dispatch () from /usr/lib/libglib-2.0.so.0
#24 0xb5fbc87b in ?? () from /usr/lib/libglib-2.0.so.0
#25 0xb5fbc9f8 in g_main_context_iteration () from /usr/lib/libglib-2.0.so.0
#26 0xb6788578 in QEventDispatcherGlib::processEvents () from /usr/lib/libQtCore.so.4
#27 0xb6a129f5 in ?? () from /usr/lib/libQtGui.so.4
#28 0xb675b00a in QEventLoop::processEvents () from /usr/lib/libQtCore.so.4
#29 0xb675b44a in QEventLoop::exec () from /usr/lib/libQtCore.so.4
#30 0xb675d8d9 in QCoreApplication::exec () from /usr/lib/libQtCore.so.4
#31 0xb69723d7 in QApplication::exec () from /usr/lib/libQtGui.so.4
#32 0x0807b02f in _start ()

Reported using DrKonqi
Comment 1 Dario Andres 2009-06-19 17:36:35 UTC
Looks related to the backtrace on bug 197090. Thanks
Comment 2 Frank Osterfeld 2009-07-17 21:33:29 UTC

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