Has anybody else run across the situation yet where transmission* keeps spewing "Tracker: no dictionary in answer" errors?
I looked at the tracker responses, and they seemed fine. (Not that I know the details of the protocol.) I suspect transmission just fails to parse them. It keeps hammering away at the tracker for a "correct" response, which looks like a fairly serious bug. -- Christian "naddy" Weisgerber [EMAIL PROTECTED]
