Description of problem: This is very frustrating. Both waiting for something else to finish and verification are tasks that the user should be able to terminate without corrupting anything. Moreover, with verification, handling of TERM signal is apparently broken (the child happily proceeds with the verification, garbling the terminal output): (141/144): graphite2-devel-1.3.6-1.fc24.x86_64.rpm 1.3 MB/s | 43 kB 00:00 (142/144): libicu-devel-56.1-4.fc24.x86_64.rpm 16 MB/s | 750 kB 00:00 (143/144): svgalib-1.9.25-19.fc24.x86_64.rpm 8.3 MB/s | 426 kB 00:00 (144/144): links-2.12-2.fc24.x86_64.rpm 34 MB/s | 2.9 MB 00:00 ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- Total 9.8 MB/s | 46 MB 00:04 Running transaction check Waiting for process with pid 6782 to finish. ^C ^C ^Z [1]+ Stopped dnf builddep -y *.rpm [root@fedora24-2 freshrpm]# kill %1 [root@fedora24-2 freshrpm]# kill %1 [root@fedora24-2 freshrpm]# kill -KILL %1 [root@fedora24-2 freshrpm]# [1]+ Killed dnf builddep -y *.rpm [root@fedora24-2 freshrpm]# And: Cleanup : xerces-c-3.1.2-4.fc24.x86_64 52/55 Cleanup : perl-Encode-3:2.82-6.fc24.x86_64 53/55 Cleanup : openldap-2.4.43-2.fc24.x86_64 54/55 Cleanup : librdmacm-1.0.18.1-5.fc24.x86_64 55/55 Verifying : webkitgtk4-plugin-process-gtk2-2.12.0-3.fc24.x86_64 1/55 Verifying : brlapi-0.6.4-5.fc24.x86_64 2/55 Verifying : brltty-5.3.1-5.fc24.x86_64 3/55 ^C Verifying : python3-brlapi-0.6.4-5.fc24.x86_64 4/55 ^C Verifying : checkpolicy-2.5-2.fc24.x86_64 5/55 Verifying : grub2-1:2.02-0.30.fc24.x86_64 6/55 Verifying : grub2-tools-1:2.02-0.30.fc24.x86_64 7/55 ^Z [1]+ Stopped dnf -y update [root@fedora24-2 lkundrak]# kill %1 Verifying : grub2-efi-1:2.02-0.30.fc24.x86_64 8/55 Verifying : harfbuzz-1.2.5-1.fc24.x86_64 9/55 Verifying : harfbuzz-icu-1.2.5-1.fc24.x86_64 10/55 Verifying : ibus-typing-booster-1.4.0-3.fc24.noarch 11/55 Version-Release number of selected component (if applicable): dnf-1.1.8-1.fc24.noarch
Thanks for the report, we'll fix it.
This package has changed ownership in the Fedora Package Database. Reassigning to the new owner of this component.
This bug appears to have been reported against 'rawhide' during the Fedora 25 development cycle. Changing version to '25'.
Note there are more signals to deal with, e.g., SIGQUIT, see also [bug 1297522]. Anyway, I'd suggest behaviour similar to ipython: - 1st trigger of the signal -> emit info (perhaps even prompt to confirm the predetined action; if there are any childs, they should likely be sent SIGSTOP for the time being, possibly resumed later on with SIGCONT) - 2nd trigger of that signal -> proceed with the predestined action This is a preoccupation-proofing, I am sure I would appreciate such behaviour at times :-)
This message is a reminder that Fedora 25 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 25. 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 '25'. 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 25 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 25 changed to end-of-life (EOL) status on 2017-12-12. Fedora 25 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.