There are two problems here
1. You need to use stderr, not stdout
2. You need a newline at the end
that may confuse existing scripts and practices as this behavior deviates from standard shell error reporting. In fact, 2. is pretty annoying given this behavior when logging in via ssh (e.g. not authorized to install software):
[davidz@yamato ~]$ this-command-does-not-exist
Command not found. [davidz@yamato ~]$
Anyway, FYI, in particular, I'm running into this problem with the udisks "D-Bus over TCP/IP over ssh tunnel" feature as there is no good way to report errors other than looking at stderr (e.g. can't check $?) - in this case the Palimpsest client writes "udisks-tcp-bridge -p <number>" and then reads stderr. Once there's a whole line of output from stderr, we check whether it's something expected (e.g. "udisks-tcp-bridge: Waiting for secret") or something else like "bash: udisks-tcp-bridge: command not found".
PackageKit-command-not-found obviously breaks this and makes my client hang if there is no udisks-tcp-bridge binary in the users $PATH on the machine being logged into.
I'm imagining there's a bunch of existing scripts that suffers from this too. Would probably be good to fix in F12 too.
Thanks for fixing this.
(In reply to comment #0)
> 2. You need a newline at the end
This should be fixed with 0.5.5 in updates-testing already.
> 1. You need to use stderr, not stdout
This isn't fixed.
> I'm imagining there's a bunch of existing scripts that suffers from this too.
> Would probably be good to fix in F12 too.
Author: Richard Hughes <firstname.lastname@example.org>
Date: Tue Dec 8 10:12:42 2009 +0000
cnf: ensure we send error messages to stderr, not stdout. Fxes rh#545220
I'll do a post-0.5.5 fixes rollup at the start of next week as there's another couple of little bugs that fell through the cracks for 0.5.5.
(In reply to comment #1)
> I'll do a post-0.5.5 fixes rollup at the start of next week as there's another
> couple of little bugs that fell through the cracks for 0.5.5.
Great, thanks for fixing this.
*** Bug 550954 has been marked as a duplicate of this bug. ***
PackageKit-0.5.6-1.fc12 has been submitted as an update for Fedora 12.
PackageKit-0.5.6-1.fc12 has been pushed to the Fedora 12 testing repository. If problems still persist, please make note of it in this bug report.
If you want to test the update, you can install it with
su -c 'yum --enablerepo=updates-testing update PackageKit'. You can provide feedback for this update here: http://admin.fedoraproject.org/updates/F12/FEDORA-2010-0193
PackageKit-0.5.6-1.fc12 has been pushed to the Fedora 12 stable repository. If problems still persist, please make note of it in this bug report.
This bug appears to have been reported against 'rawhide' during the Fedora 13 development cycle.
Changing version to '13'.
More information and reason for this action is here:
PackageKit hooks in a place where shell users don't expect it to hook in, so I would really like if it told that PackageKit had been started and if the output was prefixed with PackageKit.
That (and other changes) would make the system much more explorable and less magic.
This message is a reminder that Fedora 13 is nearing its end of life.
Approximately 30 (thirty) days from now Fedora will stop maintaining
and issuing updates for Fedora 13. 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 WONTFIX if it remains open with a Fedora
'version' of '13'.
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 prior to Fedora 13's end of life.
Bug Reporter: Thank you for reporting this issue and we are sorry that
we may not be able to fix it before Fedora 13 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 please change the 'version' of this
bug to the applicable version. If you are unable to change the version,
please add a comment here and someone will do it for you.
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.
The process we are following is described here:
Fedora 13 changed to end-of-life (EOL) status on 2011-06-25. Fedora 13 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.
Thank you for reporting this bug and we are sorry it could not be fixed.