Created attachment 1320333 [details] 'strace -ff' pk-command-not-found Description of problem: When nano is installed via C, the pk-command-not-fund process is terminated with the message 'Received SIGHUP or SIGTERM'. The nano pack has time to establish itself. ----------------------------------------------------------------------------------------------------------------------------- $ nano bash: nano: command not found... Install package 'nano' to provide command 'nano'? [N/y] y * Waiting in queue... * Loading list of packages.... The following packages have to be installed: nano-2.8.4-1.fc26.x86_64 A small text editor Proceed with changes? [N/y] y * Waiting in queue... * Waiting for authentication... * Waiting in queue... * Downloading packages... * Requesting data... * Testing changes... * Installing packages... Received SIGHUP or SIGTERM ----------------------------------------------------------------------------------------------------------------------------- Version-Release number of selected component (if applicable): PackageKit 1.1.6 nano 2.8.4 How reproducible: Without having to call a text editor from the terminal emulator's command line, agree to the offer to install the package. Steps to Reproduce: 1. The newly installed Fedora "26 (Workstation Edition)" with the latest updates on August 30, 2017. 2. Call 'nano' in the gnome-terminal. 3. Agree to install the 'nano' package. Actual results: The pk-command-not-found process ends with the message 'Received SIGHUP or SIGTERM'. The 'nano' package is installed, but it's not clear without checking. Expected results: After the end of PackageKit, the process of 'nano' is started. Additional info: I attach the trace ('stace -ff') of the process pk-command-not-found
This message is a reminder that Fedora 26 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 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 '26'. 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 26 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 26 changed to end-of-life (EOL) status on 2018-05-29. Fedora 26 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.