/etc/profile.d/speechd-user-port.sh references $USER

This bug was fixed in the package speech-dispatcher - 0.7-5ubuntu1

---------------
speech-dispatcher (0.7-5ubuntu1) maverick; urgency=low

  * Merge from debian unstable. Remaining changes:
    - Python-speechd should depend on speech-dispatcher
    - Moved the flite output module to a separate package, and added
      it to suggests
    - Use cdbs for package build, cleaner to maintain
    - Quieten logfiles by default
    - Only enable espeak output module
    - Fix pulse driver endainness
    - Fix broken spd-conf
  * debian/speech-dispatcher.init: Don't assume that the user was previously
    running speech-dispatcher system-wide, at least in Ubuntu
  * Remove references to speechd-server-spawn and speechd-user-port.sh, since
    speech-dispatcher now has a different way of spawning, and uses sockets
    (LP: #601114)
  * Flite patch from Debian fixes FTBFs (LP: #601005)
  * debian/patches/spd-conf-test-path-fix.patch: Fix path to test.wav file
    which gets played by spd-conf (LP: #314185)

speech-dispatcher (0.7-5) unstable; urgency=low

  * Move Python build dependencies from Build-Depends-Indep to Build-Depends;
    closes: #588107.
  * Standards 3.9.0 (no real change).

speech-dispatcher (0.7-4) unstable; urgency=low

  * Default AudioOutputMethod changed to "pulse" to prevent blocking audio
    output; information to README.Debian added.

speech-dispatcher (0.7-3) unstable; urgency=low

  * Paths in python-speechd adjusted to match Debian installation.
  * Package priorities set to match override entries.

speech-dispatcher (0.7-2) unstable; urgency=low

  * Link speech-dispatcher log location to /var/log/speech-dispatcher/, if
    it doesn't exist yet.
  * Permit access to speech-dispatcher socket to `audio' group.

speech-dispatcher (0.7-1) unstable; urgency=low

  * New upstream version.
  * Switch to dpkg-source 3.0 (quilt) format.
  * Versioned build dependency on flite-dev.
  * Don't start Speech Dispatcher by default; closes: #577217.
  * Standards 3.8.4 (no real change).
 -- Luke Yelavich <email address hidden> Thu, 15 Jul 2010 14:30:18 +1000

Would a backport into Lucid be possible for this? cron jobs which source /etc/profile.d wind up always returning this message, making cron jobs which should only output on error give output every time. Perhaps it could be patched more minimally than was done for Maverick, but some fix for Lucid would be much appreciated.

Setting LOGNAME in every login shell is required by POSIX. There's no such requirement for USER. The best practice is to bootstrap USER from LOGNAME wherever it's used. The environ(7) man page should be updated to reflect this.

At the very least, the offending /etc/profile.d/speechd-user-port.sh file should be removed on upgrade to maverick, as the file is not needed anymore. I filed bug #683845 about this.

There are other problems with the profile shell fragment:

- it assumes that the id never will be higher than the max port
- it guesses that the generated port number is free
- getent gets confused by numeric usernames

Also reported in Bug #696758.