Bug 90240 - Misbehaviour when overwriting a symbolic link with a real directory
Summary: Misbehaviour when overwriting a symbolic link with a real directory
Status: RESOLVED NOT A BUG
Alias: None
Product: konqueror
Classification: Applications
Component: general (show other bugs)
Version: 3.3
Platform: unspecified Linux
: NOR normal
Target Milestone: ---
Assignee: Konqueror Developers
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2004-09-25 21:27 UTC by Christoph Wiesen
Modified: 2006-10-31 08:56 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Christoph Wiesen 2004-09-25 21:27:23 UTC
Version:           3.3 (using KDE 3.3.0, SuSE)
Compiler:          gcc version 3.3.3 (SuSE Linux)
OS:                Linux (i686) release 2.6.4-52-default

I'll try to explain this the way it really happened:

I had a kdecvs directory in ~/ and moved that to /data/
Created a symlink (with Konqueror drag'n drop) of it inside /data/shared so that I hap /data/shared/kdecvs -> /data/shared.
Now  I moved (again Konqueror drag'n drop) /data/kdecvs/ to /data/shared/.
So it should overwrite the kdecvs symlink inside /data/shared.

Basically that is what happened, but /data/shared/kdecvs still hat the symlink folder-icon and I could not access it from another PC where I had /data/shared mounted via nfs - it still showed the missing-symlink-icon.

I did not check that /data/kdecvs was really gone and therefor thought /data/shared/kdecvs actually still was a symlink and deleted it. Luckily I sued the trash for that ;)

Btw. Ihave been asked if /data/shared/kdecvs should be overwritten so basically all that's wrong is that the system somehow still thinks it is a symlink instead of a real folder. I could access it locally via /data/shared/kdecvs nevertheless.
Comment 1 J Appel 2006-09-12 11:24:40 UTC
Christoph, is this still an issue with a recent kde version (ie 3.5.4) ?
Comment 2 lexual 2006-10-31 08:55:49 UTC
Closing due to no response from reporter.
Bug will be reopened if additional information is provided.
Comment 3 lexual 2006-10-31 08:56:10 UTC
closing.