Description of problem: When a command is not available on the system, xxx (shell, dnf, ???) offers to install it. If the user agree the package needed is installed, but it isn't logged at all. - dnf history doesn't list the package installation - the package installation doesn't appear in /var/log/dnf.log or dnf.rpm.log Version-Release number of selected component (if applicable): Fedora 22 x86_64 dnf 1.0.0-1 How reproducible: Steps to Reproduce: 1. type a command not available on the system 2. reply "yes" 3. check "dnf history" and /var/log/dnf.log Actual results: The new package(s) installed don't appear in the log nor history Expected results: dnf history should list the packages installed dnf log should list the packages installed Additional info:
I doubt the package was installed by dnf when there's no evidence of installation in the logs. Could toy please provide us more detailed reproducer with all output and error messages? I cant reproduce it on F22: # command_not_available_on_the_system -bash: command_not_available_on_the_system: command not found
This is not a DNF feature for sure. And AFAIK, this is not even YUM's feature. I guess that the functionality is provided by PackageKit [1]. Since PackageKit does not use DNF, I believe that it its actions shouldn't be recorded in DNF's history. [1] https://fedoraproject.org/wiki/Features/PackageKitCommandNotFound
Maybe this will be the best place where to store such information: bug 1167239
Hello, Indeed, it is due to PackageKitCommandNotFound feature. I'll add a reference in bug 1167239 to track this issue. Thank you. Maxime
Fedora 22 changed to end-of-life (EOL) status on 2016-07-19. Fedora 22 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.