Comment 58 for bug 510571

@undefined:
Yes, I'm aware of that problem, but as stated earlier, it does not seem as though the patch here fixes it, so presumably there are more issues in need of addressing in the hardy version of virtualbox. And I really don't have many a clue on how to do so.

Since the version in hardy is quite old there are a lot of revisions that have gone into vbox since, and the way to solve it would be to figure out what specific revision(s), presumably in addition to the ones in this here patch, which does address the issue. Or simply request that a later version of virtualbox be put in the -backports repository, which may be added by users if need be.

I do not intend to poke any further in this matter currently.