Bug 476738 - Dolphin crashed when copying files into a folder which requires an overwrite of the existing files.
Summary: Dolphin crashed when copying files into a folder which requires an overwrite ...
Status: RESOLVED UNMAINTAINED
Alias: None
Product: dolphin
Classification: Applications
Component: general (show other bugs)
Version: 23.08.1
Platform: Kubuntu Linux
: NOR crash
Target Milestone: ---
Assignee: Dolphin Bug Assignee
URL:
Keywords: drkonqi
Depends on:
Blocks:
 
Reported: 2023-11-09 07:13 UTC by pablo2plato
Modified: 2023-11-11 18:06 UTC (History)
2 users (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments
attachment-2591087-0.html (1.04 KB, text/html)
2023-11-10 19:04 UTC, pablo2plato
Details

Note You need to log in before you can comment on or make changes to this bug.
Description pablo2plato 2023-11-09 07:13:19 UTC
Application: dolphin (23.08.1)

Qt Version: 5.15.10
Frameworks Version: 5.110.0
Operating System: Linux 6.5.0-10-generic x86_64
Windowing System: X11
Distribution: Ubuntu 23.10
DrKonqi: 5.27.8 [KCrashBackend]

-- Information about the crash:
Copying files from a folder an SSD to a folder on another SSD.
Using Drag-n-Drop method of copying files with CTRL key pressed.
Original and destination folders are in separate instances of Dolphin.
Copy requires existing files in destination folder be overwritten.
Dolphin crashes shortly after selecting "Apply to all" and pressing the Overwrite command button.
Dolphin does NOT crash if doing the same operation with no files in the destination folder, whether copy or move is executed.

The crash can be reproduced every time.

-- Backtrace:
Application: Dolphin (dolphin), signal: Segmentation fault

[KCrash Handler]
#4  0x00007fa13ba4a3e4 in KMountPoint::mountType() const () from /lib/x86_64-linux-gnu/libKF5KIOCore.so.5
#5  0x00007fa11c53f2de in ?? () from /usr/lib/x86_64-linux-gnu/qt5/plugins/kf5/kio/kio_file.so
#6  0x00007fa13b9d5d16 in KIO::SlaveBase::dispatch(int, QByteArray const&) () from /lib/x86_64-linux-gnu/libKF5KIOCore.so.5
#7  0x00007fa13b9d68e6 in KIO::SlaveBase::dispatchLoop() () from /lib/x86_64-linux-gnu/libKF5KIOCore.so.5
#8  0x00007fa13ba73904 in ?? () from /lib/x86_64-linux-gnu/libKF5KIOCore.so.5
#9  0x00007fa139adaeb1 in ?? () from /lib/x86_64-linux-gnu/libQt5Core.so.5
#10 0x00007fa139297ada in start_thread (arg=<optimized out>) at ./nptl/pthread_create.c:444
#11 0x00007fa13932847c in clone3 () at ../sysdeps/unix/sysv/linux/x86_64/clone3.S:78

Thread 9 (Thread 0x7fa1155fb6c0 (LWP 2401013) "KDirectoryConte"):
#1  0x00007fa137d6f3cf in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#2  0x00007fa137d11d20 in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#3  0x00007fa139d27dc6 in QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /lib/x86_64-linux-gnu/libQt5Core.so.5
#4  0x00007fa139ccb15b in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () from /lib/x86_64-linux-gnu/libQt5Core.so.5
#5  0x00007fa139ad9c52 in QThread::exec() () from /lib/x86_64-linux-gnu/libQt5Core.so.5
#6  0x00007fa139adaeb1 in ?? () from /lib/x86_64-linux-gnu/libQt5Core.so.5
#7  0x00007fa139297ada in start_thread (arg=<optimized out>) at ./nptl/pthread_create.c:444
#8  0x00007fa13932847c in clone3 () at ../sysdeps/unix/sysv/linux/x86_64/clone3.S:78

Thread 8 (Thread 0x7fa11e7fc6c0 (LWP 2401008) "dolphin"):
#1  __pselect (nfds=5, readfds=0x7fa11e7f3ac0, writefds=0x0, exceptfds=0x0, timeout=<optimized out>, sigmask=<optimized out>) at ../sysdeps/unix/sysv/linux/pselect.c:56
#2  0x00007fa13754cf87 in ?? () from /lib/x86_64-linux-gnu/libusbmuxd-2.0.so.6
#3  0x00007fa13754dc1b in ?? () from /lib/x86_64-linux-gnu/libusbmuxd-2.0.so.6
#4  0x00007fa139297ada in start_thread (arg=<optimized out>) at ./nptl/pthread_create.c:444
#5  0x00007fa13932847c in clone3 () at ../sysdeps/unix/sysv/linux/x86_64/clone3.S:78

Thread 7 (Thread 0x7fa11effd6c0 (LWP 2401007) "QDBusConnection"):
#1  0x00007fa137d6f3cf in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#2  0x00007fa137d11d20 in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#3  0x00007fa139d27dc6 in QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /lib/x86_64-linux-gnu/libQt5Core.so.5
#4  0x00007fa139ccb15b in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () from /lib/x86_64-linux-gnu/libQt5Core.so.5
#5  0x00007fa139ad9c52 in QThread::exec() () from /lib/x86_64-linux-gnu/libQt5Core.so.5
#6  0x00007fa13b0581bb in ?? () from /lib/x86_64-linux-gnu/libQt5DBus.so.5
#7  0x00007fa139adaeb1 in ?? () from /lib/x86_64-linux-gnu/libQt5Core.so.5
#8  0x00007fa139297ada in start_thread (arg=<optimized out>) at ./nptl/pthread_create.c:444
#9  0x00007fa13932847c in clone3 () at ../sysdeps/unix/sysv/linux/x86_64/clone3.S:78

Thread 6 (Thread 0x7fa11f7fe6c0 (LWP 2401004) "dolphin:shlo0"):
#1  __futex_abstimed_wait_common (cancel=true, private=0, abstime=0x0, clockid=0, expected=0, futex_word=0x55698f91bff8) at ./nptl/futex-internal.c:87
#2  __GI___futex_abstimed_wait_cancelable64 (futex_word=futex_word@entry=0x55698f91bff8, expected=expected@entry=0, clockid=clockid@entry=0, abstime=abstime@entry=0x0, private=private@entry=0) at ./nptl/futex-internal.c:139
#3  0x00007fa1392969fe in __pthread_cond_wait_common (abstime=0x0, clockid=0, mutex=0x55698f91bfa8, cond=0x55698f91bfd0) at ./nptl/pthread_cond_wait.c:503
#4  ___pthread_cond_wait (cond=0x55698f91bfd0, mutex=0x55698f91bfa8) at ./nptl/pthread_cond_wait.c:627
#5  0x00007fa13131ed2d in ?? () from /usr/lib/x86_64-linux-gnu/dri/radeonsi_dri.so
#6  0x00007fa1312cf1bb in ?? () from /usr/lib/x86_64-linux-gnu/dri/radeonsi_dri.so
#7  0x00007fa13131ec5b in ?? () from /usr/lib/x86_64-linux-gnu/dri/radeonsi_dri.so
#8  0x00007fa139297ada in start_thread (arg=<optimized out>) at ./nptl/pthread_create.c:444
#9  0x00007fa13932847c in clone3 () at ../sysdeps/unix/sysv/linux/x86_64/clone3.S:78

Thread 5 (Thread 0x7fa11ffff6c0 (LWP 2401003) "dolphin:sh0"):
#1  __futex_abstimed_wait_common (cancel=true, private=0, abstime=0x0, clockid=0, expected=0, futex_word=0x55698f91be50) at ./nptl/futex-internal.c:87
#2  __GI___futex_abstimed_wait_cancelable64 (futex_word=futex_word@entry=0x55698f91be50, expected=expected@entry=0, clockid=clockid@entry=0, abstime=abstime@entry=0x0, private=private@entry=0) at ./nptl/futex-internal.c:139
#3  0x00007fa1392969fe in __pthread_cond_wait_common (abstime=0x0, clockid=0, mutex=0x55698f91be00, cond=0x55698f91be28) at ./nptl/pthread_cond_wait.c:503
#4  ___pthread_cond_wait (cond=0x55698f91be28, mutex=0x55698f91be00) at ./nptl/pthread_cond_wait.c:627
#5  0x00007fa13131ed2d in ?? () from /usr/lib/x86_64-linux-gnu/dri/radeonsi_dri.so
#6  0x00007fa1312cf1bb in ?? () from /usr/lib/x86_64-linux-gnu/dri/radeonsi_dri.so
#7  0x00007fa13131ec5b in ?? () from /usr/lib/x86_64-linux-gnu/dri/radeonsi_dri.so
#8  0x00007fa139297ada in start_thread (arg=<optimized out>) at ./nptl/pthread_create.c:444
#9  0x00007fa13932847c in clone3 () at ../sysdeps/unix/sysv/linux/x86_64/clone3.S:78

Thread 4 (Thread 0x7fa124dff6c0 (LWP 2401002) "dolphin:disk$0"):
#1  __futex_abstimed_wait_common (cancel=true, private=0, abstime=0x0, clockid=0, expected=0, futex_word=0x55698f983170) at ./nptl/futex-internal.c:87
#2  __GI___futex_abstimed_wait_cancelable64 (futex_word=futex_word@entry=0x55698f983170, expected=expected@entry=0, clockid=clockid@entry=0, abstime=abstime@entry=0x0, private=private@entry=0) at ./nptl/futex-internal.c:139
#3  0x00007fa1392969fe in __pthread_cond_wait_common (abstime=0x0, clockid=0, mutex=0x55698f983120, cond=0x55698f983148) at ./nptl/pthread_cond_wait.c:503
#4  ___pthread_cond_wait (cond=0x55698f983148, mutex=0x55698f983120) at ./nptl/pthread_cond_wait.c:627
#5  0x00007fa13131ed2d in ?? () from /usr/lib/x86_64-linux-gnu/dri/radeonsi_dri.so
#6  0x00007fa1312cf1bb in ?? () from /usr/lib/x86_64-linux-gnu/dri/radeonsi_dri.so
#7  0x00007fa13131ec5b in ?? () from /usr/lib/x86_64-linux-gnu/dri/radeonsi_dri.so
#8  0x00007fa139297ada in start_thread (arg=<optimized out>) at ./nptl/pthread_create.c:444
#9  0x00007fa13932847c in clone3 () at ../sysdeps/unix/sysv/linux/x86_64/clone3.S:78

Thread 3 (Thread 0x7fa130fa76c0 (LWP 2401001) "dolphin:cs0"):
#1  __futex_abstimed_wait_common (cancel=true, private=0, abstime=0x0, clockid=0, expected=0, futex_word=0x55698f90fca0) at ./nptl/futex-internal.c:87
#2  __GI___futex_abstimed_wait_cancelable64 (futex_word=futex_word@entry=0x55698f90fca0, expected=expected@entry=0, clockid=clockid@entry=0, abstime=abstime@entry=0x0, private=private@entry=0) at ./nptl/futex-internal.c:139
#3  0x00007fa1392969fe in __pthread_cond_wait_common (abstime=0x0, clockid=0, mutex=0x55698f90fc50, cond=0x55698f90fc78) at ./nptl/pthread_cond_wait.c:503
#4  ___pthread_cond_wait (cond=0x55698f90fc78, mutex=0x55698f90fc50) at ./nptl/pthread_cond_wait.c:627
#5  0x00007fa13131ed2d in ?? () from /usr/lib/x86_64-linux-gnu/dri/radeonsi_dri.so
#6  0x00007fa1312cf1bb in ?? () from /usr/lib/x86_64-linux-gnu/dri/radeonsi_dri.so
#7  0x00007fa13131ec5b in ?? () from /usr/lib/x86_64-linux-gnu/dri/radeonsi_dri.so
#8  0x00007fa139297ada in start_thread (arg=<optimized out>) at ./nptl/pthread_create.c:444
#9  0x00007fa13932847c in clone3 () at ../sysdeps/unix/sysv/linux/x86_64/clone3.S:78

Thread 2 (Thread 0x7fa133e846c0 (LWP 2401000) "QXcbEventQueue"):
#1  0x00007fa138aa486a in ?? () from /lib/x86_64-linux-gnu/libxcb.so.1
#2  0x00007fa138aa628c in xcb_wait_for_event () from /lib/x86_64-linux-gnu/libxcb.so.1
#3  0x00007fa133ef8eb8 in ?? () from /lib/x86_64-linux-gnu/libQt5XcbQpa.so.5
#4  0x00007fa139adaeb1 in ?? () from /lib/x86_64-linux-gnu/libQt5Core.so.5
#5  0x00007fa139297ada in start_thread (arg=<optimized out>) at ./nptl/pthread_create.c:444
#6  0x00007fa13932847c in clone3 () at ../sysdeps/unix/sysv/linux/x86_64/clone3.S:78

Thread 1 (Thread 0x7fa134711540 (LWP 2400998) "dolphin"):
#1  0x00007fa137d6f3cf in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#2  0x00007fa137d11d20 in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#3  0x00007fa139d27dc6 in QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /lib/x86_64-linux-gnu/libQt5Core.so.5
#4  0x00007fa139ccb15b in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () from /lib/x86_64-linux-gnu/libQt5Core.so.5
#5  0x00007fa139cd3904 in QCoreApplication::exec() () from /lib/x86_64-linux-gnu/libQt5Core.so.5
#6  0x000055698d7e33f4 in ?? ()
#7  0x00007fa1392280d0 in __libc_start_call_main (main=main@entry=0x55698d7e0c60, argc=argc@entry=1, argv=argv@entry=0x7ffdc6d09918) at ../sysdeps/nptl/libc_start_call_main.h:58
#8  0x00007fa139228189 in __libc_start_main_impl (main=0x55698d7e0c60, argc=1, argv=0x7ffdc6d09918, init=<optimized out>, fini=<optimized out>, rtld_fini=<optimized out>, stack_end=0x7ffdc6d09908) at ../csu/libc-start.c:360
#9  0x000055698d7e3b65 in ?? ()
[Inferior 1 (process 2400998) detached]

The reporter indicates this bug may be a duplicate of or related to bug 54445, bug 342677, bug 355853, bug 402646, bug 420179, bug 434157, bug 435688, bug 437153, bug 438072, bug 445527, bug 448114, bug 454290, bug 454619, bug 459433, bug 467674, bug 469411, bug 469458, bug 469528, bug 474451, bug 474521, bug 474555, bug 474909.

Reported using DrKonqi
Comment 1 fanzhuyifan 2023-11-10 03:44:42 UTC
Is this reproducible on the latest verssion? Seems to be a duplicate of https://bugs.kde.org/show_bug.cgi?id=474451, which has been fixed in frameworks 5.111.
Comment 2 pablo2plato 2023-11-10 16:23:38 UTC
(In reply to fanzhuyifan from comment #1)
> Is this reproducible on the latest verssion? Seems to be a duplicate of
> https://bugs.kde.org/show_bug.cgi?id=474451, which has been fixed in
> frameworks 5.111.

If you will note, these incidents are occurring with Frameworks v5.110.0 installed. Therefore, yes, it is reproducible with the latest version. And, I just now verified that the bug is still happening.
Comment 3 fanzhuyifan 2023-11-10 17:00:07 UTC
(In reply to pablo2plato from comment #2)
> If you will note, these incidents are occurring with Frameworks v5.110.0
> installed. Therefore, yes, it is reproducible with the latest version. And,
> I just now verified that the bug is still happening.

You mean the bug is still happening with frameworks 5.111?
Comment 4 pablo2plato 2023-11-10 19:04:05 UTC
Created attachment 163020 [details]
attachment-2591087-0.html

Yes, they are.


On Fri, Nov 10, 2023 at 11:00 <bugzilla_noreply@kde.org> wrote:

> https://bugs.kde.org/show_bug.cgi?id=476738
>
> --- Comment #3 from fanzhuyifan@gmail.com ---
> (In reply to pablo2plato from comment #2)
> > If you will note, these incidents are occurring with Frameworks v5.110.0
> > installed. Therefore, yes, it is reproducible with the latest version.
> And,
> > I just now verified that the bug is still happening.
>
> You mean the bug is still happening with frameworks 5.111?
>
> --
> You are receiving this mail because:
> You reported the bug.
Comment 5 fanzhuyifan 2023-11-10 19:45:31 UTC
Interesting... Unfortunately I only have single-SSD systems, and I can't reproduce this issue when the source and destination are on different mount points of the same SSD. 
Does this issue ever occur for you when source and destination are on the same SSD? 
Was there anything particular about the mount point structure/file system you noticed that was causing the issue? 
Does this issue happen no matter what file you copy?
Comment 6 fanzhuyifan 2023-11-10 19:51:16 UTC
Also, just to be 100% sure, since this really seems like a duplicate of a fixed bug, how did you install frameworks 5.111? If you are using the latest ones provided by Ubuntu, I think they are still on 5.110.
Comment 7 pablo2plato 2023-11-11 17:39:16 UTC
(In reply to fanzhuyifan from comment #6)
> Also, just to be 100% sure, since this really seems like a duplicate of a
> fixed bug, how did you install frameworks 5.111? If you are using the latest
> ones provided by Ubuntu, I think they are still on 5.110.0.

I made a mistake in reading my KDE Frameworks version, which is 5.110.0. I am sorry for that confusion and I will await release of 5.111.0
Just to clarify the events I've experienced:
I have Kubuntu 23.10 installed via the pushed upgrade process.
I checked and the crash occurs from SSD#1 to SSD#1 for Drag-and-Drop COPY w/ Overwrite ONLY, unless the target is empty.  the Drag-and-Drop MOVE w/ Overwrite worked.
Drag-and-Drop COPY or MOVE, w/ or w/out Keyboard Shortcut from SSD#1 to SSD#2 crashes all the time, unless the target is empty.
Drag-and-Drop COPY or MOVE, w/ or w/out Keyboard Shortcut from SSD#1 to HDD#1 crashes all the time, unless the target is empty.
Comment 8 fanzhuyifan 2023-11-11 18:03:06 UTC
(In reply to pablo2plato from comment #7)
> I made a mistake in reading my KDE Frameworks version, which is 5.110.0. I
> am sorry for that confusion and I will await release of 5.111.0

No worries! I am closing this bug report now. Feel free to reopen this if you still encounter this issue on 5.111.
Comment 9 fanzhuyifan 2023-11-11 18:06:18 UTC
Very likely duplicate of https://bugs.kde.org/show_bug.cgi?id=474451