Bug 123230

Summary:	Symlink resolving is not consistent
Product:	[Applications] konqueror	Reporter:	András Manţia <amantia>
Component:	general	Assignee:	Konqueror Developers <konq-bugs>
Status:	RESOLVED DUPLICATE
Severity:	normal
Priority:	NOR
Version:	unspecified
Target Milestone:	---
Platform:	unspecified
OS:	Linux
Latest Commit:		Version Fixed In:
Sentry Crash Report:

Description András Manţia 2006-03-07 13:51:23 UTC

Version:           3.5.1 (using KDE 3.5.1, compiled sources)
Compiler:          Target: x86_64-suse-linux
OS:                Linux (x86_64) release 2.6.13-15.8-default

If you have a symlinked dorectory (let's say /home/user/public is a symlink to /mnt/public) Konqueror goes to a different place when you click on the "public" folder icon or you click on the "public" directory in the sidebar. The sidebar takes you to "/home/user/public", while in the icon view area it takes you to "/mnt/public". Of course, they are the same, the real problems appears if you use kiosk and navigation outside of the home directory is forbidden. One will see that it cannot enter the directory in the icon view area, but it can in the sidebar.

Comment 1 Dik Takken 2006-03-08 09:51:31 UTC

Bug 63014 is related to this problem.

Comment 2 András Manţia 2006-03-08 10:22:49 UTC

Yes, it is related, maybe we can call it is the same. I posted a patch 
to kfm-devel, and waitinf for review. If there is no response in a week 
or so, I will commit it.

Comment 3 David Faure 2006-03-09 12:09:51 UTC

On Tuesday 07 March 2006 20:46, Andras Mantia wrote:
> Hi,
> 
>  I expect this to be a controversial patch, but it is needed to achieve 
> consistency within Konqueror itself. The problem is described in 
> http://bugs.kde.org/123230 . The reason why I changed here and not in 
> the sidebar is because it would be still inconsistent, as the user 
> could enter the directory by typing the path in the location bar.
>  I have no idea why the symlink resolving was needed, maybe it was 
> useful when running applications, but KFileItem::run anyway uses the 
> destination, not the link.

Well if you follow the comment and read KFileItem::run you can see that:
  // When clicking on a link to e.g. $HOME from the desktop, we want to open $HOME

Imagine you have a link to your home on the desktop called "MyHome", when clicking
on it you don't want to see "/home/user/Desktop/MyHome/" in konqueror, but /home/user.

So how do we solve this? In one case a symlink is used to hide the actual location
of a directory (/mnt) and in the other case the actual location (home) *is* where 
we want to go, the symlink is just a convenient way to go there. Do we need a 
desktop-specific hack (making symlink-resolution happen only if the link is on 
the desktop), or does someone have a better idea?

Comment 4 David Faure 2006-03-09 12:26:22 UTC


*** This bug has been marked as a duplicate of 63014 ***

*** This bug has been marked as a duplicate of 63014 ***

Comment 5 András Manţia 2006-03-09 12:32:51 UTC

On Thursday 09 March 2006 13:09, David Faure wrote:
> Well if you follow the comment and read KFileItem::run you can see
> that: // When clicking on a link to e.g. $HOME from the desktop, we
> want to open $HOME


I read it but it wasn't clear.

> Imagine you have a link to your home on the desktop called "MyHome",
> when clicking on it you don't want to see
> "/home/user/Desktop/MyHome/" in konqueror, but /home/user.


Hm, I missed this issue.

> So how do we solve this? In one case a symlink is used to hide the
> actual location of a directory (/mnt) and in the other case the
> actual location (home) *is* where we want to go, the symlink is just
> a convenient way to go there. Do we need a desktop-specific hack
> (making symlink-resolution happen only if the link is on the
> desktop), or does someone have a better idea?


The current behavior is very confusing for a normal user and as I wrote 
it is inconsistent as well. So unless there is abetter idea I support 
the desktop-specific hack.

Andras