Virtualbox: error during installation of v6.0.4-3.2

Today during “zypper dup” I got an error from the virtualbox-6.0.4-3.2 package.
The problem arose during the execution of the /usr/lib/virtualbox/vboxdrv.sh script.
This is the error:

apr 12 20:19:38 polarisuse systemd[1]: Starting VirtualBox Linux kernel module...
apr 12 20:19:38 polarisuse vboxdrv.sh[11974]: vboxdrv.sh: Starting VirtualBox services.
apr 12 20:19:38 polarisuse vboxdrv.sh[11974]: /usr/lib/virtualbox/vboxdrv.sh: line 224: setup: command not found
apr 12 20:19:38 polarisuse vboxdrv.sh[11974]: vboxdrv.sh: failed: modprobe vboxdrv failed. Please use 'dmesg' to find out why.

There is nothing enlightening in dmesg:

cris@polarisuse ~]**$** dmesg|tail
  728.700863] BTRFS info (device sdb3): disk space caching is enabled
  728.700866] BTRFS info (device sdb3): has skinny extents
  728.720597] BTRFS info (device sdb3): enabling ssd optimizations
  729.802021] BTRFS info (device sdb3): disk space caching is enabled
  729.802025] BTRFS info (device sdb3): has skinny extents
  729.820403] BTRFS info (device sdb3): enabling ssd optimizations
  731.630171] BTRFS info (device sdb3): disk space caching is enabled
  731.630173] BTRFS info (device sdb3): has skinny extents
  731.648875] BTRFS info (device sdb3): enabling ssd optimizations
  735.536763] VBoxPciLinuxLinuxUnload

I tried manually executing the script again and got the same error:

cris@polarisuse ~]**$** LANG=C sudo /usr/lib/virtualbox/vboxdrv.sh start  
vboxdrv.sh: Starting VirtualBox services.
/usr/lib/virtualbox/vboxdrv.sh: line 224: setup: command not found
vboxdrv.sh: failed: modprobe vboxdrv failed. Please use 'dmesg' to find out why.

Line 224 invokes the “setup” command, but there’s no trace of a “setup” command in the /usr/lib/virtualbox directory nor elsewhere (at least not in PATH).

Any hints?

Thank you in advance
Cris

Forgot to say that I’m on Tumbleweed VERSION=“20190411”

Hi
A known issue… See http://forums.opensuse.org/showthread.php?t=535576 and https://lists.opensuse.org/opensuse-factory/2019-04/msg00196.html

Hi malcolmlewis!
Thank you for your suggestions. I had already scoured through the proposed threads before initiating my own thread. Unfortunately, unless I’m completely missing something, those thread do not discuss the problem I’m having. Besides, they point out problem with previous Tumbleweed releases, not the one I’m on.
If OTOH your point is simply that I should wait for a later update that will fix things, then I’m ok with that.

Cris

BTW, I was able to fix the problem with the same approach I had used with one of the previous problematic Tumbleweed snapshots: I just ran “sudo vboxconfig”.
Thank you
Cris

Hi
Yes, sometimes it may take a couple of snapshot releases before things are fixed since it’s a third party application, virtualbox not working won’t stop a snapshot release.