Starting and using the VirtualBox GUI (virtualbox) works the first time no configuration (VirtualBox.xml) exists. Creating a VM (and using it) works ok. However restarting the GUI -> Segmentation fault. Deleting the configuration helps. vboxmanage is not affected, creating, modifying and staring VMs is ok. If a VM is started with vboxmanage startvm ... and then virtualbox (while the VM is running) -> NO segmentation fault. Reproducible: Always Steps to Reproduce: 1. Start virtualbox, create a VM, start it. Exit virtualbox 2. Start virtualbox -> Segmentation fault 3. Delete VirtualBox.xml 4. Start virtualbox -> OK 5. Create a VM, exit virtualbox. 6. Start the VM with vboxmanage startvm ... 7. Start virtualbox -> OK Actual Results: Segmentation fault with existing configuration or no VM running. Expected Results: No Segmentation fault with configuration and no VM running.
Created attachment 124174 [details] emerge --info
Does it work with the -bin version?
Changing permissions of VirtualBox.xml and <your_vm_name>.xml for each virtual machine from 0600 to 0644 resolved the issue for me.
(In reply to comment #3) actually seems not. it started to fall with segmentation faults again after some restarts.
Tried the -bin version, same problem. Also changing permissions of the .xml files does not help here.
when bin is also affected, highly your system is broken in a subtle way as the bin is used all over the place. I suggest double checking your system, marking invalid for now. Feel free to reopen if you can track down how this happens
