Bug 191877 - Extracting RAR file Ark reports that the contained "iso" file is 4.3 Gb but extacted file is only 1 Gb or less. For some reason it fails to extract the compleate file.
Summary: Extracting RAR file Ark reports that the contained "iso" file is 4.3 Gb but e...
Status: RESOLVED DUPLICATE of bug 176914
Alias: None
Product: ark
Classification: Applications
Component: general (show other bugs)
Version: 2.10.999
Platform: unspecified Linux
: NOR normal
Target Milestone: ---
Assignee: Harald Hvaal
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2009-05-07 08:32 UTC by zsimac
Modified: 2009-05-07 09:23 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description zsimac 2009-05-07 08:32:51 UTC
Version:           2.10.999 (using 4.1.3 (KDE 4.1.3) "release 4.10.4", openSUSE 11.1)
Compiler:          gcc
OS:                Linux (x86_64) release 2.6.27.21-0.1-trace

Trying to extract RAR archive (70 files).
When ARK opens it reports that archive contains 1 single ISO file which size is 3.5 GiB.
When I click "Extract" and specify folder ARK begins saying that is extracting 1 file of the type=raw CD image.
When the progress bar disappears I open "Extract folder in my file manager (Dolphin & Krusader) and the reported size is never more than 1 Gib; sometimes as little as 38 MiB.

When I try to open created file with "ISO Master" it reports that it "Failed to read Expected number of bytes".

RAR file is confirmed "GOOD" by extracting in Windows OS with WinRAR without a glitch to the correct size: I am able to burn the disc as well, so the ISO image file itself is a valid file.
Comment 1 zsimac 2009-05-07 08:51:13 UTC
I have just tried extracting files from RAR archive with command line UNRAR utility and all works fine.

Also now I see that UNRAR runs quite a bit longer than Ark for the same file set; It look to me that ARK stops, for some reason, prematurely.

I am using SUSE V11.1 64 bit.
Comment 2 Harald Hvaal 2009-05-07 09:23:53 UTC
This has been fixed in a newer version already.

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