Description of problem: abrt uses unnecessary amount of disk space when getting debug info and goes far outside the quota. This makes it unusable for a system with limited extra disk space. Limited disk space is in this case 2 GB and does not feel unreasonable to expect it to work for this. Version-Release number of selected component (if applicable): abrt.x86_64 1.0.6-1.fc12 How reproducible: always when lot's of debug info is missing and disk space is limited (limited in this case is less than 2 GB) Steps to Reproduce: 1. remove all debug info from abrt 2. have a bug that requires lot's of debug info to report 3. have limited disk space to work with for abrt Actual results: abrt downloads all missing debug info, then unpacks it, then writes the needed files to disk. This operation dies before finish unnecessarily when disk space runs out. Expected results: Suggestion: abrt could download one debug info file at a time, unpack it, write the needed files to it's cache and then release the working disk space. Then repeat for every missing debug info file. This would reduce the needed amount of working disk space if I have not misunderstood how the process works. Additional info:
>Suggestion: abrt could download one debug info file at a time, unpack it, write t he needed files to it's cache and then release the working disk space. Committed a change to git to do exactly this.
abrt-1.0.7-1.fc12 has been submitted as an update for Fedora 12. http://admin.fedoraproject.org/updates/abrt-1.0.7-1.fc12
abrt-1.0.7-1.fc12 has been pushed to the Fedora 12 testing repository. If problems still persist, please make note of it in this bug report. If you want to test the update, you can install it with su -c 'yum --enablerepo=updates-testing update abrt'. You can provide feedback for this update here: http://admin.fedoraproject.org/updates/F12/FEDORA-2010-1598
abrt-1.0.7-1.fc12 tested and worked fine. The problem seems solved in this version. Thanks
abrt-1.0.7-1.fc12 has been pushed to the Fedora 12 stable repository. If problems still persist, please make note of it in this bug report.