http://bugzilla.opensuse.org/show_bug.cgi?id=1044931 Bug ID: 1044931 Summary: broken virtualbox-guest-tools installation Classification: openSUSE Product: openSUSE Distribution Version: Leap 42.2 Hardware: x86-64 OS: Windows 7 Status: NEW Severity: Major Priority: P5 - None Component: Virtualization:Tools Assignee: virt-bugs@suse.de Reporter: M.Kraft@gmx.com QA Contact: qa-bugs@suse.de Found By: --- Blocker: --- Hi *, I have an OpenSUSE Leap 42.2 installed as guest in a VirtualBox 5.1.22 on Windows 7 x86_64. I tried to install the current virtualbox-guest-tools-5.1.22-19.21.1 from the update repo. Although the installation succeeded, it is unusable. ---- # rpm -q virtualbox-guest-tools virtualbox-guest-tools-5.1.22-19.21.1.x86_64 ---- 1) Trying to 'systemctl start vboxadd' gives in 'journalctl -xe': ---- Jun 19 12:56:18 xxx systemd[1]: Starting LSB: VirtualBox Linux Additions kernel modules... -- Subject: Unit vboxadd.service has begun start-up -- Defined-By: systemd -- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel -- -- Unit vboxadd.service has begun starting up. Jun 19 12:56:18 xxx vboxadd[2267]: /etc/init.d/vboxadd: line 118: .: filename argument required Jun 19 12:56:18 xxx vboxadd[2267]: .: usage: . filename [arguments] Jun 19 12:56:18 xxx systemd[1]: vboxadd.service: Control process exited, code=exited status=2 Jun 19 12:56:18 xxx systemd[1]: Failed to start LSB: VirtualBox Linux Additions kernel modules. -- Subject: Unit vboxadd.service has failed -- Defined-By: systemd -- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel -- -- Unit vboxadd.service has failed. -- -- The result is failed. Jun 19 12:56:18 xxx systemd[1]: vboxadd.service: Unit entered failed state. Jun 19 12:56:18 xxx systemd[1]: vboxadd.service: Failed with result 'exit-code'. ---- The problematic line 118 in /etc/init.d/vboxadd is: ---- 116 117 if test -r $config; then 118 . $config 119 else 120 fail "Configuration file $config not found" ---- Up to this point $config is not defined in the script. 2) Maybe related, but I am not sure, I also found that the sysv migration handling is defective. There is a typo in the RPM scriptlets leading to: ---- # ls /var/lib/systemd/migrated/vb* /var/lib/systemd/migrated/vboadd /var/lib/systemd/migrated/vboxadd-service ---- read: actual 'vboadd' vs. expected 'vboxadd' Its wrong throughout preinstall, but correct in postinstall, which is why the postinstall scriptlet is ineffective. 3) While looking for possible trouble sources I stumbled over another one, which might or might not be relevant here. Checking if all files are installed I found that vboxguestconfig is installed without execution permission: ---- # for f in `rpm -ql virtualbox-guest-tools`; do ls -ld "$f"; done [...] -rw-r--r-- 1 root root 1423 Jun 8 15:33 /sbin/vboxguestconfig [...] ---- Please review and fix if possible. Thank you very much! -- Matthias Kraft -- You are receiving this mail because: You are on the CC list for the bug.