Bug 317057

Summary:	Resuming a copy operation from smb:// fails
Product:	[Frameworks and Libraries] frameworks-kio	Reporter:	Christian Muehlhaeuser <muesli>
Component:	general	Assignee:	David Faure <faure>
Status:	RESOLVED FIXED
Severity:	normal	CC:	adawit, kdelibs-bugs
Priority:	NOR
Version:	unspecified
Target Milestone:	---
Platform:	Arch Linux
OS:	Linux
Latest Commit:		Version Fixed In:
Sentry Crash Report:
Attachments:	Screenshot

Description Christian Muehlhaeuser 2013-03-20 01:11:00 UTC

After an aborted copy operation from smb, I triggered a new copy operation, which pops a warning dialog asking me to Overwrite or Resume the copy. Even when I click "Resume" the destination file gets overwritten and the file is re-downloaded completely.

Reproducible: Always



Expected Results:  
Either remove the option to resume smb transfer operations or (preferrably) make resuming work as expected.

Comment 1 Jekyll Wu 2013-03-20 02:52:27 UTC

Can't reproduce. 

If I abort the copying of some hello.avi, there will be a hello.avi.part left in the destination folder, and when I start a new copy to the same destination, it will just overwrite that hello.avi.part without asking.

So, which KDE version is this report about?  (you should really always provide this information for every bug report)

Comment 2 Christian Muehlhaeuser 2013-03-20 02:57:38 UTC

Sorry, updated. 4.10.1, ArchLinux packages.

Comment 3 Christian Muehlhaeuser 2013-03-20 03:00:15 UTC

Created attachment 78232 [details]
Screenshot

Comment 4 Dawit Alemayehu 2013-08-18 20:38:53 UTC

Resume will only work if the server supports resumption. If it does not clicking on "Resume" will be treated as if you wanted to download again. I cannot duplicate this with my own local test either. A resume operation is properly resumed. Does this issue happen against one single smb server or every smb server you connect to?

Comment 5 Christian Muehlhaeuser 2018-07-14 04:03:49 UTC

I can still reproduce this with smb:// and fish:// for all servers I'm working with.

Comment 6 Christoph Feck 2018-08-03 09:59:38 UTC

Thanks for the update, changing status.

Comment 7 Justin Zobel 2022-11-29 05:06:26 UTC

Thank you for reporting this issue in KDE software. As it has been a while since this issue was reported, can we please ask you to see if you can reproduce the issue with a recent software version?

If you can reproduce the issue, please change the status to "REPORTED" when replying. Thank you!

Comment 8 Christian Muehlhaeuser 2022-11-29 16:16:32 UTC

This seems to be resolved and working now.