> The work-around suggested in the duplicate report #328181, of moving the svn subdirectory out of the plugins directory is effective
Just to be clear, this work-around completely disables svn integration right? I just mention this so no one gets the wrong idea when you say it is "effective". It is "effective" in the sense that it makes the error go away, not in the sense that it actually fixes the problem.
> The work-around suggested in the duplicate report #328181, of moving the svn subdirectory out of the plugins directory is effective
Just to be clear, this work-around completely disables svn integration right? I just mention this so no one gets the wrong idea when you say it is "effective". It is "effective" in the sense that it makes the error go away, not in the sense that it actually fixes the problem.
I found if I rebooted the problem actually went away. /bugs.launchpad .net/bugs/ 328181
More details on the other bug report:
https:/