AlexShadow / superputty

Automatically exported from code.google.com/p/superputty
MIT License
0 stars 0 forks source link

File transfer from server to localhost does not work #305

Closed GoogleCodeExporter closed 8 years ago

GoogleCodeExporter commented 8 years ago
What steps will reproduce the problem?
1. Open Sessions toolbar
2. Right click on host, select "File Transfer"
3. Attempt to drag file from file transfer window onto desktop (Can't do it)

What is the expected output? What do you see instead?
I expect the file to transfer to my local machine.  Instead nothing happens.  
The mouse cursor does not change while dragging, and nothing happens once the 
mouse button is released on my desktop.  No entries in Log Viewer beyond the 
"Activated" entry when I switch back to the Superputty window.

Right clicking and hitting delete while files are selected within the File 
Transfer window also has no effect (no idea if those actions would have an 
affect anyway).

What version of the product are you using? On what operating system?
Superputty 1.4.0.2 (also tried 1.3.0.0 and 1.4.0.1)
Local O/S: Windows 7 SP1
Remote O/S: RHEL 5.8 (also tried CentOS 6.3)

Please provide any additional information below.
For good measure, attempted the same operation after setting Superputty.exe to 
compatibilty mode for WinXP SP3 and "Open as Administrator" (both separately 
and together).  Didn't help.

Note that I am able to transfer files TO the remote host just fine.  I just 
cannot interact with / download files from the remote host.

Original issue reported on code.google.com by anthony....@gmail.com on 13 Mar 2013 at 5:12

GoogleCodeExporter commented 8 years ago
1.4.0.4's file transfer has a new pane which has a local browser where you can 
drop files onto.

I might try to allow remote-to-explorer drag and drop later, but it's a bit 
involved.
http://blogs.msdn.com/b/delay/archive/2009/10/26/creating-something-from-nothing
-developer-friendly-virtual-file-implementation-for-net.aspx 

Original comment by btatey...@gmail.com on 22 May 2013 at 5:13

GoogleCodeExporter commented 8 years ago

Original comment by btatey...@gmail.com on 22 May 2013 at 5:22

GoogleCodeExporter commented 8 years ago
in remote machine by default it is trying to open /home/<loginuser> directory.
In case if in remote machine directory does not exist then it throws error as 
below

2014-01-16 10:03:44,900 INFO            PscpClient - Process exited, pid=7880, 
exitCode=0
2014-01-16 10:03:44,902 ERROR     BrowserPresenter - Unable to open /home/root: 
no such file or directory
2014-01-16 10:04:35,327 DEBUG           SuperPuTTY - STATUS: Editing Options

This should be configurable i.e. which directory i want to list for PscpClient 
process

Original comment by singhi...@gmail.com on 16 Jan 2014 at 4:43

GoogleCodeExporter commented 8 years ago

The root user is a typical example, as there is no /home/root. As a workaround, 
I added asymlink (cd /home && ln -s /root/) and the file transfer pane works 
fine.

Original comment by stoumpos...@gmail.com on 24 Mar 2014 at 11:41

GoogleCodeExporter commented 8 years ago
Please fix the issue. On most servers I handle the expectation of /home/$user 
to exist is simply wrong, so the file transfer feature is useless. While a 
configurable as fix would be the best solution IMO, a quick fix would be to 
fall back to / if /home/$user can't be found.

Original comment by noack.mi...@googlemail.com on 6 Mar 2015 at 10:38