Comment 2 for bug 2005125

Have mysteriously resolved this while working on what I thought were unrelated dependency/permissions issues in the x86 vbox version of the same box. Wish I had a better answer to provide as to why this was happening, but seems to be fixed now.