Note that though this appears to be a continuation of an old bug, reading the earlier comments suggests that it was an issue with the ownership of .Xauthority. It seems that the new problem is not that but is related to the contents of the file.
Note that though this appears to be a continuation of an old bug, reading the earlier comments suggests that it was an issue with the ownership of .Xauthority. It seems that the new problem is not that but is related to the contents of the file.