Comment 6 for bug 496360

This is caused by a recent change to the the way login.launchpad.net hosts the xrds files. They now being served statically but, for some reason, the content type changed from application/xrds+xml to application/xml on the user xrds docs. This broke the discovery process for the drupal module during completion as it checked for this content type in the response.

We're working with our sysadmins on a fix for this.