Ticket #86 (reopened defect)

Opened 7 years ago

Last modified 6 years ago

symbolic links to directories are shown as file insted directory

Reported by: kuschky Owned by: alamaison
Priority: minor (e.g. uncommon, cosmetic, has workaround) Milestone: 0.9.x Bug sprint
Component: frontend Version: 0.6.0
Keywords: Cc:

Description

If I connect from my Windows machine via swish to a remote ubuntu 10.04 server symbolic links pointing to directories shown as file instead directories and they are not browseable. A click on those links as me to download it. It should be possible like with WinSCp to browse into directories linked via symbolic links

Change History

comment:1 Changed 7 years ago by alamaison

  • Status changed from new to accepted

comment:2 Changed 7 years ago by ubergeeknz

I get the same issue. Remote server is:
Linux version 2.6.30-bpo.2-686 (Debian 2.6.30-8~bpo50+2) ( nobse@debian.org) (gcc version 4.3.2 (Debian 4.3.2-1.1) ) #1 SMP Fri Dec 11 18:12:58 UTC 2009

comment:3 Changed 7 years ago by clinem@georgetown.edu

ditto. Same issue

comment:4 Changed 6 years ago by markos

I was about to log this as a bug too (with remote server Ubuntu 10.10 and 11.04). It is a "critical" bug for what I was hoping to use Swish to do :-( but I concede it will be a "minor" bug (as kuschky logged it) for most users.

comment:5 Changed 6 years ago by Jason jvonmitchell@gmail.com

I have the same bug too. It's pretty critical for me because I have a multi user system where $HOME/www maps to /var/www/whoami . I have a windows user that I would like to have the same setup. Oh, well I'll just make /var/www/whoami soft and $HOME/www hard for that user.

comment:6 Changed 6 years ago by alamaison

  • Status changed from accepted to closed
  • Resolution set to fixed

The  latest release (0.5.4) adds support for symlinks. Please try it out and let us know how you get on.

comment:7 follow-up: ↓ 8 Changed 6 years ago by markos

Nice one, thank you! I've upgraded to version 0.6.0 and the symbolic links to directories are working great.

However, if I double-click a symbolic link that is to a file I get an "Unable to access the directory (Failed opening remote file: FX_NO_SUCH_FILE)" error. If I right-click the file link and choose send to the target file is copied correctly, so it appears that it is just the open link action that isn't working for me.

comment:8 in reply to: ↑ 7 ; follow-up: ↓ 9 Changed 6 years ago by alamaison

  • Status changed from closed to reopened
  • Version set to 0.6.0
  • Resolution fixed deleted
  • Milestone set to 0.6.1 Bug sprint

Replying to markos:

However, if I double-click a symbolic link that is to a file I get an "Unable to access the directory (Failed opening remote file: FX_NO_SUCH_FILE)" error. If I right-click the file link and choose send to the target file is copied correctly, so it appears that it is just the open link action that isn't working for me.

I suspect this is due to the interaction between 'linkness' and the new direct opening capability. What happens if you drag-and-drop/cut-and-paste the file to the local disk?

Can you give me the long-form directory entry (i.e. ls -l) of both the link and its target?

comment:9 in reply to: ↑ 8 Changed 6 years ago by markos

Replying to alamaison:

I suspect this is due to the interaction between 'linkness' and the new direct opening capability. What happens if you drag-and-drop/cut-and-paste the file to the local disk?

Dragging and dropping (or copying) either a linked folder or file makes a copy of the target with the name of the link. Right-clicking and choosing Send to works in the same way. Right-clicking and choosing Open link works for linked folders but not files.

Can you give me the long-form directory entry (i.e. ls -l) of both the link and its target?

I created a basic folder structure to demonstrate the issue. Here is the result of performing a ls -l -R on that:

.:
drwxr-xr-x 3 root root 4096 2011-09-26 16:26 swish

./swish:
drwxr-xr-x 4 root root 4096 2011-09-26 16:26 is

./swish/is:
drwxr-xr-x 2 root root 4096 2011-09-26 16:30 clever
drwxr-xr-x 2 root root 4096 2011-09-26 16:31 great

./swish/is/clever:
-rw-r--r-- 1 root root 4 2011-09-26 16:30 yesitis.txt

./swish/is/great:
lrwxrwxrwx 1 root root 10 2011-09-26 16:28 good -> ../clever/
lrwxrwxrwx 1 root root 21 2011-09-26 16:31 isntit.txt -> ../clever/yesitis.txt

When I navigate this structure using Swish: double-clicking the /swish/is/great/good folder redirects to /swish/is/clever as hoped; double-clicking the /swish/is/great/isntit.txt file gives the FX_NO_SUCH_FILE error.

comment:10 Changed 6 years ago by alamaison

  • Milestone changed from 0.6.x Bug sprint to 0.7.x Bug sprint
Note: See TracTickets for help on using tickets.