Super User is a question and answer site for computer enthusiasts and power users. Join them; it only takes a minute:

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

As said, an image is worth a thousand words:

enter image description here

This blank line is weird.

SSH works correctly.

Some verbose mode shows me this:

enter image description here

I just... scp never gave up on me. Looks like it did today.

share|improve this question
I wanted to add the wtf tag, but don't have enough reputation. – Florian Margaine Jan 7 '13 at 16:33
Totally worth that tag! – Abhishrek Jan 7 '13 at 16:39
Could the line be the progress meter? I know it is normally ===> but... – terdon Jan 7 '13 at 16:56
@terdon yeah, this is normally ===>. Maybe it's a "starting to write but failed" line... dunno. – Florian Margaine Jan 7 '13 at 17:12

"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).

share|improve this answer
up vote 0 down vote accepted

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.

share|improve this answer

You must log in to answer this question.

Not the answer you're looking for? Browse other questions tagged .