After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 358205 - Creating shortcut to folder on SMB-share fails
Creating shortcut to folder on SMB-share fails
Status: RESOLVED DUPLICATE of bug 314065
Product: nautilus
Classification: Core
Component: general
3.2.x
Other All
: Normal normal
: ---
Assigned To: Nautilus Maintainers
Nautilus Maintainers
Depends on:
Blocks: 652944
 
 
Reported: 2006-09-28 22:22 UTC by Oliver Gerlich
Modified: 2013-04-23 18:00 UTC
See Also:
GNOME target: ---
GNOME version: 3.1/3.2



Description Oliver Gerlich 2006-09-28 22:22:20 UTC
Please describe the problem:
When trying to use Nautilus to create a shortcut to a folder that is on a Windows Share (eg. accessed via smb://...), an error message appears, and no shortcut is created.

Steps to reproduce:
1. Open "Locations" -> "Network server"
2. Go to "Windows Network" and select a workgroup, then a computer, then a shared folder
3. Make sure there's a folder inside the shared folder
4. Right-click on the inner folder, and select "Create Shortcut"


Actual results:
The following error message appears: "Fehler »Nicht unterstützter Vorgang« beim Anlegen einer Verknüpfung mit »smb://charly/save/da«." ("Action not supported when trying to create shortcut to smb://charly/save/da"), and it asks if I want to go ("Abort", "Retry"). No shortcut is created.

Expected results:
Either a shortcut should be created "as usual" (ie. in the shared folder), so that I can then move it where I like it (eg. to the Desktop). Or Nautilus should tell me that the shortcut cannot be created in that location, and ask me whether I want the shortcut to be created on the Desktop.

Currently, I have worked around this problem by using the "Locations" menu, then selecting "Connection to server...". Then I could select "Windows Share" from the list, and manually fill in all necessary information. This gets me exactly the shortcut I want to have (on the Desktop, where I wanted it :) . So it is possible to create such shortcuts, but it probably doesn't fit into Nautilus' usual way (I guess usually Nautilus creates a symlink if one creates a shortcut to a folder).

Does this happen every time?
Yes

Other information:
Comment 1 André Klapper 2011-08-18 20:21:49 UTC
As nautilus uses a different library (gio/gvfs instead of gnome-vfs) for this since 2.22/2.24: Is this still an issue in 3.0 or 2.32 or can this be closed as obsolete?
Comment 2 Akhil Laddha 2011-09-30 11:49:37 UTC
Thanks for taking the time to report this bug; however, closing due to lack of
response of the reporter, sorry. if you still see this issue with recent
stable releases of GNOME (3.0.2 or 3.2.0), please reopen. tia.
Comment 3 chrysn 2011-09-30 19:09:28 UTC
i can confirm this is still present in 3.2. the current error message is:

> Error while creating link to <target>.
> 
> The target doesn't support symbolic links.

it seems i don't have the permissions to reopen this.
Comment 4 André Klapper 2011-10-02 12:03:39 UTC
Reopening.
Comment 5 Itai Bar-Haim 2012-03-25 09:02:56 UTC
happens to me as well. trying to link a shared Samba folder to desktop. it either fails or creates a bad link.
Comment 6 António Fernandes 2013-04-23 18:00:29 UTC
Thanks for the bug report. This particular bug involves two bugs which have already been reported into our bug tracking system, but please feel free to report any further bugs you find.

(In reply to comment #0)
> Either a shortcut should be created "as usual" (ie. in the shared folder), so
> that I can then move it where I like it (eg. to the Desktop). [...]

This is not possible util bug 562029 is fixed, as explained on bug 677397.

> [...] Or Nautilus
> should tell me that the shortcut cannot be created in that location, and ask me
> whether I want the shortcut to be created on the Desktop.

This is requested on bug 314065.

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