Bug 367890 - Dolphin crashed when moving many files in parallel from a external HD to athe internal SSD
Summary: Dolphin crashed when moving many files in parallel from a external HD to athe...
Status: RESOLVED DUPLICATE of bug 368287
Alias: None
Product: dolphin
Classification: Applications
Component: general (show other bugs)
Version: 15.12.3
Platform: Ubuntu Linux
: NOR crash
Target Milestone: ---
Assignee: Dolphin Bug Assignee
URL:
Keywords: drkonqi
: 352315 370956 371026 383954 386154 386399 396533 398318 399353 400031 400830 401292 402431 403908 405449 (view as bug list)
Depends on:
Blocks:
 
Reported: 2016-08-27 10:51 UTC by Xavier Besnard
Modified: 2019-03-19 05:26 UTC (History)
17 users (show)

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:


Attachments
New crash information added by DrKonqi (8.33 KB, text/plain)
2018-10-16 20:18 UTC, Zsombor
Details
attachment-13836-0.html (1.72 KB, text/html)
2019-02-09 16:12 UTC, spaginni2000
Details
attachment-22212-0.html (1.68 KB, text/html)
2019-02-10 00:09 UTC, spaginni2000
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Xavier Besnard 2016-08-27 10:51:57 UTC
Application: dolphin (15.12.3)

Qt Version: 5.6.1
Frameworks Version: 5.24.0
Operating System: Linux 4.4.0-34-generic x86_64
Distribution: Ubuntu Yakkety Yak (development branch)

-- Information about the crash:
- What I was doing when the application crashed:

 I was moving many files in parallel from a external HD to at he internal SSD. Thenn Dolphin crashed.

Configuration: 
Kubuntu 16.10 Yakkety (Development) updated dayly.
ASUS Zenbook UX305CA

Dolphin restarted and I completed my multiple moves without problems.

-- Backtrace:
Application: Dolphin (dolphin), signal: Aborted
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
[Current thread is 1 (Thread 0x7fed4bc5bd40 (LWP 27745))]

Thread 3 (Thread 0x7fed26fcc700 (LWP 27748)):
#0  0x00007fed4b67610d in poll () at ../sysdeps/unix/syscall-template.S:84
#1  0x00007fed41ce19b6 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#2  0x00007fed41ce1acc in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#3  0x00007fed463821cb in QEventDispatcherGlib::processEvents (this=0x7fed200008c0, flags=...) at kernel/qeventdispatcher_glib.cpp:419
#4  0x00007fed4632ae4a in QEventLoop::exec (this=this@entry=0x7fed26fcbd00, flags=..., flags@entry=...) at kernel/qeventloop.cpp:204
#5  0x00007fed461539e4 in QThread::exec (this=<optimized out>) at thread/qthread.cpp:500
#6  0x00007fed46158808 in QThreadPrivate::start (arg=0x19c1130) at thread/qthread_unix.cpp:341
#7  0x00007fed4286f70a in start_thread (arg=0x7fed26fcc700) at pthread_create.c:333
#8  0x00007fed4b6820ff in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:105

Thread 2 (Thread 0x7fed2ffff700 (LWP 27747)):
#0  0x00007fed41ce0e53 in g_main_context_prepare () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#1  0x00007fed41ce18db in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#2  0x00007fed41ce1acc in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#3  0x00007fed463821cb in QEventDispatcherGlib::processEvents (this=0x7fed280008c0, flags=...) at kernel/qeventdispatcher_glib.cpp:419
#4  0x00007fed4632ae4a in QEventLoop::exec (this=this@entry=0x7fed2fffecd0, flags=..., flags@entry=...) at kernel/qeventloop.cpp:204
#5  0x00007fed461539e4 in QThread::exec (this=this@entry=0x7fed4bdbad40 <(anonymous namespace)::Q_QGS__q_manager::innerFunction()::holder>) at thread/qthread.cpp:500
#6  0x00007fed4bd47515 in QDBusConnectionManager::run (this=0x7fed4bdbad40 <(anonymous namespace)::Q_QGS__q_manager::innerFunction()::holder>) at qdbusconnection.cpp:189
#7  0x00007fed46158808 in QThreadPrivate::start (arg=0x7fed4bdbad40 <(anonymous namespace)::Q_QGS__q_manager::innerFunction()::holder>) at thread/qthread_unix.cpp:341
#8  0x00007fed4286f70a in start_thread (arg=0x7fed2ffff700) at pthread_create.c:333
#9  0x00007fed4b6820ff in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:105

Thread 1 (Thread 0x7fed4bc5bd40 (LWP 27745)):
[KCrash Handler]
#6  __GI_raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/raise.c:58
#7  0x00007fed4b5b13ea in __GI_abort () at abort.c:89
#8  0x00007fed4b5a7c47 in __assert_fail_base (fmt=<optimized out>, assertion=assertion@entry=0x7fed497b839f "!q->hasSubjobs()", file=file@entry=0x7fed497b9488 "/build/kio-rOipto/kio-5.24.0/src/core/copyjob.cpp", line=line@entry=1336, function=function@entry=0x7fed497b8740 "void KIO::CopyJobPrivate::slotResultCopyingFiles(KJob*)") at assert.c:92
#9  0x00007fed4b5a7cf2 in __GI___assert_fail (assertion=0x7fed497b839f "!q->hasSubjobs()", file=0x7fed497b9488 "/build/kio-rOipto/kio-5.24.0/src/core/copyjob.cpp", line=1336, function=0x7fed497b8740 "void KIO::CopyJobPrivate::slotResultCopyingFiles(KJob*)") at assert.c:101
#10 0x00007fed496f9876 in ?? () from /usr/lib/x86_64-linux-gnu/libKF5KIOCore.so.5
#11 0x00007fed463599c1 in QMetaObject::activate (sender=0x2a5b2a0, signalOffset=<optimized out>, local_signal_index=<optimized out>, argv=<optimized out>) at kernel/qobject.cpp:3730
#12 0x00007fed478b1312 in KJob::result(KJob*, KJob::QPrivateSignal) () from /usr/lib/x86_64-linux-gnu/libKF5CoreAddons.so.5
#13 0x00007fed478b2c51 in KJob::finishJob(bool) () from /usr/lib/x86_64-linux-gnu/libKF5CoreAddons.so.5
#14 0x00007fed497409b9 in KIO::FileCopyJob::slotResult(KJob*) () from /usr/lib/x86_64-linux-gnu/libKF5KIOCore.so.5
#15 0x00007fed497418f8 in ?? () from /usr/lib/x86_64-linux-gnu/libKF5KIOCore.so.5
#16 0x00007fed463599c1 in QMetaObject::activate (sender=0x2f74f20, signalOffset=<optimized out>, local_signal_index=<optimized out>, argv=<optimized out>) at kernel/qobject.cpp:3730
#17 0x00007fed478b1312 in KJob::result(KJob*, KJob::QPrivateSignal) () from /usr/lib/x86_64-linux-gnu/libKF5CoreAddons.so.5
#18 0x00007fed478b2c51 in KJob::finishJob(bool) () from /usr/lib/x86_64-linux-gnu/libKF5CoreAddons.so.5
#19 0x00007fed4974b372 in KIO::SimpleJob::slotFinished() () from /usr/lib/x86_64-linux-gnu/libKF5KIOCore.so.5
#20 0x00007fed463599c1 in QMetaObject::activate (sender=0x2f04ea0, signalOffset=<optimized out>, local_signal_index=<optimized out>, argv=<optimized out>) at kernel/qobject.cpp:3730
#21 0x00007fed49725231 in KIO::SlaveInterface::dispatch(int, QByteArray const&) () from /usr/lib/x86_64-linux-gnu/libKF5KIOCore.so.5
#22 0x00007fed49723857 in KIO::SlaveInterface::dispatch() () from /usr/lib/x86_64-linux-gnu/libKF5KIOCore.so.5
#23 0x00007fed49728b01 in KIO::Slave::gotInput() () from /usr/lib/x86_64-linux-gnu/libKF5KIOCore.so.5
#24 0x00007fed497b39b5 in ?? () from /usr/lib/x86_64-linux-gnu/libKF5KIOCore.so.5
#25 0x00007fed463599c1 in QMetaObject::activate (sender=0x2b23ed0, signalOffset=<optimized out>, local_signal_index=<optimized out>, argv=<optimized out>) at kernel/qobject.cpp:3730
#26 0x00007fed496c6ad0 in ?? () from /usr/lib/x86_64-linux-gnu/libKF5KIOCore.so.5
#27 0x00007fed4635a569 in QObject::event (this=0x2b23ed0, e=<optimized out>) at kernel/qobject.cpp:1256
#28 0x00007fed46e78afc in QApplicationPrivate::notify_helper (this=<optimized out>, receiver=0x2b23ed0, e=0x2f13450) at kernel/qapplication.cpp:3804
#29 0x00007fed46e7e036 in QApplication::notify (this=0x7ffdf1f99270, receiver=0x2b23ed0, e=0x2f13450) at kernel/qapplication.cpp:3561
#30 0x00007fed4632d0f8 in QCoreApplication::notifyInternal2 (receiver=0x2b23ed0, event=event@entry=0x2f13450) at kernel/qcoreapplication.cpp:1015
#31 0x00007fed4632efba in QCoreApplication::sendEvent (event=0x2f13450, receiver=<optimized out>) at ../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:225
#32 QCoreApplicationPrivate::sendPostedEvents (receiver=receiver@entry=0x0, event_type=event_type@entry=0, data=0x147b8a0) at kernel/qcoreapplication.cpp:1650
#33 0x00007fed4632f478 in QCoreApplication::sendPostedEvents (receiver=receiver@entry=0x0, event_type=event_type@entry=0) at kernel/qcoreapplication.cpp:1508
#34 0x00007fed46381da3 in postEventSourceDispatch (s=0x14c3480) at kernel/qeventdispatcher_glib.cpp:270
#35 0x00007fed41ce17b7 in g_main_context_dispatch () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#36 0x00007fed41ce1a20 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#37 0x00007fed41ce1acc in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#38 0x00007fed463821af in QEventDispatcherGlib::processEvents (this=0x14c0910, flags=...) at kernel/qeventdispatcher_glib.cpp:417
#39 0x00007fed4632ae4a in QEventLoop::exec (this=this@entry=0x7ffdf1f99140, flags=..., flags@entry=...) at kernel/qeventloop.cpp:204
#40 0x00007fed4633350c in QCoreApplication::exec () at kernel/qcoreapplication.cpp:1285
#41 0x00007fed4688883c in QGuiApplication::exec () at kernel/qguiapplication.cpp:1607
#42 0x00007fed46e75ac5 in QApplication::exec () at kernel/qapplication.cpp:2979
#43 0x00007fed4b99ee2b in kdemain (argc=1, argv=<optimized out>) at /build/dolphin-HvGmRr/dolphin-15.12.3/src/main.cpp:150
#44 0x00007fed4b59a3f1 in __libc_start_main (main=0x400710 <main(int, char**)>, argc=1, argv=0x7ffdf1f993f8, init=<optimized out>, fini=<optimized out>, rtld_fini=<optimized out>, stack_end=0x7ffdf1f993e8) at ../csu/libc-start.c:291
#45 0x0000000000400749 in _start ()

Possible duplicates by query: bug 359869.

Reported using DrKonqi
Comment 1 Elvis Angelaccio 2016-12-24 15:20:53 UTC
*** Bug 371026 has been marked as a duplicate of this bug. ***
Comment 2 Elvis Angelaccio 2016-12-24 15:21:13 UTC
*** Bug 370956 has been marked as a duplicate of this bug. ***
Comment 3 Elvis Angelaccio 2017-08-24 14:25:25 UTC
*** Bug 383954 has been marked as a duplicate of this bug. ***
Comment 4 Christoph Feck 2017-10-24 23:49:40 UTC
*** Bug 386154 has been marked as a duplicate of this bug. ***
Comment 5 Elvis Angelaccio 2017-11-01 11:49:50 UTC
*** Bug 386399 has been marked as a duplicate of this bug. ***
Comment 6 Julian Steinmann 2018-06-10 18:06:06 UTC
All these reports were made with a now very old Dolphin version (16.04 or older). Can anybody confirm that such a crash has happened to them with a newer version of Dolphin? Thanks!
Comment 7 Julian Steinmann 2018-06-28 19:22:28 UTC
It'd be great if we could confirm the status of this bug. Has somebody been able to reproduce the crash with a newer version of Dolphin?
Comment 8 Xavier Besnard 2018-06-29 07:25:33 UTC
Noto reproduced at this time under KDE  5.12.5, with Kubuntu 18.10 
Cosmic updated daily.

Le 28/06/2018 à 21:22, Julian Schraner a écrit :
> https://bugs.kde.org/show_bug.cgi?id=367890
>
> --- Comment #7 from Julian Schraner <juliquadrat@gmail.com> ---
> It'd be great if we could confirm the status of this bug. Has somebody been
> able to reproduce the crash with a newer version of Dolphin?
>
Comment 9 Julian Steinmann 2018-07-13 20:00:16 UTC
Thanks @xavier for your response; as nobody else confirmed that this bug does still occur, I'll close the report. Please reopen if you can still reproduce this issue with a newer version of Dolphin. Thanks!
Comment 10 Nate Graham 2018-08-24 17:30:16 UTC
*** Bug 396533 has been marked as a duplicate of this bug. ***
Comment 11 Elvis Angelaccio 2018-10-07 20:17:33 UTC
*** Bug 398318 has been marked as a duplicate of this bug. ***
Comment 12 Elvis Angelaccio 2018-10-07 20:17:41 UTC
*** Bug 399353 has been marked as a duplicate of this bug. ***
Comment 13 Zsombor 2018-10-16 20:18:10 UTC
Created attachment 115688 [details]
New crash information added by DrKonqi

dolphin (17.04.3) using Qt 5.9.1

- What I was doing when the application crashed:

Tried to move git folders between HDDs when it crashed

-- Backtrace (Reduced):
#6  __GI_raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/raise.c:51
#7  0x00007fbce63d3f5d in __GI_abort () at abort.c:90
#8  0x00007fbce63c9f17 in __assert_fail_base (fmt=<optimized out>, assertion=assertion@entry=0x7fbce45d0cf0 "!q->hasSubjobs()", file=file@entry=0x7fbce45d2090 "/build/kio-bOrDXU/kio-5.38.0/src/core/copyjob.cpp", line=line@entry=1373, function=function@entry=0x7fbce45d1320 "void KIO::CopyJobPrivate::slotResultCopyingFiles(KJob*)") at assert.c:92
#9  0x00007fbce63c9fc2 in __GI___assert_fail (assertion=0x7fbce45d0cf0 "!q->hasSubjobs()", file=0x7fbce45d2090 "/build/kio-bOrDXU/kio-5.38.0/src/core/copyjob.cpp", line=1373, function=0x7fbce45d1320 "void KIO::CopyJobPrivate::slotResultCopyingFiles(KJob*)") at assert.c:101
[...]
#11 0x00007fbce4512acb in KIO::CopyJob::slotResult(KJob*) () from /usr/lib/x86_64-linux-gnu/libKF5KIOCore.so.5
Comment 14 Elvis Angelaccio 2018-10-20 09:34:56 UTC
*** Bug 400031 has been marked as a duplicate of this bug. ***
Comment 15 Elvis Angelaccio 2018-11-10 11:01:17 UTC
*** Bug 400830 has been marked as a duplicate of this bug. ***
Comment 16 Elvis Angelaccio 2018-11-21 22:12:28 UTC
*** Bug 401292 has been marked as a duplicate of this bug. ***
Comment 17 Elvis Angelaccio 2018-12-23 16:40:18 UTC
*** Bug 352315 has been marked as a duplicate of this bug. ***
Comment 18 Elvis Angelaccio 2018-12-23 16:40:37 UTC
*** Bug 402431 has been marked as a duplicate of this bug. ***
Comment 19 Christoph Feck 2019-01-17 03:22:47 UTC
*** Bug 402431 has been marked as a duplicate of this bug. ***
Comment 20 Elvis Angelaccio 2019-02-05 21:17:28 UTC
*** Bug 403908 has been marked as a duplicate of this bug. ***
Comment 21 My1 2019-02-05 22:13:56 UTC
so if this has been fixed (status does say resolved fixed), in what version has it been fixed, so we can somehow get the update or at least know when we got a fixed version, because apparently this thing still does appear in the wild.
Comment 22 Julian Steinmann 2019-02-09 15:27:41 UTC
(In reply to My1 from comment #21)
> so if this has been fixed (status does say resolved fixed), in what version
> has it been fixed, so we can somehow get the update or at least know when we
> got a fixed version, because apparently this thing still does appear in the
> wild.

I do not know the exact version that this bug was fixed in, but nobody has been able to reproduce it with a version newer than 17.12.3. If you still encounter this crash with a version newer than 17.12.3 (preferably 18.12.x, as this is the newest version right now), please reopen this report. Thanks!
Comment 23 spaginni2000 2019-02-09 16:12:21 UTC
Created attachment 117947 [details]
attachment-13836-0.html

I reported it happen on 18.04, i moved my OS because it keeps happeing.
baloo also just DOES no want to work. If you install debug, everything goes
to hell.

Will Plaza
Mobile Communication ~

On Feb 9, 2019 10:27 AM, "Julian Schraner" <bugzilla_noreply@kde.org> wrote:

https://bugs.kde.org/show_bug.cgi?id=367890

--- Comment #22 from Julian Schraner <mail@xyquadrat.ch> ---
(In reply to My1 from comment #21)

> so if this has been fixed (status does say resolved fixed), in what
version
> has it been fixed, so we can somehow get the update or at least know when
we
> got a fixed version, because apparently this thing still does appear in
the
> wild.

I do not know the exact version that this bug was fixed in, but nobody has
been
able to reproduce it with a version newer than 17.12.3. If you still
encounter
this crash with a version newer than 17.12.3 (preferably 18.12.x, as this is
the newest version right now), please reopen this report. Thanks!
Comment 24 Julian Steinmann 2019-02-09 21:00:50 UTC
Ah, I've just seen that there is indeed a bug report with the same crash cause that happens with Dolphin 18.04. Would it be possible for you to install Dolphin 18.12 on your current system and try if you can reproduce the bug? We will of course reopen this report if the crash is not fixed, but it'd be great to have confirmation that the bug does still exist.

For your baloo-related problems: You might want to seek help on #kde or alternatively disable baloo temporarily with 'balooctl disable'. Hope that helps!

(In reply to spaginni2000 from comment #23)
> Created attachment 117947 [details]
> attachment-13836-0.html
> 
> I reported it happen on 18.04, i moved my OS because it keeps happeing.
> baloo also just DOES no want to work. If you install debug, everything goes
> to hell.
> 
> Will Plaza
> Mobile Communication ~
Comment 25 My1 2019-02-10 00:05:50 UTC
(In reply to Julian Schraner from comment #22)
> (In reply to My1 from comment #21)
> > so if this has been fixed (status does say resolved fixed), in what version
> > has it been fixed, so we can somehow get the update or at least know when we
> > got a fixed version, because apparently this thing still does appear in the
> > wild.
> 
> I do not know the exact version that this bug was fixed in, but nobody has
> been able to reproduce it with a version newer than 17.12.3. If you still
> encounter this crash with a version newer than 17.12.3 (preferably 18.12.x,
> as this is the newest version right now), please reopen this report. Thanks!

the question is are the newer versions even stable, or still in beta, and if they are stable why are they not released?
the Software center still reports the latest version as "4:17.12.3-0ubuntu1" in my kubuntu 18.04.
and then how am I supposed to get a newer dolphin? is there a .deb lying around somehwere?
Comment 26 spaginni2000 2019-02-10 00:09:32 UTC
Created attachment 117958 [details]
attachment-22212-0.html

I'll try it when I can.

On Sat, Feb 9, 2019, 4:00 PM Julian Schraner <bugzilla_noreply@kde.org
wrote:

> https://bugs.kde.org/show_bug.cgi?id=367890
>
> --- Comment #24 from Julian Schraner <mail@xyquadrat.ch> ---
> Ah, I've just seen that there is indeed a bug report with the same crash
> cause
> that happens with Dolphin 18.04. Would it be possible for you to install
> Dolphin 18.12 on your current system and try if you can reproduce the bug?
> We
> will of course reopen this report if the crash is not fixed, but it'd be
> great
> to have confirmation that the bug does still exist.
>
> For your baloo-related problems: You might want to seek help on #kde or
> alternatively disable baloo temporarily with 'balooctl disable'. Hope that
> helps!
>
> (In reply to spaginni2000 from comment #23)
> > Created attachment 117947 [details]
> > attachment-13836-0.html
> >
> > I reported it happen on 18.04, i moved my OS because it keeps happeing.
> > baloo also just DOES no want to work. If you install debug, everything
> goes
> > to hell.
> >
> > Will Plaza
> > Mobile Communication ~
>
> --
> You are receiving this mail because:
> You are on the CC list for the bug.
Comment 27 Elvis Angelaccio 2019-03-17 12:21:43 UTC
*** Bug 405449 has been marked as a duplicate of this bug. ***
Comment 28 Elvis Angelaccio 2019-03-17 12:25:21 UTC
@anyone still seeing a crash with this stacktrace: please try again with Frameworks 5.56, which should have a fix for this issue.

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