Summary: | Dolphin crashes after failing to copy files to Android phone over mtp | ||
---|---|---|---|
Product: | [Applications] dolphin | Reporter: | Donatas Glodenis <dg> |
Component: | general | Assignee: | Dolphin Bug Assignee <dolphin-bugs-null> |
Status: | RESOLVED WORKSFORME | ||
Severity: | crash | CC: | bughunt, Buo.Ren.Lin, elvis.angelaccio, jan.anonim, kde.org, kde, mail, nate, notuxius, rafael.linux.user, usef_62 |
Priority: | NOR | Keywords: | drkonqi |
Version: | 17.08.1 | ||
Target Milestone: | --- | ||
Platform: | Neon | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: | ||
Attachments: | New crash information added by DrKonqi |
Description
Donatas Glodenis
2017-09-22 19:27:50 UTC
*** 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. |