Discussion:
[dolphin] [Bug 400874] New: Dolphin crashed on file transfer
Add Reply
b***@kde.org
2018-11-09 16:04:31 UTC
Reply
Permalink
https://bugs.kde.org/show_bug.cgi?id=400874

Bug ID: 400874
Summary: Dolphin crashed on file transfer
Product: dolphin
Version: unspecified
Platform: Ubuntu Packages
OS: Linux
Status: REPORTED
Keywords: drkonqi
Severity: crash
Priority: NOR
Component: general
Assignee: dolphin-bugs-***@kde.org
Reporter: ***@hotmail.com
CC: ***@kde.org
Target Milestone: ---

Application: dolphin (16.04.3)

Qt Version: 5.6.1
Frameworks Version: 5.36.0
Operating System: Linux 4.15.0-38-generic x86_64
Distribution: Ubuntu 16.04.5 LTS

-- Information about the crash:
- What I was doing when the application crashed:
This is a duplicate as I filed a bug report of the same crash a day or two ago,
but the crash report agent failed to find my duplicate.

What happened was I opened Dolphin and opened the location where I want the
files copied and the files from the memory card(s) to their respective save
folders, a short time elapsed and then Dolphin crashed.

The crash can be reproduced every time.

-- 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 0x7f37cb6468c0 (LWP 25717))]

Thread 6 (Thread 0x7f37a04f5700 (LWP 25722)):
#0 0x00007f37cb04e27d in read () at ../sysdeps/unix/syscall-template.S:84
#1 0x00007f37c1493790 in g_wakeup_acknowledge (__nbytes=16,
__buf=0x7f37a04f4af0, __fd=<optimized out>) at
/usr/include/x86_64-linux-gnu/bits/unistd.h:44
#2 0x00007f37c1493790 in g_wakeup_acknowledge (wakeup=0x7f37a80025a0) at
/build/glib2.0-7ZsPUq/glib2.0-2.48.2/./glib/gwakeup.c:210
#3 0x00007f37c144fe74 in g_main_context_check
(context=***@entry=0x7f3798000990, max_priority=2147483647,
fds=***@entry=0x7f3798002e20, n_fds=***@entry=1) at
/build/glib2.0-7ZsPUq/glib2.0-2.48.2/./glib/gmain.c:3632
#4 0x00007f37c1450330 in g_main_context_iterate
(context=***@entry=0x7f3798000990, block=***@entry=1,
dispatch=***@entry=1, self=<optimized out>) at
/build/glib2.0-7ZsPUq/glib2.0-2.48.2/./glib/gmain.c:3837
#5 0x00007f37c145049c in g_main_context_iteration (context=0x7f3798000990,
may_block=***@entry=1) at
/build/glib2.0-7ZsPUq/glib2.0-2.48.2/./glib/gmain.c:3901
#6 0x00007f37c5d6937b in
QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>)
(this=0x7f37980008c0, flags=...) at kernel/qeventdispatcher_glib.cpp:419
#7 0x00007f37c5d11ffa in
QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>)
(this=***@entry=0x7f37a04f4d00, flags=..., ***@entry=...) at
kernel/qeventloop.cpp:204
#8 0x00007f37c5b3a9e4 in QThread::exec() (this=<optimized out>) at
thread/qthread.cpp:500
#9 0x00007f37c5b3f808 in QThreadPrivate::start(void*) (arg=0x2a476f0) at
thread/qthread_unix.cpp:341
#10 0x00007f37c1fdc6ba in start_thread (arg=0x7f37a04f5700) at
pthread_create.c:333
#11 0x00007f37cb05e41d in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 5 (Thread 0x7f37a419f700 (LWP 25721)):
#0 0x00007f37c1fe2360 in pthread_cond_wait@@GLIBC_2.3.2 () at
../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185
#1 0x00007f37adf9970b in () at /usr/lib/x86_64-linux-gnu/dri/r600_dri.so
#2 0x00007f37adf99427 in () at /usr/lib/x86_64-linux-gnu/dri/r600_dri.so
#3 0x00007f37c1fdc6ba in start_thread (arg=0x7f37a419f700) at
pthread_create.c:333
#4 0x00007f37cb05e41d in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 4 (Thread 0x7f37acb60700 (LWP 25720)):
#0 0x00007f37c1fe2360 in pthread_cond_wait@@GLIBC_2.3.2 () at
../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185
#1 0x00007f37adf9970b in () at /usr/lib/x86_64-linux-gnu/dri/r600_dri.so
#2 0x00007f37adf99427 in () at /usr/lib/x86_64-linux-gnu/dri/r600_dri.so
#3 0x00007f37c1fdc6ba in start_thread (arg=0x7f37acb60700) at
pthread_create.c:333
#4 0x00007f37cb05e41d in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 3 (Thread 0x7f37afd73700 (LWP 25719)):
#0 0x00007f37cb05274d in poll () at ../sysdeps/unix/syscall-template.S:84
#1 0x00007f37c145038c in g_main_context_iterate (priority=2147483647, n_fds=1,
fds=0x7f37a8015230, timeout=<optimized out>, context=0x7f37a8000990) at
/build/glib2.0-7ZsPUq/glib2.0-2.48.2/./glib/gmain.c:4135
#2 0x00007f37c145038c in g_main_context_iterate
(context=***@entry=0x7f37a8000990, block=***@entry=1,
dispatch=***@entry=1, self=<optimized out>) at
/build/glib2.0-7ZsPUq/glib2.0-2.48.2/./glib/gmain.c:3835
#3 0x00007f37c145049c in g_main_context_iteration (context=0x7f37a8000990,
may_block=***@entry=1) at
/build/glib2.0-7ZsPUq/glib2.0-2.48.2/./glib/gmain.c:3901
#4 0x00007f37c5d6937b in
QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>)
(this=0x7f37a80008c0, flags=...) at kernel/qeventdispatcher_glib.cpp:419
#5 0x00007f37c5d11ffa in
QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>)
(this=***@entry=0x7f37afd72cd0, flags=..., ***@entry=...) at
kernel/qeventloop.cpp:204
#6 0x00007f37c5b3a9e4 in QThread::exec() (this=***@entry=0x7f37cb7a8d40
<(anonymous namespace)::Q_QGS__q_manager::innerFunction()::holder>) at
thread/qthread.cpp:500
#7 0x00007f37cb735515 in QDBusConnectionManager::run() (this=0x7f37cb7a8d40
<(anonymous namespace)::Q_QGS__q_manager::innerFunction()::holder>) at
qdbusconnection.cpp:189
#8 0x00007f37c5b3f808 in QThreadPrivate::start(void*) (arg=0x7f37cb7a8d40
<(anonymous namespace)::Q_QGS__q_manager::innerFunction()::holder>) at
thread/qthread_unix.cpp:341
#9 0x00007f37c1fdc6ba in start_thread (arg=0x7f37afd73700) at
pthread_create.c:333
#10 0x00007f37cb05e41d in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 2 (Thread 0x7f37b550a700 (LWP 25718)):
#0 0x00007f37cb05274d in poll () at ../sysdeps/unix/syscall-template.S:84
#1 0x00007f37bf3d3c62 in () at /usr/lib/x86_64-linux-gnu/libxcb.so.1
#2 0x00007f37bf3d58d7 in xcb_wait_for_event () at
/usr/lib/x86_64-linux-gnu/libxcb.so.1
#3 0x00007f37b7a60d29 in QXcbEventReader::run() (this=0x258d650) at
qxcbconnection.cpp:1325
#4 0x00007f37c5b3f808 in QThreadPrivate::start(void*) (arg=0x258d650) at
thread/qthread_unix.cpp:341
#5 0x00007f37c1fdc6ba in start_thread (arg=0x7f37b550a700) at
pthread_create.c:333
#6 0x00007f37cb05e41d in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 1 (Thread 0x7f37cb6468c0 (LWP 25717)):
[KCrash Handler]
#6 0x00007f37caca8248 in () at
/usr/lib/x86_64-linux-gnu/libdolphinprivate.so.5
#7 0x00007f37c5ba0227 in QHashData::detach_helper(void (*)(QHashData::Node*,
void*), void (*)(QHashData::Node*), int, int) (this=0x3356a70,
node_duplicate=0x7f37caca8240, node_delete=<optimized out>, nodeSize=<optimized
out>, nodeAlign=8) at tools/qhash.cpp:503
#8 0x00007f37caca922a in () at
/usr/lib/x86_64-linux-gnu/libdolphinprivate.so.5
#9 0x00007f37caca93d1 in () at
/usr/lib/x86_64-linux-gnu/libdolphinprivate.so.5
#10 0x00007f37caca2ecb in KFileItemModelRolesUpdater::updateChangedItems() ()
at /usr/lib/x86_64-linux-gnu/libdolphinprivate.so.5
#11 0x00007f37caca3c10 in
KFileItemModelRolesUpdater::resolveRecentlyChangedItems() () at
/usr/lib/x86_64-linux-gnu/libdolphinprivate.so.5
#12 0x00007f37c5d40c24 in QMetaObject::activate(QObject*, int, int, void**)
(a=0x7ffea3eefcc0, r=0x30cc260, this=<optimized out>) at
../../include/QtCore/../../src/corelib/kernel/qobject_impl.h:124
#13 0x00007f37c5d40c24 in QMetaObject::activate(QObject*, int, int, void**)
(sender=***@entry=0x30cef10, signalOffset=<optimized out>,
local_signal_index=***@entry=0, argv=***@entry=0x0) at
kernel/qobject.cpp:3715
#14 0x00007f37c5d411b7 in QMetaObject::activate(QObject*, QMetaObject const*,
int, void**) (sender=***@entry=0x30cef10, m=***@entry=0x7f37c5f5c720
<QTimer::staticMetaObject>, local_signal_index=***@entry=0,
argv=***@entry=0x0) at kernel/qobject.cpp:3595
#15 0x00007f37c5dbbe80 in QTimer::timeout(QTimer::QPrivateSignal)
(this=***@entry=0x30cef10) at .moc/moc_qtimer.cpp:198
#16 0x00007f37c5d4d0b8 in QTimer::timerEvent(QTimerEvent*) (this=0x30cef10,
e=<optimized out>) at kernel/qtimer.cpp:247
#17 0x00007f37c5d416d3 in QObject::event(QEvent*) (this=0x30cef10, e=<optimized
out>) at kernel/qobject.cpp:1278
#18 0x00007f37c6649afc in QApplicationPrivate::notify_helper(QObject*, QEvent*)
(this=<optimized out>, receiver=0x30cef10, e=0x7ffea3eeffd0) at
kernel/qapplication.cpp:3804
#19 0x00007f37c664f036 in QApplication::notify(QObject*, QEvent*)
(this=0x7ffea3ef0360, receiver=0x30cef10, e=0x7ffea3eeffd0) at
kernel/qapplication.cpp:3561
#20 0x00007f37c5d142a8 in QCoreApplication::notifyInternal2(QObject*, QEvent*)
(receiver=0x30cef10, event=***@entry=0x7ffea3eeffd0) at
kernel/qcoreapplication.cpp:1015
#21 0x00007f37c5d6824e in QTimerInfoList::activateTimers()
(event=0x7ffea3eeffd0, receiver=<optimized out>) at
../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:225
#22 0x00007f37c5d6824e in QTimerInfoList::activateTimers() (this=0x25c5550) at
kernel/qtimerinfo_unix.cpp:637
#23 0x00007f37c5d68781 in timerSourceDispatch(GSource*, GSourceFunc, gpointer)
(source=<optimized out>) at kernel/qeventdispatcher_glib.cpp:176
#24 0x00007f37c1450197 in g_main_context_dispatch (context=0x7f37b00016f0) at
/build/glib2.0-7ZsPUq/glib2.0-2.48.2/./glib/gmain.c:3154
#25 0x00007f37c1450197 in g_main_context_dispatch
(context=***@entry=0x7f37b00016f0) at
/build/glib2.0-7ZsPUq/glib2.0-2.48.2/./glib/gmain.c:3769
#26 0x00007f37c14503f0 in g_main_context_iterate
(context=***@entry=0x7f37b00016f0, block=***@entry=1,
dispatch=***@entry=1, self=<optimized out>) at
/build/glib2.0-7ZsPUq/glib2.0-2.48.2/./glib/gmain.c:3840
#27 0x00007f37c145049c in g_main_context_iteration (context=0x7f37b00016f0,
may_block=***@entry=1) at
/build/glib2.0-7ZsPUq/glib2.0-2.48.2/./glib/gmain.c:3901
#28 0x00007f37c5d6935f in
QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>)
(this=0x25bbaf0, flags=...) at kernel/qeventdispatcher_glib.cpp:417
#29 0x00007f37c5d11ffa in
QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>)
(this=***@entry=0x7ffea3ef0220, flags=..., ***@entry=...) at
kernel/qeventloop.cpp:204
#30 0x00007f37c5d1a6bc in QCoreApplication::exec() () at
kernel/qcoreapplication.cpp:1285
#31 0x00007f37cb380b89 in kdemain () at
/usr/lib/x86_64-linux-gnu/libkdeinit5_dolphin.so
#32 0x00007f37caf77830 in __libc_start_main (main=0x4006c0, argc=2,
argv=0x7ffea3ef04e8, init=<optimized out>, fini=<optimized out>,
rtld_fini=<optimized out>, stack_end=0x7ffea3ef04d8) at ../csu/libc-start.c:291
#33 0x00000000004006f9 in _start ()

Reported using DrKonqi
--
You are receiving this mail because:
You are watching all bug changes.
b***@kde.org
2018-11-09 16:18:21 UTC
Reply
Permalink
https://bugs.kde.org/show_bug.cgi?id=400874

--- Comment #1 from ***@hotmail.com ---
Dolphin version 16.04.3
I also searched for the first crash report I filed but it seems it did not go
through though there's a crash report with an identical title, 'Dolphin crashed
on file transfer' but it's not.

Also, the crash happened while I was transferring the files from the front cam
AND the rear cam at the SAME time.
--
You are receiving this mail because:
You are watching all bug changes.
Elvis Angelaccio
2018-11-10 10:57:51 UTC
Reply
Permalink
https://bugs.kde.org/show_bug.cgi?id=400874

Elvis Angelaccio <***@kde.org> changed:

What |Removed |Added
----------------------------------------------------------------------------
Status|REPORTED |NEEDSINFO
Resolution|--- |BACKTRACE

--- Comment #2 from Elvis Angelaccio <***@kde.org> ---
If you can reproduce the crash, please install debug symbols for dolphin and
post another backtrace here. Thanks!
--
You are receiving this mail because:
You are watching all bug changes.
b***@kde.org
2018-11-10 11:11:28 UTC
Reply
Permalink
https://bugs.kde.org/show_bug.cgi?id=400874

***@hotmail.com changed:

What |Removed |Added
----------------------------------------------------------------------------
Resolution|BACKTRACE |FIXED
CC| |***@hotmail.com

--- Comment #3 from ***@hotmail.com ---
I have tried yo install dolphin-dbg but I encounter a problem.

The following packages have unmet dependencies.
dolphin-dbg : Depends: dolphin (= 4:15.12.3-0ubuntu1) but
4:16.04.3-0ubuntu2.1~ubuntu16.04~ppa1 is to be installed
E: Unable to correct problems, you have held broken packages.

I have tried via Synaptic Package Manager AND Konsole, I get the same error.I
don't know how to install the correct version of dbg.
--
You are receiving this mail because:
You are watching all bug changes.
Christoph Feck
2018-11-12 13:49:38 UTC
Reply
Permalink
https://bugs.kde.org/show_bug.cgi?id=400874

--- Comment #4 from Christoph Feck <***@kde.org> ---
Was it your intention to mark this bug as 'FIXED'?
--
You are receiving this mail because:
You are watching all bug changes.
b***@kde.org
2018-11-12 15:47:18 UTC
Reply
Permalink
https://bugs.kde.org/show_bug.cgi?id=400874

--- Comment #5 from ***@hotmail.com ---
(In reply to Christoph Feck from comment #4)
Post by Christoph Feck
Was it your intention to mark this bug as 'FIXED'?
No, I don't know what to select, could you please select one...
--
You are receiving this mail because:
You are watching all bug changes.
Christoph Feck
2018-11-13 17:26:00 UTC
Reply
Permalink
https://bugs.kde.org/show_bug.cgi?id=400874

Christoph Feck <***@kde.org> changed:

What |Removed |Added
----------------------------------------------------------------------------
Resolution|FIXED |BACKTRACE

--- Comment #6 from Christoph Feck <***@kde.org> ---
Please ask for help in a forum of your distribution how to install debug symbol
packages.
--
You are receiving this mail because:
You are watching all bug changes.
b***@kde.org
2018-11-22 01:55:48 UTC
Reply
Permalink
https://bugs.kde.org/show_bug.cgi?id=400874

--- Comment #7 from ***@hotmail.com ---
I have posted a question requesting help installing the dbg for dolphin 16.04
and apparently there is no dbg file available for it, so I am unable to provide
a crash report with any deeper crash level info.
--
You are receiving this mail because:
You are watching all bug changes.
b***@kde.org
2018-11-22 13:09:09 UTC
Reply
Permalink
https://bugs.kde.org/show_bug.cgi?id=400874

--- Comment #8 from ***@hotmail.com ---
I have posted a question in the forum on this domain, the other one I was
referring to was on linux uk forums.
--
You are receiving this mail because:
You are watching all bug changes.
Bug Janitor Service
2018-12-07 03:44:13 UTC
Reply
Permalink
https://bugs.kde.org/show_bug.cgi?id=400874

--- Comment #9 from Bug Janitor Service <bug-***@kde.org> ---
Dear Bug Submitter,

This bug has been in NEEDSINFO status with no change for at least
15 days. Please provide the requested information as soon as
possible and set the bug status as REPORTED. Due to regular bug
tracker maintenance, if the bug is still in NEEDSINFO status with
no change in 30 days the bug will be closed as RESOLVED > WORKSFORME
due to lack of needed information.

For more information about our bug triaging procedures please read the
wiki located here:
https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

If you have already provided the requested information, please
mark the bug as REPORTED so that the KDE team knows that the bug is
ready to be confirmed.

Thank you for helping us make KDE software even better for everyone!
--
You are receiving this mail because:
You are watching all bug changes.
b***@kde.org
2018-12-07 22:29:42 UTC
Reply
Permalink
https://bugs.kde.org/show_bug.cgi?id=400874

--- Comment #10 from ***@hotmail.com ---
I am unable to locate a dbg file for Dolphin 16.04 and as far as I can
understand, there is no dbg for 16.04, so unless you can prove otherwise, there
is nothing else I can do to improve on the crash report.
Who actually wrote dolphin and how can I contact them to find out more about
dolphin 16.04 and the lack of a dbg file.
--
You are receiving this mail because:
You are watching all bug changes.
b***@kde.org
2018-12-08 14:48:05 UTC
Reply
Permalink
https://bugs.kde.org/show_bug.cgi?id=400874

--- Comment #11 from ***@hotmail.com ---
You can recreate the crash yourself as I've figured out why it's doing it.
I reckon it's because it's trying to write from two folders off one location to
2 folders on the destination drive.
'front' & 'rear' from a USB stick to 'front' & 'rear' to an internal drive at
the same time causes the crash, yet doing one at a time does not cause a crash.
--
You are receiving this mail because:
You are watching all bug changes.
Elvis Angelaccio
2018-12-08 15:32:27 UTC
Reply
Permalink
https://bugs.kde.org/show_bug.cgi?id=400874

--- Comment #12 from Elvis Angelaccio <***@kde.org> ---
(In reply to ponchorat1968 from comment #11)
Post by b***@kde.org
'front' & 'rear' from a USB stick to 'front' & 'rear' to an internal drive
at the same time causes the crash
Can you explain better what are you doing? Are you copying two folders called
"front" and "rear" ?
--
You are receiving this mail because:
You are watching all bug changes.
b***@kde.org
2018-12-10 15:13:46 UTC
Reply
Permalink
https://bugs.kde.org/show_bug.cgi?id=400874

--- Comment #13 from ***@hotmail.com ---
Yes, I have two folders labelled 'front' & 'rear' inside another one labelled
'carcam'(on the internal hard drive), and I am copying the contents (video
files) from 2 car cameras into their respective folders on the internal had
drive.

Another note: I have Dolphin in split window mode where the destination folders
(front & rear) are both open and in one tab, I have the car cameras open in
split window mode in another tab,also with front & rear showing (whatever the
folder names be, e.g. '/nextbase/dcim/recordings').
--
You are receiving this mail because:
You are watching all bug changes.
Loading...