This might be due to some subtle incompatibility introduced by
[737e76a69fbc2e] or a related check-in.  Do you have the same problem
using a client built from the latest code, or is this only an issue
with older clients?