Oracle Linux 6 : gconf-sanity-check-2 Exited With Status 256

If you see an error about gconf-sanity-check-2, apply the following solutions (note you may need to apply all the solutions):

Fix #1: /tmp permission

You need to make sure /tmp permissions are with the sticky bit mode. An access-right flag on /tmp can be set as follows.

# ls -ld /tmp/
Sample outputs without sticky bit:

drwxr-xr-x 27 vivek users 12288 Jul 18 15:20 /tmp/

Set the correct permission and stick bit as follows (run it as root user):

# chown -R root:root /tmp

# chmod 1777 /tmp

Verify new permissions:

# ls -ld /tmp/

Sample outputs:



drwxrwxrwt 27 root root 12288 Jul 18 15:25 /tmp/



Fix #2: /home permission


Make sure /home has correct permission set. A typical set of permission looks as follows on /home

$ ls -ld /home/

Sample outputs:


drwxr-xr-x 4 root root 4096 May  5 16:29 /home/
If permisions are not as above set it as follows (run it as root user):

# chown root:root /home

# chmod 0755 /home









Try rebooting the system after applying above two solutions. If you 
still getting the message, empty the gdm home. Run it as root (this for 
gdm3):





# rm -rf /var/lib/gdm3/.*

For older gnome version (gdm 2) try:

# rm -rf /var/lib/gdm/.*

VT-X IS BEING USED BY ANOTHER HYPERVISOR (VERR_VMX_IN_VMX_ROOT_MODE)

It depend on your cpu.

If you get a error saying that the service is still running, then run the follwing command to stop the service before removing it.:

# rmmod -f kvm_intel

Reboot the computer after that :

# apt-get remove libvirt-bin

And finally, the modprobe command :

# modprobe -r kvm_intel

After that, you can run Virtualbox wihtout any error.