As said, an image is worth a thousand words:
This blank line is weird.
SSH works correctly.
Some verbose mode shows me this:
I just... scp never gave up on me. Looks like it did today.
The issue was that I added some fun stuff in the remote .bashrc, namely some cowsay + fortune.
This screwed everything up. Removing it, everything worked flawlessly again.
For those stumbling on this thread as I did, but who want to preserve their fortune telling cow friends - Add this to the head of your .bashrc
.
# If not running interactively, don't do anything
# prevents bashrc from breaking non-interactive commands
# like SCP
case $- in
*i*) ;;
*) return;;
esac
This will check for interactivity and not run your .bashrc
for non-interactive shells - such as the SCP case above.
"Note that scp clients do not know how to handle certain URI characters - therefore the filename reported in the status is mangled to remove bad characters with "_" (underscores). This is only for the status report and has no affect on the target filename."
From this page (I googled "scp sink underscore" and looked at the first link. Others may be more explicit)
You may want to try another LC_LANG : LC_LANG=C scp ..........
(and try others, until display is correctly showing the filename).
===>
but...===>
. Maybe it's a "starting to write but failed" line... dunno.