Description of problem: Dump emits erroneous output. Version-Release number of selected component (if applicable): How reproducible: 100% Steps to Reproduce: 1. run dump using on any filesystem using "-A somefilename.toc" 2. I also use the "-L" and "-z2" switches but doubt that has anything to do 3. the requested TOC file is generated but so is the following message to the console - NOT the middle line is wrong about the NULL: DUMP: Wrote 15833450kB uncompressed, 5657014kB compressed, 2.799:1 DUMP: Archiving dump to (null) DUMP: DUMP IS DONE Actual results: Archive works fine - toc file made and OK Expected results: Middle liine should be DUMP: Archiving dump to whateverfilename.Igave Additional info: While nothing is truly wrong, the information posted makes you suspect there is a problem.
This package has changed maintainer in the Fedora. Reassigning to the new maintainer of this component.
This message is a reminder that Fedora 30 is nearing its end of life. Fedora will stop maintaining and issuing updates for Fedora 30 on 2020-05-26. 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 '30'. 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 30 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.
This message is a reminder that Fedora 31 is nearing its end of life. Fedora will stop maintaining and issuing updates for Fedora 31 on 2020-11-24. 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 '31'. 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 31 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.
Still the same bug in 5.8.16-200.fc32.x86_64.
FEDORA-2021-7d627951a0 has been submitted as an update to Fedora 32. https://bodhi.fedoraproject.org/updates/FEDORA-2021-7d627951a0
FEDORA-2021-2583417b8d has been submitted as an update to Fedora 33. https://bodhi.fedoraproject.org/updates/FEDORA-2021-2583417b8d
FEDORA-2021-7d627951a0 has been pushed to the Fedora 32 stable repository. If problem still persists, please make note of it in this bug report.
FEDORA-2021-2583417b8d has been pushed to the Fedora 33 stable repository. If problem still persists, please make note of it in this bug report.
It appears to be fixed. Thanks.