Summary: | tar/zip/... ioslave cannot extract large files when coping | ||
---|---|---|---|
Product: | [Applications] konqueror | Reporter: | Clara Gnos <clara.gnos> |
Component: | general | Assignee: | Konqueror Developers <konq-bugs> |
Status: | RESOLVED FIXED | ||
Severity: | normal | CC: | sven.burmeister, vide80 |
Priority: | NOR | ||
Version: | unspecified | ||
Target Milestone: | --- | ||
Platform: | Gentoo Packages | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: | ||
Sentry Crash Report: | |||
Attachments: | small tar.bz2 where the problem appears |
Description
Clara Gnos
2005-03-14 17:06:19 UTC
Created attachment 10099 [details]
small tar.bz2 where the problem appears
Open the the file in konqueror -> right click -> copy. Go to another path ->
right click -> paste. It will probably create an empty file
Just tested it with a "total" different system, kubuntu and kde 3.4 rc1. It is the same problem here CVS commit by pletourn: Send the data in small pieces (Connection::sendnow() has a 16MB limit) BUG:101486 M +15 -1 tar.cc 1.34.2.1 --- kdebase/kioslave/tar/tar.cc #1.34:1.34.2.1 @@ -369,7 +369,21 @@ void ArchiveProtocol::get( const KURL & mimeType( result->mimeType() ); - data( completeData ); + QByteArray partialData; + int offset = 0; + const int inc = 0x800000; // 8MB + + while ( offset + inc < archiveFileEntry->size() ) { + partialData.setRawData( completeData.data() + offset, inc ); + data( partialData ); + partialData.resetRawData( completeData.data() + offset, inc ); + processedSize( offset + inc ); + offset += inc; + } + partialData.setRawData( completeData.data() + offset, archiveFileEntry->size() - offset ); + data( partialData ); + partialData.resetRawData( completeData.data() + offset, archiveFileEntry->size() - offset ); processedSize( archiveFileEntry->size() ); + data( QByteArray() ); *** Bug 100871 has been marked as a duplicate of this bug. *** *** Bug 93249 has been marked as a duplicate of this bug. *** I know it's a little thing but why is my bug which has a minor number marked as duplicate of a larger one? :( Because the patch that fixed this one also fixed yours, and the developer probably didn't know that until he retested. |