Post a reply

Before posting, please read how to report bug or request support effectively.

Bug reports without an attached log file are usually useless.

Options
Add an Attachment

If you do not want to add an Attachment to your Post, please leave the Fields blank.

(maximum 10 MB; please compress large files; only common media, archive, text and programming file formats are allowed)

Options

Topic review

martin

Thanks for the details. Though I still cannot reproduce the problem.

I have sent you an email with a debug version of WinSCP to the address you have used to register on this forum.
Jeroen45

Thanks for your reply, I've attached the (modified to hide identifying information) log file. I also think I might have found more specific steps to reproduce the problem. I noticed that the problem doesn't occur when dragging files from within the left local directory window within the program to the right remote directory window to upload them, and then clicking the proceed in background button. The problem only occurs when the same steps are followed, but the files are dragged to the remote directory from a Windows explorer window outside the program. Hopefully this information helps, thanks a lot for taking a look at this problem.
martin

I never got any feedback from anyone regarding this (seemingly very rare) problem.
Can you post a session log file showing the problem (using the latest version of WinSCP)?

To generate the session log file, enable logging, log in to your server and do the operation and only the operation that causes the error. Submit the log with your post as an attachment. Note that passwords and passphrases not stored in the log. You may want to remove other data you consider sensitive though, such as host names, IP addresses, account names or file names (unless they are relevant to the problem). If you do not want to post the log publicly, you can mark the attachment as private.
Jeroen45

Sorry for the ambiguity, I meant the "Pressing "Proceed in background" terminates the transfer immediately in the latest version of winscp" problem.
martin

Jeroen45 wrote:

Sorry for bumping this topic, but this is the only reference to this problem I could find, and I'm still experiencing this problem with winscp 5.17.10. Is any fix known yet, apart from downgrading to older versions?

What problem exactly? There are two different issues discussed here.
Jeroen45

Hi there!

Sorry for bumping this topic, but this is the only reference to this problem I could find, and I'm still experiencing this problem with winscp 5.17.10. Is any fix known yet, apart from downgrading to older versions?
Thanks in advance for any update on this.
martin

radekzc wrote:

Pressing "Proceed in background" terminates the transfer immediately in the latest version of winscp 5.17.2.

Thanks for your report.

Can you send me an email, so I can send you back a debug version of WinSCP to track the problem? Please include a link back to this topic in your email. Also note in this topic that you have sent the email. Thanks.

You will find my address (if you log in) in my forum profile.
radekzc

Pressing "Proceed in background" terminates the transfer immediately in the latest version of winscp 5.17.2.
Guest

really?

You mean you can't see a use case where you would want to check on your background transfers. Maybe see how far they have come, maybe to cancel the operation altogether or maybe figure out if you can close the program and restart your pc already.

It shouldn't have been implemented without an undo function built in, that's just basic HCI.
martin

Re: How to bring background transfers to the foreground?

It's not possible.
What is your use case for this?
NewUser

How to bring background transfers to the foreground?

This should be a simple task but for some reason I cannot find any option that allows me to bring the background transfer to the foreground.