I found out one of the issues is when you login and are using /bin/sh, instead of /bin/bash for your login shell. This is still occuring on Debian Lenny to current date. When I login as a user using /bin/sh, it proves to find this bug immediately. When after logging in, I run bash as a new shell, it resolves it for that session, until I exit that shell and return back to sh.
Eric Renfro
