Bug 330588

Summary:	when I deleted (skipping the trash) a symbolic link to a folder, the folder itself was deleted together with the link
Product:	[Unmaintained] kio	Reporter:	Tomas Van Verrewegen <tomasvanverrewegen>
Component:	general	Assignee:	David Faure <faure>
Status:	RESOLVED WORKSFORME
Severity:	critical	CC:	adawit, cfeck, frank78ac
Priority:	NOR	Keywords:	triaged
Version First Reported In:	4.11.3
Target Milestone:	---
Platform:	Ubuntu
OS:	Linux
Latest Commit:		Version Fixed/Implemented In:
Sentry Crash Report:

Description Tomas Van Verrewegen 2014-01-30 17:28:20 UTC

What I did:
-open dolphin
-use treeview mode
-split screen vertically
-drag a folder from the right screen to the left
-choose "Link here"
This is all very simple and straight forward, now work with these files for a couple of hours, everything works as it should... but then...
-the icon of the symbolic link has changed (behind my back) to a question mark with a link arrow on top, it is not a folder anymore, but also not a file or link, I cannot open it, dolphin says it is a file of "Unknown type", I can't change the name, move it, .... I can't do anything with it anymore...
So... I check the original folder -> this is still OK, I think "Phew... thought I'd lost a lot of work here...", so then I delete (shift-delete) the screwed up symbolic link and what happens....??? BOTH THE (screwed up, unknown filetype, unreadable, unwritable) LINK AND THE ORIGINAL FOLDER ARE DELETED 

I also have another problem with dolpin, maybe these 2 are related somehow... I will create a separate bugreport for this and let people who know what they are doing sort this out

Reproducible: Didn't try



Expected Results:  
It should have deleted the link, not the original folder+contents

tomas@tomas:~$ lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description:    Ubuntu 13.10
Release:        13.10
Codename:       saucy

KDE: 4.11.3

Comment 1 Tomas Van Verrewegen 2014-01-30 17:40:24 UTC

link to other bug (possibly related, probably not): https://bugs.kde.org/show_bug.cgi?id=330589

Comment 2 Frank Reininghaus 2014-01-30 18:03:15 UTC

Thanks for the bug report. Most likely, this is not a Dolphin bug. It might be related to KIO (the part of kdelibs that is used to interact with the file system).

The description sounds weird though. Do you use some special way to mount the affected device(s)?

I don't know what could cause such a problem, but maybe someone else has an idea.

Comment 3 Tomas Van Verrewegen 2014-01-30 18:45:49 UTC

I didn't really think it is a dolphin bug myself, but since dolphin is acting up a bit lately...
The folder and the symlink were both inside my home folder, so just regular ext4.

from /etc/fstab:
# <file system> <mount point>   <type>  <options>       <dump>  <pass>
# / was on /dev/sda6 during installation
UUID=4517aa0b-909b-4d2a-a134-4ab34edf82de /               ext4    errors=remount-ro 0       1
# /home was on /dev/sda8 during installation
UUID=ee3eac1c-ddcc-4f74-bade-9c78922adeb6 /home           ext4    defaults        0       2

Comment 4 Christoph Feck 2014-01-30 22:27:12 UTC

What does "rm -r" do on a symbolic link?

Comment 5 Tomas Van Verrewegen 2014-01-31 08:41:26 UTC

tomas@tomas:~$ mkdir test
tomas@tomas:~$ cd test/
tomas@tomas:~/test$ mkdir 1
tomas@tomas:~/test$ ln -s 1 2
tomas@tomas:~/test$ ls -l
total 4
drwxr-xr-x 2 tomas tomas 4096 Jan 31 09:35 1
lrwxrwxrwx 1 tomas tomas    1 Jan 31 09:35 2 -> 1
tomas@tomas:~/test$ rm -r 2
tomas@tomas:~/test$ ls -l
total 4
drwxr-xr-x 2 tomas tomas 4096 Jan 31 09:35 1
omas@tomas:~/test$ 

like this?

Comment 6 Dawit Alemayehu 2014-05-03 12:32:06 UTC

(In reply to comment #5)
> tomas@tomas:~$ mkdir test
> tomas@tomas:~$ cd test/
> tomas@tomas:~/test$ mkdir 1
> tomas@tomas:~/test$ ln -s 1 2
> tomas@tomas:~/test$ ls -l
> total 4
> drwxr-xr-x 2 tomas tomas 4096 Jan 31 09:35 1
> lrwxrwxrwx 1 tomas tomas    1 Jan 31 09:35 2 -> 1
> tomas@tomas:~/test$ rm -r 2
> tomas@tomas:~/test$ ls -l
> total 4
> drwxr-xr-x 2 tomas tomas 4096 Jan 31 09:35 1
> omas@tomas:~/test$ 
> 
> like this?

And if you do that same exact test in Dolphin again what happens? IOW, can you reliably reproduce this issue? I tried to reproduce this issue on my own machine, but I could not.

Comment 7 Andrew Crouthamel 2018-09-25 03:55:50 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 set the bug status 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 Andrew Crouthamel 2018-10-27 02:48:52 UTC

Dear Bug Submitter,

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!