On Tue, 31 Mar 2015 15:39:13 -0500, John McKown wrote:
Hum, on my system, I get the message you are expecting. Transcript:
-snip-
And, here...
This is puzzling.
On an older Ubuntu 10.04 system I still use (I know, I know...) I
get _no_ response. But the return code appears correct:
On Wed, Apr 01, 2015 at 05:21:42PM +, Allodoxaphobia wrote:
On an older Ubuntu 10.04 system I still use (I know, I know...) I
get _no_ response. But the return code appears correct:
jonesy@nix4:~$ uname -a
Linux nix4 2.6.32-39-generic #86-Ubuntu SMP Mon Feb 13 21:47:32 UTC 2012 i686
Hum, on my system, I get the message you are expecting. Transcript:
$ uname -a
Linux it-johnmckown-linux 3.19.1-201.fc21.x86_64 #1 SMP Wed Mar 18
04:29:24 UTC 2015 x86_64 x86_64 x86_64 GNU/Linux
[tsh009@it-johnmckown-linux junk]$ bash --version
GNU bash, version 4.3.33(1)-release
Configuration Information [Automatically generated, do not change]:
Machine: x86_64
OS: linux-gnu
Compiler: gcc
Compilation CFLAGS: -DPROGRAM='bash' -DCONF_HOSTTYPE='x86_64'
-DCONF_OSTYPE='linux-gnu' -DCONF_MACHTYPE='x86_64-redhat-linux-gnu'
-DCONF_VENDOR='redhat' -DLOCALEDIR='/usr/share/locale'
It was fixed a year ago:
https://github.com/hughsie/PackageKit/commit/b8f5de2e0ceaf7424e4e2c94adc46fa06eefce73
On Tue, Mar 31, 2015 at 1:04 PM, Robin A. Meade robin.a.me...@gmail.com
wrote:
ok, thanks. If I run bash with no startup files, I get expected output.
With my regular start-up
ok, thanks. If I run bash with no startup files, I get expected output.
With my regular start-up files:
$ declare -f command_not_found_handle
command_not_found_handle ()
{
runcnf=1;
retval=127;
[ ! -S /var/run/dbus/system_bus_socket ] runcnf=0;
[ ! -x /usr/libexec/packagekitd ]
