Description of problem:
Ark hangs when trying to open large tar files. I suspect that it
doesn't realize they are compressed. The file in question was
produced as root with:
tar -cvzf home.tgz /home
It was 4.1 GB in size. Tar opened it easily. I suspect ark didn't
realize it was compressed, but that is just a guess.
Version-Release number of selected component (if applicable):
Is ark part of kdebase ?
I tested it twice and it happened twice. Due to the time it takes to
test this, I didn't test it again, although I could if you need me to.
home.tgz is backed up on disk.
Steps to Reproduce:
1.tar a large amount of data using tar -cvzf something.tgz /somewhere
2.open the archive with ark.
3.wait and wait and wait.
ark hangs. The OS slows down considerably.
ark should build the directory/file list and display them.
I liked file roller a lot better than ark (so far)
Ark had problems with some other files as well. In general I've found
it to be nearly unusable. I used the tar /home example because I knew
the archive was good and I tried it twice.
This is still a problem with FC3 final. It totally stalls the
machine. file-roller does the task easily.
Fedora Core 3 is now maintained by the Fedora Legacy project for security
updates only. If this problem is a security issue, please reopen and
reassign to the Fedora Legacy product. If it is not a security issue and
hasn't been resolved in the current FC5 updates or in the FC6 test
release, reopen and change the version to match.
Closing per lack of response to previous request for information.
This bug was originally filed against a much earlier version of Fedora
Core, and significant changes have taken place since the last version
for which this bug is confirmed.
Note that FC3 and FC4 are supported by Fedora Legacy for security
fixes only. Please install a still supported version and retest. If
it still occurs on FC5 or FC6, please reopen and assign to the correct
version. Otherwise, if this a security issue, please change the
product to Fedora Legacy. Thanks, and we are sorry that we did not
get to this bug earlier.