Bug 353226

Summary:	Dolphin fails after copying the first 4 GB of a large file
Product:	[Frameworks and Libraries] frameworks-kio	Reporter:	Christopher Yeleighton <giecrilj>
Component:	general	Assignee:	David Faure <faure>
Status:	RESOLVED DUPLICATE
Severity:	normal	CC:	bugseforuns, frank78ac, kdelibs-bugs, pip.kde, suse
Priority:	NOR
Version:	unspecified
Target Milestone:	---
Platform:	openSUSE
OS:	Linux
Latest Commit:		Version Fixed In:

Description Christopher Yeleighton 2015-09-27 05:37:22 UTC

Dolphin fails after copying the first 4 GB of a large file when the target file is located on a FAT-formatted USB memory stick.

Reproducible: Always

Steps to Reproduce:
1. Tell Dolphin to copy the file openSUSE-Tumbleweed-DVD-x86_64-Snapshot20150909-Media.iso to a FAT-formatted USB memory stick.


Actual Results:  
1. Dolphin copies the first 4 GB of the file, fails and leaves the target file incomplete.

Expected Results:  
1. Let Dolphin recognise that it cannot allocate such a large file on a target device and offer to split the file into parts.

Comment 1 Paul 2015-09-27 08:27:00 UTC

(In reply to Christopher Yeleighton from comment #0)
> Dolphin fails after copying the first 4 GB of a large file when the target
> file is located on a FAT-formatted USB memory stick.

That's due to the limitation of the FAT formatted memory stick. :)

Comment 2 Frank Reininghaus 2015-09-27 08:40:31 UTC

Thanks for the report.

(In reply to Christopher Yeleighton from comment #0)
> Expected Results:  
> 1. Let Dolphin recognise that it cannot allocate such a large file on a
> target device and offer to split the file into parts.

Alternatively, simply display an error message and tell the user that it's not possible to copy the file.

In any case, this looks like a KIO issue.

Comment 3 suse 2018-03-28 20:16:54 UTC

confirmed.

plasma: 5.12.3
framework: 5.44.0
application: 17.12.3

But even "cp" starts to copy the file and stops at 4 GiB (message "File too large") as well as rsync.

Comment 4 Patrick Silva 2018-04-21 18:25:56 UTC


*** This bug has been marked as a duplicate of bug 198772 ***