Description of problem: abrt-gui fails to unpack debuginfo cpio archive Version-Release number of selected component (if applicable): 2.1.9-1.fc20 How reproducible: 100% Steps to Reproduce: 1. wait for something to crash (not difficult in fc20-beta) 2. start abrt-gui 3. say no to uploading coredump Actual results: abrt attempts to install debuginfo packages and gets: 2013-12-02-16:16:56 Coredump references 178 debuginfo files, 178 of them are not installed 2013-12-02-16:16:57 Setting up yum repositories 2013-12-02-16:16:57 Looking for needed packages in repositories 2013-12-02-16:16:57 Can't find packages for 139 debuginfo files 2013-12-02-16:16:57 Packages to download: 10 2013-12-02-16:17:00 Downloading 38.42Mb, installed size: 201.31Mb. Continue? 'YES' 2013-12-02-16:17:01 Downloading (1 of 10) cyrus-sasl-debuginfo-2.1.26-14.fc20.x86_64.rpm: 100% 2013-12-02-16:17:01 Extracting cpio from /var/tmp/abrt-tmp-debuginfo-2013-12-02-16:16:56.17521/cyrus-sasl-debuginfo-2.1.26-14.fc20.x86_64.rpm 2013-12-02-16:17:02 Caching files from unpacked.cpio made from cyrus-sasl-debuginfo-2.1.26-14.fc20.x86_64.rpm 2013-12-02-16:17:02 Can't extract files from '/var/tmp/abrt-tmp-debuginfo-2013-12-02-16:16:56.17521/unpacked.cpio' 2013-12-02-16:17:02 Unpacking failed, aborting download... 2013-12-02-16:17:02 Can't download debuginfos: 'DebugInfoDownload' object has no attribute 'cleanup_tmp_dir' 2013-12-02-16:17:02 Generating backtrace 2013-12-02-16:17:03 Backtrace is generated and saved, 24536 bytes 2013-12-02-16:17:05 Looking for similar problems in bugzilla 2013-12-02-16:17:08 Searching for updates 2013-12-02-16:17:09 No updates for this package found Expected results: abrt installs require debuginfo packages Additional info: The cpio archive that abrt complains about exists and is valid: # cpio -itv < /var/tmp/abrt-tmp-debuginfo-2013-12-02-16:16:56.17521/unpacked.cpio drwxr-xr-x 5 root root 0 Nov 15 09:31 ./usr/lib/debug drwxr-xr-x 24 root root 0 Nov 15 09:31 ./usr/lib/debug/.build-id drwxr-xr-x 2 root root 0 Nov 15 09:31 ./usr/lib/debug/.build-id/10 lrwxrwxrwx 1 root root 35 Nov 15 09:31 ./usr/lib/debug/.build-id/10/cffaea3a51f92b8fdaa24ecc9ec01983884f18 -> ../../../../bin/sasl2-sample-server lrwxrwxrwx 1 root root 39 Nov 15 09:31 ./usr/lib/debug/.build-id/10/cffaea3a51f92b8fdaa24ecc9ec01983884f18.debug -> ../../usr/bin/sasl2-sample-server.debug drwxr-xr-x 2 root root 0 Nov 15 09:30 ./usr/lib/debug/.build-id/14 ... Unfortunately due to this, I can't report the various other things on FC20 that are crashing right now.
This is a pretty critical bug as it prevents the filing of other fairly serious application crashes with meaningful stack traces. For example I have one seemingly gtk crash whenever evolution (and who knows what else) is run on the second screen of a dual-head configuration, which itself I think should quality at least critical if not blocker for the release.
Thank you for the report. If you have time to run the following commands $ cd /var/cache/abrt-di $ cpio -idu < /var/tmp/abrt-tmp-debuginfo-2013-12-02-16:16:56.17521/unpacked.cpio , please do so and report the results here.
Is this bug still reproducible?
I don't really know. I don't get many new crashes and all the ones I do get (repeatedly) are known so abrt doesn't really take any action on that. Perhaps we need to wait for FC21 to get new bugs to verify this on.
I think this has been reproduced in Bug 1169774 for Fedora 20 and Bug 1213485 for Fedora 21.
This message is a reminder that Fedora 20 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 20. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a Fedora 'version' of '20'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 20 is 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 change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. 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.
Fedora 20 changed to end-of-life (EOL) status on 2015-06-23. Fedora 20 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed.