Bug 412618 - Crash when copying directory with the same name
Summary: Crash when copying directory with the same name
Status: RESOLVED WORKSFORME
Alias: None
Product: dolphin
Classification: Applications
Component: general (show other bugs)
Version: 18.12.3
Platform: Ubuntu Linux
: NOR crash
Target Milestone: ---
Assignee: Dolphin Bug Assignee
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2019-10-04 20:45 UTC by pac.dlfisher
Modified: 2019-12-25 04:33 UTC (History)
3 users (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments
Developer Information from Dolphin's crash report. (18.92 KB, text/plain)
2019-10-04 20:45 UTC, pac.dlfisher
Details
Useless bug report (18.92 KB, text/plain)
2019-10-21 05:25 UTC, pac.dlfisher
Details

Note You need to log in before you can comment on or make changes to this bug.
Description pac.dlfisher 2019-10-04 20:45:25 UTC
Created attachment 123020 [details]
Developer Information from Dolphin's crash report.

File structure
foo/bar
var/foo/bar

Dolphin's version of: `$cp -r foo var` tells the user that the folder already exists.
You are suggested to provided a new name but the options to skip, write into, and cancel exists.

If the option to skip is taken, then Dolphin will crash with a segment fault.

This can also happen if the user opts to `Move Here` and again opts to skip all the files.

This only happens if Dolphin does not successfully write a file. If just one file is written, Dolphin is happy and will continue to function normally. I did not test this with write permissions as I'm a noob and dolphin doesn't like those directories anyways.

SOFTWARE/OS VERSIONS
Kubuntu 19.04

KDE Daemon 5.56.0

(available in About System)
KDE Plasma Version: 
KDE Frameworks Version: 
Qt Version: 

^ I don't know which command to run --version on.
Comment 1 Elvis Angelaccio 2019-10-06 09:48:02 UTC
Please install debug symbols for kio and then post another backtrace.
Comment 2 Bug Janitor Service 2019-10-21 04:33:09 UTC
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!
Comment 3 pac.dlfisher 2019-10-21 05:24:19 UTC
Not sure which package actually contains kio. I went with kdelibs5-dbg. I should also add that the ubuntu repo only had kdelibs5 and libqt4 in the repo.

The generated bug report has some extra fun "this bug report is probably not useful, 1 star of 3" stuff to it that I think is kinda cool! Maybe I missed that before.

The packages containing debug information for the following application and libraries are missing:
/usr/bin/dolphin
/lib/x86_64-linux/libQt5Widgets.so.5
/lib/x86_64-linux/libkdeinti5_dolphin.so
/lib/x86_64-linux/libKF5CoreAddons.so.5
/lib/x86_64-linux/libKF5KIOCore.so.5
/lib/x86_64-linux/libQt5Core.so.5

Unmodified repo file from minimum kubuntu install with closed source driver support

$ apt search dolphin-*
> dolphin-dev

$ apt search libkdeinit
> pkg-kde-tools [installed

$ apt search libkf5coreaddons
> *-data [installed]
> *-dev
> *-dev-bin
> *-doc
> *5 [installed]
> qml-module-org-kde-kcoreaddons [installed]

$ apt search libKF5KIO
> *-dev
> *-doc
> *filewidgets5 [installed]
> *ntlm5 [installed]
> *widgets5 [installed]

$ apt search libqt5core
> *5a [installed]


-------
And I realize this is VERY off topic but there is ABSOLUTELY no way I would go about making a bug report for something I can't reliably reproduce nor would have any idea where to start looking for a backtrace.
When I have Kate focused, the computer will randomly lock up and I'm forced to power cycle the PC. If you happen to know what files might be of use, I can take a gander and make an educated decision on making a bug report for this.
Comment 4 pac.dlfisher 2019-10-21 05:25:36 UTC
Created attachment 123371 [details]
Useless bug report
Comment 5 pac.dlfisher 2019-10-21 05:27:01 UTC
Update status comment requirement message fulfillment center. How may I direct your call?
Comment 6 Elvis Angelaccio 2019-11-03 13:52:19 UTC
(In reply to pac.dlfisher from comment #3)
> Not sure which package actually contains kio.

Should be kio-dbgsym, but please ask in the Ubuntu support channels to be sure.
Comment 7 Bug Janitor Service 2019-11-18 04:33:07 UTC
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!
Comment 8 pac.dlfisher 2019-11-23 15:08:36 UTC
A few things -- I thought I was being clear in the fact that I did look and that I was asking someone who might know or perhaps somewhere where an alternative link could be provided to the package.
I'm able to reproduce it consistently on different hardware running the current version kubuntu - I did that BEFORE bothering to report.

I realize that everyone that contributes or works on fixing these bugs has a life but so do the people who report them and I waited over two weeks just to be told that I need to try and find a better solution to the problem that isn't actually the one I'm reporting so you can have a more detailed report.

Just close the ticket at this point since nobody cares about this issue or can identify where it is coming from.
Comment 9 Elvis Angelaccio 2019-11-24 09:28:52 UTC
We do care, but as already said we need a stacktrace with debug symbols enabled, otherwise there is nothing we can do.
Comment 10 pac.dlfisher 2019-11-25 16:25:08 UTC
And I feel as if I've been very clear in my "I can't figure how to get what you need and shown the steps I have taken to try and find what it is you need"

For reference: https://packages.ubuntu.com/search?keywords=kio&searchon=names&suite=disco&section=all

even instructions on a different solution path would be viable. But instead, I get told to check with the community about it. (A different repo, a direct download, etc)
Comment 11 Julian Steinmann 2019-11-25 17:14:11 UTC
Huh, for some reason Ubuntu doesn't publish kio-dbgsym in the newer repos anymore... Anyways, you should be able to download the .deb package from launchpad: https://launchpad.net/ubuntu/disco/amd64/kio-dbgsym/5.56.0-0ubuntu1. If you do not use a KDE backports PPA, this one should be the correct version. Theoretically the backtrace should then be complete.
Comment 12 pac.dlfisher 2019-11-25 17:21:39 UTC
THAT, that's 19illionth times better than the initial response I got about checking with the community with the information I gave. THANK YOU!!!!!!!

Just for clarification. The KDE backports refer to the older versions and not the current stable release?

How do I verify that I'm not using "KDE packports PPA"?
Comment 13 Julian Steinmann 2019-11-25 18:06:10 UTC
(In reply to pac.dlfisher from comment #12)
> THAT, that's 19illionth times better than the initial response I got about
> checking with the community with the information I gave. THANK YOU!!!!!!!
> 
> Just for clarification. The KDE backports refer to the older versions and
> not the current stable release?
> 
> How do I verify that I'm not using "KDE packports PPA"?

If you don't know whether you are using the backports PPA or not, you most likely don't use it. (You could check this by looking at the output of `sudo apt update` - if ppa.launchpad.net/kubuntu-ppa/[...] is in there, the repository is enabled). The PPA (https://launchpad.net/~kubuntu-ppa/+archive/ubuntu/backports) is to allow users on Kubuntu to get newer versions of KDE software. This would be important because if you had a newer version of KIO, you would also need a newer kio-dbgsym package.
Comment 14 Bug Janitor Service 2019-12-10 04:33:09 UTC
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!
Comment 15 Bug Janitor Service 2019-12-25 04:33:09 UTC
This bug has been in NEEDSINFO status with no change for at least
30 days. The bug is now 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

Thank you for helping us make KDE software even better for everyone!