Description of problem: Today empathy/telepathy crashed on my system. I want to report the crash via ABRT. I chose to analyze the crash using the local gdb method. In the "Analyzing" step error messages started to appear at a rate about 1 per second: /var/cache/abrt-di is 5324102002 bytes (more than 4096 MB), deleting '/var/cache/abrt-di/usr/lib/debug/usr/lib64/xulrunner-2/libxul.so.debug' Can't unlink '/var/cache/abrt-di/usr/lib/debug/usr/lib64/xulrunner-2/libxul.so.debug': Permission denied /var/cache/abrt-di is 5324102002 bytes (more than 4096 MB), deleting '/var/cache/abrt-di/usr/lib/debug/usr/lib64/xulrunner-2/libxul.so.debug' Can't unlink '/var/cache/abrt-di/usr/lib/debug/usr/lib64/xulrunner-2/libxul.so.debug': Permission denied ... At first I thought it was an infinite loop, but eventually it ended. Using wc I counted there were 999 tries before it finished with: ... Can't unlink '/var/cache/abrt-di/usr/lib/debug/usr/lib64/xulrunner-2/libxul.so.debug': Permission denied Analyzing coredump '/home/michich/.abrt/spool/ccpp-2011-04-23-06:33:47-2240/coredump' Všech 24 souborů s ladicími informacemi je k dostupných Backtrace is generated and saved, 3325 bytes Version-Release number of selected component (if applicable): abrt-2.0.1-2.fc15.x86_64 abrt-desktop-2.0.1-2.fc15.x86_64 abrt-gui-2.0.1-2.fc15.x86_64 abrt-plugin-logger-2.0.1-2.fc15.x86_64 abrt-addon-python-2.0.1-2.fc15.x86_64 abrt-cli-2.0.1-2.fc15.x86_64 abrt-libs-2.0.1-2.fc15.x86_64 abrt-addon-kerneloops-2.0.1-2.fc15.x86_64 abrt-plugin-bugzilla-2.0.1-2.fc15.x86_64 abrt-addon-ccpp-2.0.1-2.fc15.x86_64 How reproducible: Well I have not tested it, but I guess it will happen again when I try to report another crash. There's still 5.2 GiB of files under it. Actual results: 999 repeated errors. Expected results: A "permission denied" error won't just go away, so don't try the same operation over and over again. I am not familiar with the architecture of ABRT, but perhaps it was trying to delete the debug files using a wrong UID? Additional info: $ ls -ld /var/cache/abrt-di/usr/lib/debug/usr/lib64/xulrunner-2/ drwxr-xr-x. 3 abrt abrt 4096 4. bře 10.11 /var/cache/abrt-di/usr/lib/debug/usr/lib64/xulrunner-2/
If you don't mind downloading symbols again, a workaround might be to remove everything in /var/cache/abrt-di/. Although I haven't encountered this bug, I have done that, and abrt seems to handle it fine. With the debuginfo for dconf-editor: $ du -sh /var/cache/abrt-di/ 847M /var/cache/abrt-di/ abrt-2.0.1-2.fc15.x86_64
Closing - this should be fixed in git by commit 67a3602e83af42f932e0583d7385d9bcf7ea7e16
abrt-2.0.2-1.fc15 has been submitted as an update for Fedora 15. https://admin.fedoraproject.org/updates/abrt-2.0.2-1.fc15
Package abrt-2.0.2-1.fc15: * should fix your issue, * was pushed to the Fedora 15 testing repository, * should be available at your local mirror within two days. Update it with: # su -c 'yum update --enablerepo=updates-testing abrt-2.0.2-1.fc15' as soon as you are able to. Please go to the following url: https://admin.fedoraproject.org/updates/abrt-2.0.2-1.fc15 then log in and leave karma (feedback).
abrt-2.0.2-3.fc15 has been submitted as an update for Fedora 15. https://admin.fedoraproject.org/updates/abrt-2.0.2-3.fc15
This message is a notice that Fedora 15 is now at end of life. Fedora has stopped maintaining and issuing updates for Fedora 15. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At this time, all open bugs with a Fedora 'version' of '15' have been closed as WONTFIX. (Please note: Our normal process is to give advanced warning of this occurring, but we forgot to do that. A thousand apologies.) Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, feel free to reopen this bug and simply change the 'version' to a later Fedora version. Bug Reporter: Thank you for reporting this issue and we are sorry that we were unable to fix it before Fedora 15 reached end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged to click on "Clone This Bug" (top right of this page) and open it against that version of Fedora. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete. The process we are following is described here: http://fedoraproject.org/wiki/BugZappers/HouseKeeping