On Wed, Jun 14, 2017 at 5:54 PM, Cameron Simpson <cs@xxxxxxxxxx> wrote:
On 14Jun2017 12:52, Matt Morgan <minxmertzmomo@xxxxxxxxx> 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 trying to check for what package provides that command,
but failing.
Has anyone else seen this? What can I do about it?
Apologies if this is a common error--it's resistant at least to the search
terms I can think of.
You can sometimes see external stuff by running this:
(set -x; pv )
If this is entire bash-internal then it won't help, and if it happens in bash's prompt logic it won't help, but this might:
set -x; pv
Sounds like others have named the offending thing; this is just debugging help.
Cheers,
Cameron Simpson <cs@xxxxxxxxxx>
Thanks, everyone. Interesting that nobody had a fix for the (humorously named) PackageKit-command-not-found issue, i.e., all respondents were just happy trashing it. I work on new computers a lot and don't always keep track of what packages I install, so (although I agree it's weird and not a very unixy/linuxy way to do things) I actually wouldn't mind if it ever worked again! In the meantime, I have also trashed it.
Best,
Matt
_______________________________________________ users mailing list -- users@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to users-leave@xxxxxxxxxxxxxxxxxxxxxxx
