Version: (using KDE KDE 3.4.2) Installed from: SuSE RPMs OS: Linux This may sound strange, but this is what I did. I had some encrypted files stored in a tar.bz2 archive on a CD-ROM. I wanted to decrypt and view them, but without having any trace of them ever stored on the hard disks. So I thought that creating a RAM disk might accomplish that: travisge:/mnt/hda2/home/travisge> su Password: root:/mnt/hda2/home/travisge# cd tmp root:/mnt/hda2/home/travisge/tmp# mkdir tmpdisk root:/mnt/hda2/home/travisge/tmp# mount ramfs tmpdisk -t ramfs root:/mnt/hda2/home/travisge/tmp# chown travisge.users tmpdisk I was then able to copy the archive to the RAM disk using Konqueror under my normal user account. When I right-clicked it and choose "Extract," Ark said there was no disk space to extract the archive. This is incorrect, because I was able to extract the archive just fine using 'tar' from within Konsole [come to think of it, since I was already using Konsole, I guess I would have made more sense to do that in the first place ;-) ], plus I was able to copy more files to it using Konqueror, and Ark didn't complain when I tried to *create* archives on the RAM disk (as opposed to extracting them).
We have similar problems also, but with a samba filesystem. With tar all works right but with ark shows an "insufficient disk space" message.
Has this still in ark in kde 4?
Looks like a DUPLICATE, marking it as such. *** This bug has been marked as a duplicate of bug 108468 ***
I'm not so sure. This particular case happens even when there is disk space in /tmp. The problem seems to be because the kernel reports the free space on ramfs to always be 0 (since it grows dynamically), and this confuses Ark because it apparently checks the free space left before trying. IMO it shouldn't do that; it should try first and then if an error occurs, report it then.
Did you have enough space in /tmp when this error happened? I have tried to do the same here with KDE 4.2.2 and Ark extracted my tar file correctly.
Yes, it occurs even when there is enough space in /tmp--I've tested this again on KDE 3.5.10. It's possible that it has been fixed in KDE 4 (though I don't plan on upgrading to KDE 4 for quite a while still).
Ark was rewritten for KDE 4; the KDE 3 version is unmantained. Therefore, this bug will not be fixed. Please upgrade to KDE 4.
Actually, changing from WONTFIX to UNMAINTAINED, thus making the third status modification in the day ;) Bugs that are currently present only in KDE3 but do not exist in KDE4 are being marked as UNMAINTAINED, since there won't be a 3.5.11.