Upgraded to 6.1.34, after this "Unable to locate imported symbol 'memset'"

[gusnan]

The updated packages are available in the repositories on https://download.virtualbox.org/virtualbox for about 4 hours now.

Great - the problem is fixed for me now. Thanks!

[Sagypt]

Hi,

the problem is fixed also for me.

Great support, thanks.

[klockren]

Hi,

does the source code package need to be patched as well?

I build a headless install from source, and the bug is still there.

Thanks

[birdie]

Hi,

does the source code package need to be patched as well?

I build a headless install from source, and the bug is still there.

Thanks

The answer is just a few posts earlier: viewtopic.php?f=7&t=105815#p516603

The updated packages are available in the repositories on https://download.virtualbox.org/virtualbox for about 4 hours now.

For 3rd party packagers: the patch which needs to be applied to resolve this memset issue (which is due to compilers becoming too smart lately) is https://www.virtualbox.org/changeset?re ... Config.kmk - the Debian/Ubuntu packager reported this applies with a little fuzz, but it works.

[AndyPagin]

The updated packages are available in the repositories on https://download.virtualbox.org/virtualbox for about 4 hours now.

The combination that worked for me:
https://download.virtualbox.org/virtual ... x86_64.rpm
https://download.virtualbox.org/virtual ... ox-extpack

[InvalidNickNamePickANew]

I also can't get 6.1.34 to work, after upgrading from 6.1.28. Dropping back to 6.1.3 as suggested and seems to be fine now.

6.1.34 breaks network VPN connection, graphics display, and both Ubuntu and Windows started freezing.

VirtualBox should release only stable versions once they're tested properly. It's always Russian roulette when upgrading