Re: terminal hangs looking for missing commands

2017-06-15 Thread Rick Stevens
On 06/15/2017 12:28 PM, Matt Morgan wrote: > On Wed, Jun 14, 2017 at 5:54 PM, Cameron Simpson > wrote: > > On 14Jun2017 12:52, Matt Morgan > wrote: > > On a newish computer with F25, I see this at the command line >

Re: terminal hangs looking for missing commands

2017-06-15 Thread Matt Morgan
On Wed, Jun 14, 2017 at 5:54 PM, Cameron Simpson wrote: > On 14Jun2017 12:52, Matt Morgan wrote: > >> On a newish computer with F25, I see this at the command line when I type >> in a command that's not installed: >> >> [matt@envious ~]$ pv >> bash: pv: command not found... >> >> and then it jus

Re: terminal hangs looking for missing commands

2017-06-14 Thread Cameron Simpson
On 14Jun2017 12:52, Matt Morgan wrote: On a newish computer with F25, I see this at the command line when I type in a command that's not installed: [matt@envious ~]$ pv bash: pv: command not found... and then it just sits there until I ctrl-c or similar. I assume what's happening is it's tryin

Re: terminal hangs looking for missing commands

2017-06-14 Thread Rick Stevens
On 06/14/2017 09:52 AM, Matt Morgan wrote: > On a newish computer with F25, I see this at the command line when I > type in a command that's not installed: > > [matt@envious ~]$ pv > bash: pv: command not found... > > and then it just sits there until I ctrl-c or similar. I assume what's > happen

Re: terminal hangs looking for missing commands

2017-06-14 Thread Tom Horsley
On Wed, 14 Jun 2017 12:52:09 -0400 Matt Morgan wrote: > Has anyone else seen this? What can I do about it? The very first time I saw that I spent hours tracking down the "PackageKit-command-not-found" package and taking great pleasure in running the command: dnf erase PackageKit-command-not-foun

terminal hangs looking for missing commands

2017-06-14 Thread Matt Morgan
On a newish computer with F25, I see this at the command line when I type in a command that's not installed: [matt@envious ~]$ pv bash: pv: command not found... and then it just sits there until I ctrl-c or similar. I assume what's happening is it's trying to check for what package provides that