Comment 5 for bug 660260

I'm not sure if these have been modified since the issue existed sorry but they are what is currently on my system. The error is no longer present due the workaround described above. If you want anything else please let me know.