** Description changed: Exiting the noping command with ^C leaves the terminal in an odd state where newline does not do anything. Starting "reset" brings the terminal back to a sane state. - - This does not occur in the Debian version 1.10.0-2+b1 ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: oping 1.10.0-1build1 ProcVersionSignature: Ubuntu 4.15.0-21.22-generic 4.15.17 Uname: Linux 4.15.0-21-generic x86_64 ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 CurrentDesktop: LXQt Date: Mon May 14 01:22:36 2018 InstallationDate: Installed on 2016-01-20 (844 days ago) InstallationMedia: Xubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) SourcePackage: liboping UpgradeStatus: No upgrade log present (probably fresh install)
** Description changed: Exiting the noping command with ^C leaves the terminal in an odd state where newline does not do anything. Starting "reset" brings the terminal back to a sane state. + + This seems to occur when one of the hosts to be pinged does not answer. + When this occurs, noping exits with the message: + + ping_send failed: Interrupted system call ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: oping 1.10.0-1build1 ProcVersionSignature: Ubuntu 4.15.0-21.22-generic 4.15.17 Uname: Linux 4.15.0-21-generic x86_64 ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 CurrentDesktop: LXQt Date: Mon May 14 01:22:36 2018 InstallationDate: Installed on 2016-01-20 (844 days ago) InstallationMedia: Xubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) SourcePackage: liboping UpgradeStatus: No upgrade log present (probably fresh install) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1771038 Title: Exiting noping cli command leaves terminal in a broken state To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/liboping/+bug/1771038/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
