Bug 289255 - Desktop to Path symlink handling, option to choose [absolute] or [relative]
Summary: Desktop to Path symlink handling, option to choose [absolute] or [relative]
Status: RESOLVED FIXED
Alias: None
Product: systemsettings
Classification: Applications
Component: kcm_desktoppath (show other bugs)
Version: 1.0
Platform: Mageia RPMs Linux
: NOR wishlist
Target Milestone: ---
Assignee: Unassigned bugs mailing-list
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-12-18 06:55 UTC by Jose Da Silva
Modified: 2015-04-17 16:46 UTC (History)
3 users (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 Jose Da Silva 2011-12-18 06:55:29 UTC
Version:           1.0 (using KDE 4.7.3) 
OS:                Linux

In the Mageia Forums, it came to attention that path selection appears different when upgrading from Mandriva 2010.2 (using KDE 4.3) to Mageia 1 (using KDE 4.6.5). I just checked with Mageia 2 Alpha1 (using KDE 4.7.3) and see this still exists.

Problem:
When you open an application, such as Kwrite, Okular, Ksnapshot, Gwenview, if your designated path is a symlink to another location, instead of following the symlink as defined, we begin with the absolute translated real path. In prior versions of KDE (4.3) you would normally follow the symlink path, but now with KDE 4.6.5,4.7.3 we are given the real path.
You can follow the discussion details here: https://forums.mageia.org/en/viewtopic.php?f=8&t=1578
title "make application go to the symlink"

Wishlist Question:
Would it be possible to add a feature into kcmshell4 desktopath to allow users to follow the relative or the absolute path. It is understood some people come from a Windows background and may prefer or be used to an absolute path, while users more accustomed to a unix/linux/bsd background are more used to a symlink followed path. Having this option available would allow users to choose there preferred option choice if the described path happens to be a symlink to another location.

Reproducible: Always

Steps to Reproduce:
1) In case you cannot replicate this under a simpler setup, then it is probably best to begin with 2 different partition compiled with different file formatting, for example "/home/user" is located in "/dev/sda1" and formatted as "reiserFS", partition "/dev/sda5" is "/" (not important, but let's say ext4), and another partition "/dev/sda6" is formatted as xfs and holds "/mnt/temp".

2) In /mnt/temp, now create another directory, temp2, and give it read/write permissions so that user can write in it... chmod 777 /mnt/temp/temp2

3) In user's home directory, create a symlink.
cd ~
ln -s /mnt/temp/temp2 /home/user/xyz

4) Start KDE's System settings and go to Account Details, and convert the existing paths to use the symlink instead. Examples:
Document Paths: /home/user/xyz/
Pictures Paths: /home/user/xyz/
Apply the fix, do not move documents to new location.

5) Run a program. Okular. Select File->Open
expected path is /home/user/xyz but the given path shows /mnt/temp/temp2

6) Try a few other programs, Ksnapshot, Kwrite ...

Actual Results:  
Open or Save file default location points to the resolved path of /mnt/temp/temp2

Expected Results:  
Was hoping to see the symlink path since the path written in desktopath was /home/user/xyz.

There are some KDE bugs and wishes (around KDE 4.3) where this began gradually changing from the stated method to the resolved method.
http://forum.kde.org/viewtopic.php?f=22&t=84150
http://forum.kde.org/brainstorm.php#idea84173_page1
and eventually by version KDE 4.7.3 (approaching 4.8) we begin to see a fair bit of the resulting changes.
http://trueg.wordpress.com/2011/12/07/symbolic-links-in-nepomuk-a-solution/

As mentioned up above... this came about as something of interest in https://forums.mageia.org/en/viewtopic.php?f=8&t=1578

this problem could be worked-around by providing a different path, like /home/user but maybe it is worth adding an option or selection toggle for these exceptions when users use a symlink as their chosen path.
Comment 1 John Groombridge 2011-12-18 20:50:28 UTC
Although it might appear to not matter, there can be different directories either side of the symlinked directory compared with the corresponding directory on the originating partition. This can be very inconvenient if another directory is desired which is not also on the partition pointed at by the symlink.
Comment 2 Morgan Leijström 2012-01-05 08:55:44 UTC
I think this need to be resolved

Normally a user expects to see the path be like the one he clicked on.

I can see that sometimes it is informative to see where you actually end up "geographically" such as at a file server.  But that information should  be conveyed in another way IMO.

The user should not need to re-think or adapt some other links, because the sysop moved file storage and updated users links.  (Like me as admin on a family network may do)
Comment 3 David Edmundson 2015-04-17 16:46:13 UTC
It shows the symlink path here (i.e ~/xyz), setting with Plasma 5, but opening using both Qt4 and Qt5 apps.

By default kwrite/gwenview will be opening the last folder, maybe you're just seeing that?
Or maybe it's been changed in the meantime.