Summary: | Ark incorrectly claims there is no disk space when attempting to extracting archives stored on a RAM disk | ||
---|---|---|---|
Product: | [Applications] ark | Reporter: | Travis Evans <travisgevans> |
Component: | general | Assignee: | Harald Hvaal <metellius> |
Status: | RESOLVED UNMAINTAINED | ||
Severity: | normal | CC: | jonas.vejlin, rakuco |
Priority: | NOR | ||
Version: | unspecified | ||
Target Milestone: | --- | ||
Platform: | openSUSE | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: |
Description
Travis Evans
2005-08-31 10:27:58 UTC
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. |