I was trying to pinpoint one other bug and needed to do quite a bit of copying back and forth in .thunderbird folder. At some point things behaved weirdly enough that I checked and discovered that Ctrl+A, Ctrl+C, Ctrl+V I'd been using in Dolphin skipped some files silently. If I copy the same files using "cp -r * destination" there are no files skipped. After trying to repro multiple times it appears to be intermittent. I've got two kioclient logs, one with skipped files the other without. The one with skipped files seems to contain what looks like a crash stack: kioclient(22693)/kio (KIOJob) KIO::SimpleJob::~SimpleJob: Killing job KIO::SimpleJob(0x8d3a5e0) in destructor! "[ 0: /usr/lib/libkdecore.so.5(kRealBacktrace(int)+0x3e) [0xb645303e] 1: /usr/lib/libkio.so.5(KIO::SimpleJob::~SimpleJob()+0x96) [0xb75b2d86] 2: /usr/lib/libkio.so.5(KIO::ListJob::~ListJob()+0x26) [0xb75b31f6] 3: /usr/lib/libkio.so.5(KIO::ListJob::~ListJob()+0x1c) [0xb75b321c] 4: /usr/lib/i386-linux-gnu/libQtCore.so.4(qDeleteInEventHandler(QObject*)+0x13) [0xb61a0423] 5: /usr/lib/i386-linux-gnu/libQtCore.so.4(QObject::event(QEvent*)+0x230) [0xb61a65b0] 6: /usr/lib/i386-linux-gnu/libQtGui.so.4(QApplicationPrivate::notify_helper(QObject*, QEvent*)+0xa4) [0xb6765744] 7: /usr/lib/i386-linux-gnu/libQtGui.so.4(QApplication::notify(QObject*, QEvent*)+0x203) [0xb676c223] 8: /usr/lib/i386-linux-gnu/libQtCore.so.4(QCoreApplication::notifyInternal(QObject*, QEvent*)+0x7a) [0xb618ceda] 9: /usr/lib/i386-linux-gnu/libQtCore.so.4(QCoreApplicationPrivate::sendPostedEvents(QObject*, int, QThreadData*)+0x1dd) [0xb61906ad] 10: /usr/lib/i386-linux-gnu/libQtCore.so.4(QCoreApplication::sendPostedEvents(QObject*, int)+0x2c) [0xb6190bbc] 11: /usr/lib/i386-linux-gnu/libQtCore.so.4(+0x1a5f6e) [0xb61bcf6e] 12: /lib/i386-linux-gnu/libglib-2.0.so.0(g_main_context_dispatch+0x13e) [0xb554c83e] 13: /lib/i386-linux-gnu/libglib-2.0.so.0(+0x46be8) [0xb554cbe8] 14: /lib/i386-linux-gnu/libglib-2.0.so.0(g_main_context_iteration+0x38) [0xb554cca8] 15: /usr/lib/i386-linux-gnu/libQtCore.so.4(QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>)+0x5f) [0xb61bc8bf] 16: /usr/lib/i386-linux-gnu/libQtGui.so.4(+0x1ee32e) [0xb681a32e] 17: /usr/lib/i386-linux-gnu/libQtCore.so.4(QEventLoop::processEvents(QFlags<QEventLoop::ProcessEventsFlag>)+0x43) [0xb618b9f3] 18: /usr/lib/i386-linux-gnu/libQtCore.so.4(QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>)+0x179) [0xb618bd19] 19: /usr/lib/i386-linux-gnu/libQtCore.so.4(QCoreApplication::exec()+0x8e) [0xb619189e] 20: /usr/lib/i386-linux-gnu/libQtGui.so.4(QApplication::exec()+0x24) [0xb6763974] 21: kioclient() [0x804ba8d] 22: kioclient() [0x804c912] 23: kioclient() [0x804add6] 24: /lib/i386-linux-gnu/libc.so.6(__libc_start_main+0xf5) [0xb5d92905] 25: kioclient() [0x804b2cf] I don't get any crash notifications though. Will try to install debug libs to get more info. Is there a way to attach files here privately? I don't want logs public but could send them to an interested developer. This really ruins my trust in Dolphin and a simple "this was fixed in version x, please upgrade" would be useful too if it's not a bug in trunk. Although I am using Kubuntu 13.10 which is still supported and should be stable enough to not loose files like this. Reproducible: Sometimes
Actually it also happens on 4.13.0.
To check which files should be copied, you could do this: - Ctrl+A, Ctrl+C in source to copy - switch to a text editor, Ctrl+V there (then you have the list to copy) - switch back to destination folder, Ctrl+V there After everything is copied, compare the contents of the destination with the list of files in text editor. I am wondering, if the the clipboard doesn't contain all files, or if some of them are skipped while processing. Also, does killing Klipper make a difference?
While I originally noticed this bug by copying in Dolphin where clipboard could be involved the bug also manifested when using kioclient from command-line. This surely means that the problem isn't just the clipboard losing items?
Correct. If you already tested kioclient, the clipboard isn't to blame.
*** This bug has been marked as a duplicate of bug 162211 ***