Description of problem: While downloading debuginfo packages the abrt window shows a very unhelpful message that says: No handlers could be found for logger "dnf" I have no idea what this means or if it's a problem or if I'm supposed to do anything about it, so why bother displaying it to the user? Version-Release number of selected component (if applicable): abrt-2.6.0-1.fc22.x86_64 dnf-1.0.1-2.fc22.noarch How reproducible: Always Steps to Reproduce: 1. report a crash in abrt 2. when prompted to upload the core file say no 3. start downloading the debuginfo packages to create a backtrace Actual results: Status line says [No handlers could be found for logger "dnf"] and then appears to be doing nothing for a long time (with the "working" icon spinning, but I can't tell if the process has just got stuck). It is unclear if a problem has happened that requires user interaction, or if "No handlers could be found" is not a problem and can be ignored. Expected results: If the reporting process is still working then the status should indicate something is ongoing, it should not show what appears to be an error with no clue how whether the user needs to do anything. Expanding the full log gives no more information that anything is still progressing, until eventually some more lines are printed indicating work is still happening. Additional info: Full log shows: --- Running report_uReport --- ('report_uReport' completed successfully) --- Running analyze_CCpp --- Ok to upload core dump? (It may contain sensitive data). If your answer is 'No', a stack trace will be generated locally. (It may download a huge amount of data). 'NO' Analyzing coredump 'coredump' Cannot get real path for '/home/jwakely/.config/abrt/settings/libreport.conf': Permission denied Coredump references 84 debuginfo files, 50 of them are not installed Initializing package manager Setting up repositories No handlers could be found for logger "dnf" Looking for needed packages in repositories Can't find packages for 2 debuginfo files Packages to download: 26 Downloading 161.28Mb, installed size: 671.76Mb. Continue? 'YES' ...
Thank you for the report! Upstream commit https://github.com/abrt/libreport/commit/6536b2daef9b6ffb700ea9508aea9be590e6ac7a fixes this bug.
libreport-2.6.1-1.fc22,abrt-2.6.1-1.fc22,satyr-0.19-1.fc22 has been submitted as an update for Fedora 22. https://admin.fedoraproject.org/updates/libreport-2.6.1-1.fc22,abrt-2.6.1-1.fc22,satyr-0.19-1.fc22
Package libreport-2.6.1-1.fc22, abrt-2.6.1-1.fc22, satyr-0.19-1.fc22: * should fix your issue, * was pushed to the Fedora 22 testing repository, * should be available at your local mirror within two days. Update it with: # su -c 'yum update --enablerepo=updates-testing libreport-2.6.1-1.fc22 abrt-2.6.1-1.fc22 satyr-0.19-1.fc22' as soon as you are able to. Please go to the following url: https://admin.fedoraproject.org/updates/FEDORA-2015-11434/libreport-2.6.1-1.fc22,abrt-2.6.1-1.fc22,satyr-0.19-1.fc22 then log in and leave karma (feedback).
libreport-2.6.1-1.fc22, abrt-2.6.1-1.fc22, satyr-0.19-1.fc22 has been pushed to the Fedora 22 stable repository. If problems still persist, please make note of it in this bug report.