As covered in https://bugzilla.novell.com/show_bug.cgi?id=1136761, some users are unable to start VirtualBox due to a missing SUID in the permissions for /usr/lib/virtualbox/VirtualBoxVM. Changing the permissions for that file does not always work, but 'sudo chkstat --system" does. One of the users ran a "sudo zypper in --force virtualbox", who got the following additional rpm output: Additional rpm output: /usr/lib/virtualbox/VBoxNetNAT: will not give away s-bits on an insecure path ERROR: not all operations were successful. setting /usr/lib/virtualbox/VBoxNetNAT to root:vboxusers 4750. (wrong permissions 0750) /usr/lib/virtualbox/VBoxNetDHCP: will not give away s-bits on an insecure path ERROR: not all operations were successful. setting /usr/lib/virtualbox/VBoxNetDHCP to root:vboxusers 4750. (wrong permissions 0750) /usr/lib/virtualbox/VBoxNetAdpCtl: will not give away s-bits on an insecure path ERROR: not all operations were successful. setting /usr/lib/virtualbox/VBoxNetAdpCtl to root:vboxusers 4750. (wrong permissions 0750) /usr/lib/virtualbox/VBoxHeadless: will not give away s-bits on an insecure path ERROR: not all operations were successful. setting /usr/lib/virtualbox/VBoxHeadless to root:vboxusers 4750. (wrong permissions 0750) On my system, I got the lines about setting permissions, but not the error lines. The other user gets the problem intermittently after a "zypper dup", thus I am assuming that I get the "correct" results. What might be wrong to generate the "will not give away s-bits on an insecure path" message? We have verified that both of us have "easy" permissions set. Thanks, Larry -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org