>> Try with "sudo su -"
Thanks for the suggestion, as soon as I'll have access to that machine again I'll try that. I tried to reproduce the same on a clean Ubuntu VM with the same VirtualBox build at home and didn't even run into the issue with simply calling my binary with "sudo". So I assume something is wrong with that particular machine (I updated from 4.3.x to 5.0.x - maybe that broke something).
_______________________________________________ vbox-dev mailing list vbox-dev@virtualbox.org https://www.virtualbox.org/mailman/listinfo/vbox-dev
