Uploading changes in default Editor doesn't work sometimes

Advertisement

franc
Donor
franc avatar
Joined:
Posts:
45

Uploading changes in default Editor doesn't work sometimes

Hello

this is a weird bug, I have only since the WinSCP version 5.5.2
I am on Windows XP (SP3, 32).

I use normally the multitabbed Editor EditPad Pro, version 7.3.1
Often I edit files from my SSH-connected Ubuntu Server with SFTP in this editor.

But sometimes, it happend now the second time, I wonder why the changes are not visible, but I did save them, no error message.
Reason is, that WinSCP doesn't upload it again.
So I tried with a single window editor, TedNPad, but still the same.

It will work again, I thought, when I restart WinSCP, but this is a bit annoying, because I have three WinSCP tabs and files open.
But no, this doesn't still not work, when restarted WinSCP.
I tried to upload big changes, so WinSCP should be busy a little and I can look into the Queue, there I see strange Progress Completed and Transferred 0 B, after a short while Queue closed.

I don't think it is possible to log WinSCP, because this bug appears not often, so the logfile could be gigabytes.

Thank you.
frank

Description: Queue WinSCP 5.5.2

winscp-queue.jpg

Reply with quote

Advertisement

franc
Donor
franc avatar
Joined:
Posts:
45

This is a real problem.
I cannot trust to editing through WinSCP anymore.
I wonder why things not working and again this doesn't upload!

I don't know what this is, the only way then is, to delete file, and recreate it with same content. This work then a while.

What could that be?

Reply with quote

martin
Site Admin
martin avatar
Joined:
Posts:
41,405
Location:
Prague, Czechia

Re: Uploading changes in default Editor doesn't work sometimes

Thanks for your report.
I have sent you an email with a debug version of WinSCP to address you have used to register on this forum.

Reply with quote

franc
Donor
franc avatar
Joined:
Posts:
45

Can you send me a version, where there is all private data in the debug log excluded?
I find a lot of things like:

[Password=A35C795D0D2E333...]

in this debug-logfile.

I guess till the bug will appear, it could take some time, and in the end, I have a debug protocol of 100 MB or more.
It will be not possible for me to surely delete all private data in this log (like I tried last time).
The log will be filled with passwords, I cannot send these out, sorry.

Reply with quote

Advertisement

You can post new topics in this forum