Application: dolphin (17.08.1) Qt Version: 5.9.1 Frameworks Version: 5.38.0 Operating System: Linux 4.8.0-28-generic x86_64 Distribution: KDE neon User Edition 5.10 -- Information about the crash: - What I was doing when the application crashed: I was copying files to an Android phone over mtp kio. Some files did copy, but then Dolphin began to throw notices that it cannot copy one file, then another, and then it crashed The crash can be reproduced sometimes. -- Backtrace: Application: Dolphin (dolphin), signal: Segmentation fault Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". [Current thread is 1 (Thread 0x7f25d97b28c0 (LWP 14424))] Thread 4 (Thread 0x7f25b8b3f700 (LWP 14427)): #0 0x00007f25d91c870d in poll () at ../sysdeps/unix/syscall-template.S:84 #1 0x00007f25cdfe138c in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x00007f25cdfe149c in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x00007f25d3ed394b in QEventDispatcherGlib::processEvents (this=0x7f25b00008c0, flags=...) at kernel/qeventdispatcher_glib.cpp:425 #4 0x00007f25d3e7c7ca in QEventLoop::exec (this=this@entry=0x7f25b8b3ed00, flags=..., flags@entry=...) at kernel/qeventloop.cpp:212 #5 0x00007f25d3ca5cd4 in QThread::exec (this=<optimized out>) at thread/qthread.cpp:515 #6 0x00007f25d3caa989 in QThreadPrivate::start (arg=0x11e53e0) at thread/qthread_unix.cpp:368 #7 0x00007f25d00b56ba in start_thread (arg=0x7f25b8b3f700) at pthread_create.c:333 #8 0x00007f25d91d43dd in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 3 (Thread 0x7f25c236c700 (LWP 14426)): #0 0x00007f25d91c870d in poll () at ../sysdeps/unix/syscall-template.S:84 #1 0x00007f25cdfe138c in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x00007f25cdfe149c in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x00007f25d3ed394b in QEventDispatcherGlib::processEvents (this=0x7f25b40008c0, flags=...) at kernel/qeventdispatcher_glib.cpp:425 #4 0x00007f25d3e7c7ca in QEventLoop::exec (this=this@entry=0x7f25c236bcd0, flags=..., flags@entry=...) at kernel/qeventloop.cpp:212 #5 0x00007f25d3ca5cd4 in QThread::exec (this=<optimized out>) at thread/qthread.cpp:515 #6 0x00007f25d98a1b75 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5DBus.so.5 #7 0x00007f25d3caa989 in QThreadPrivate::start (arg=0x7f25d9917da0) at thread/qthread_unix.cpp:368 #8 0x00007f25d00b56ba in start_thread (arg=0x7f25c236c700) at pthread_create.c:333 #9 0x00007f25d91d43dd in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 2 (Thread 0x7f25c3d5c700 (LWP 14425)): #0 0x00007f25d91c870d in poll () at ../sysdeps/unix/syscall-template.S:84 #1 0x00007f25cd92ac62 in ?? () from /usr/lib/x86_64-linux-gnu/libxcb.so.1 #2 0x00007f25cd92c8d7 in xcb_wait_for_event () from /usr/lib/x86_64-linux-gnu/libxcb.so.1 #3 0x00007f25c62b4329 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5XcbQpa.so.5 #4 0x00007f25d3caa989 in QThreadPrivate::start (arg=0xb98320) at thread/qthread_unix.cpp:368 #5 0x00007f25d00b56ba in start_thread (arg=0x7f25c3d5c700) at pthread_create.c:333 #6 0x00007f25d91d43dd in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 1 (Thread 0x7f25d97b28c0 (LWP 14424)): [KCrash Handler] #6 KIO::Slave::deref (this=0x16320f0) at /workspace/build/src/core/slave.cpp:300 #7 0x00007f25d77328dd in KIO::Slave::gotInput (this=0x16320f0) at /workspace/build/src/core/slave.cpp:419 #8 0x00007f25d77bf965 in KIO::Slave::qt_static_metacall (_o=<optimized out>, _c=<optimized out>, _id=<optimized out>, _a=<optimized out>) at /workspace/build/obj-x86_64-linux-gnu/src/core/moc_slave.cpp:89 #9 0x00007f25d3eaac19 in QMetaObject::activate (sender=0x1792b80, signalOffset=<optimized out>, local_signal_index=<optimized out>, argv=<optimized out>) at kernel/qobject.cpp:3766 #10 0x00007f25d3eabc59 in QObject::event (this=0x1792b80, e=<optimized out>) at kernel/qobject.cpp:1246 #11 0x00007f25d47e63fc in QApplicationPrivate::notify_helper (this=<optimized out>, receiver=0x1792b80, e=0x19a67c0) at kernel/qapplication.cpp:3717 #12 0x00007f25d47ede07 in QApplication::notify (this=0x7ffda7eb8b30, receiver=0x1792b80, e=0x19a67c0) at kernel/qapplication.cpp:3476 #13 0x00007f25d3e7e798 in QCoreApplication::notifyInternal2 (receiver=0x1792b80, event=event@entry=0x19a67c0) at kernel/qcoreapplication.cpp:1018 #14 0x00007f25d3e80f7b in QCoreApplication::sendEvent (event=0x19a67c0, receiver=<optimized out>) at ../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:233 #15 QCoreApplicationPrivate::sendPostedEvents (receiver=receiver@entry=0x0, event_type=event_type@entry=0, data=0xb7dfd0) at kernel/qcoreapplication.cpp:1678 #16 0x00007f25d3e813e8 in QCoreApplication::sendPostedEvents (receiver=receiver@entry=0x0, event_type=event_type@entry=0) at kernel/qcoreapplication.cpp:1532 #17 0x00007f25d3ed4323 in postEventSourceDispatch (s=0xbbddd0) at kernel/qeventdispatcher_glib.cpp:276 #18 0x00007f25cdfe1197 in g_main_context_dispatch () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #19 0x00007f25cdfe13f0 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #20 0x00007f25cdfe149c in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #21 0x00007f25d3ed392f in QEventDispatcherGlib::processEvents (this=0xbc7510, flags=...) at kernel/qeventdispatcher_glib.cpp:423 #22 0x00007f25d3e7c7ca in QEventLoop::exec (this=this@entry=0x7ffda7eb89f0, flags=..., flags@entry=...) at kernel/qeventloop.cpp:212 #23 0x00007f25d3e85704 in QCoreApplication::exec () at kernel/qcoreapplication.cpp:1291 #24 0x00007f25d94da41a in kdemain (argc=2, argv=<optimized out>) at /workspace/build/src/main.cpp:163 #25 0x00007f25d90ed830 in __libc_start_main (main=0x4006b0 <main(int, char**)>, argc=2, argv=0x7ffda7eb8cb8, init=<optimized out>, fini=<optimized out>, rtld_fini=<optimized out>, stack_end=0x7ffda7eb8ca8) at ../csu/libc-start.c:291 #26 0x00000000004006e9 in _start () Possible duplicates by query: bug 384035, bug 382847, bug 381285, bug 381020, bug 379953. Reported using DrKonqi
*** Bug 392633 has been marked as a duplicate of this bug. ***
*** Bug 392993 has been marked as a duplicate of this bug. ***
As there have been various reports of such a crash happening, I'll set the status to CONFIRMED.
*** Bug 393897 has been marked as a duplicate of this bug. ***
It's a KDE Plasma big bug. It's reproducible in ALL DISTROS WITH PLASMA. If you use Gnome instead Plasma, the MTP connection works out of the box perfectly, like it should be. However, if you try to open the same way the same smartphone on Plasma, you will get an error. It's so clear that it's a Plasma fail that if you use Caja file manager in Plasma (it's not using KIO) you can open without issues you USB plugged smartphone. KDE should fix this severe bugs before adding more functionalities, cause we have now a pretty but unusable desktop. An angry KDE-Plasma user for years.
Hello Rafael, I do understand that you'd like to have this crash fixed (in fact, everybody would obviously like to resolve this issue), but KDE is a community where every developer can choose on their own what they want to work on. We cannot force a developer to fix a specific issue, because most programmers contributing for KDE do this in their free time and do not get paid for their work. A good way to show that you are interested in a fix is to vote for the bug report. You can do that on the right of the "Importance" field in the report. This will not guarantee anything, but can be an indicator for devs to find out which bugs to prioritize next. Please refrain from writing aggressive comments, they will likely do more harm than good. I'd still like to thank you for your continued use of KDE Plasma in the past and hope that you will continue to do so in the future despite this issue. Have a nice day, Julian
(In reply to Julian Schraner from comment #6) I'm sorry, Julian. I didn't pretend that my comment were "aggresive". This thread is not the place to begin a discussion about my experiencie with KDE-Plasma, so I only treated to be honest in my experiencie. I'm a fan of KDE applications like Krusader, Kate, Kdenlive, Krita and even I donated as a way to thank developers their work. But you must understand that if base system in not working as it should do at 2018, I can't make use of Plasma desktop as it should be. That's to say (and this is only an example, I could you tell you more examples) if it's knew that MTP protocol is *not* working in Plasma (and anyone can check it), why Plasma continues this non working applications (or KIO slave) to be disposable for final users? The experience for a new user trying to make work something that simply doesn't work is really maddening. Open source world is sometimes obscure. In Gnome and derivatives MTP works like a charm. Why KDE MTP developers can't take that source code and learn of it or adapt it or simply abandon that project till it really works? It's only my opinion and I'm sure many people will be agree, of course, but I took Linux with KDE as a professional platform many years ago and nowadays I'm frustrated cause things that was working today fails. I wish you understand my point of view. Anyway, thank you for your advice about the "Importance" field that I sometimes forget ;) Regards
Created attachment 114085 [details] New crash information added by DrKonqi dolphin (18.04.3) using Qt 5.11.1 - What I was doing when the application crashed: I attempt the copy some music folders to the device, the copy process doesn't seem to be starting so I attempt to unlock the device just to see if it's the cause, the copy process failed, then Dolphin crashed. -- Backtrace (Reduced): #7 0x00007f106c09bb7d in KIO::Slave::gotInput (this=0x2a86120) at /workspace/build/src/core/slave.cpp:419 #8 0x00007f106c12ce05 in KIO::Slave::qt_static_metacall (_o=<optimized out>, _c=<optimized out>, _id=<optimized out>, _a=<optimized out>) at /workspace/build/obj-x86_64-linux-gnu/src/core/moc_slave.cpp:89 [...] #10 0x00007f1067ccffb9 in QObject::event (this=0x2a6cbb0, e=<optimized out>) at kernel/qobject.cpp:1251 #11 0x00007f1068cff39c in QApplicationPrivate::notify_helper (this=<optimized out>, receiver=0x2a6cbb0, e=0x2a600b0) at kernel/qapplication.cpp:3727 #12 0x00007f1068d06ab0 in QApplication::notify (this=0x7ffe47f49690, receiver=0x2a6cbb0, e=0x2a600b0) at kernel/qapplication.cpp:3486
*** Bug 392355 has been marked as a duplicate of this bug. ***
*** Bug 388402 has been marked as a duplicate of this bug. ***
*** Bug 397846 has been marked as a duplicate of this bug. ***
Is anyone able to reproduce this issue with any version of Dolphin after 19.04? IIRC that's when the MTP handling was re-done, which seems to have eliminated this issue.
I have not encountered this bug for a while now. It must have been solved.
Maybe this issue doesn't happen, but MTP protocol still not working fine at 2020.
I don't know why there should be two implementation paths (different libraries?), but as a replacement solution, downloading pics from an attached phone via gwenview works A-OK.