Well the oddest thing just happened... Rebooted and decided to try again, I didn't change anything and watched my ram usage closely. The compile got about half way then the ram useage spiked to 98%. I was fully excepting it to fail, but it continued and the ram usage dropped and the compile finished successfully. Not sure why or how but I am not complaining lol. Thanks for all your help.

Dunno if that helps but 3 packages were upgraded from the repo before installing virtualbox and acpica was one of them:
[*] acpica-20211217-x86_64-1_pprkut.txz pprkut[*] confuse-3.3-x86_64-1_pprkut.txz pprkut[*] libftdi1-1.5-x86_64-1_pprkut.txz pprkut

When installing virtualbox-kernel-6.1.32_5.15.16-x86_64-1_pprkut.txz, it searched into /lib/modules/5.15.16/ but that is not my running kernel.
Executing install script for virtualbox-kernel-6.1.32_5.15.16-x86_64-1_pprkut.txz.
depmod: WARNING: could not open modules.order at /lib/modules/5.15.16: No such file or directory
depmod: WARNING: could not open modules.builtin at /lib/modules/5.15.16: No such file or directory
Package virtualbox-kernel-6.1.32_5.15.16-x86_64-1_pprkut.txz installed.

Regardless, it is working.
I wonder if I'll have to reinstall when I'll upgrade the kernel?

Yeah I believe ppr:kut said on his blog he wasn't going to rebuild the virtualbox kernel module for every kernel upgrade so you will have to do that yourself. its easy enough, just do...

then upgrade the package.

4 members found this post helpful.

Nice
Just did it and it was flawless.

ctrlaltca - I implemented this same workaround for Slackware-Current almost a year ago. However, I would actually like to be able to check for VirtualBox updates from Slackware-Current. Have you ever come across an actual fix for this bug since posting this message in January of 2021?

A new test build-6.1.33-revision-149686,
with extension pack-6.1.33-149614
and
a new development snapshot-6.1.97-revision-149682,
with extension pack-6.1.97-149678,
have been posted at,
https://www.virtualbox.org/wiki/Testbuilds

1 members found this post helpful.

Busy, busy.
A new test build-6.1.33-revision-149712,
with extension pack-6.1.33-149712
has been posted at,
https://www.virtualbox.org/wiki/Testbuilds

1 members found this post helpful.

A new test build-6.1.33-revision-149753,
with extension pack-6.1.33-149753
and
a new development snapshot-6.1.97-revision-149795,
with extension pack-6.1.97-149786,
have been posted at,
https://www.virtualbox.org/wiki/Testbuilds

1 members found this post helpful.

This fixes the problem of disabling the update in Virtualbox so that it doesn't show the segmentation error?

Well, the auto-update check is disabled by default. But if you try the update-check from the UI it hits the same segfault.

I'm starting to think there is something in the wind......


A new test build-6.1.33-revision-149825,
with extension pack-6.1.33-149753
and
a new development snapshot-6.1.97-revision-149824,
with extension pack-6.1.97-149814,
have been posted at,
https://www.virtualbox.org/wiki/Testbuilds

Hi,

@mfoley and others.

I've had a look around today for the problem and the root cause fix for this NMAgentManagerError segfault when running vb especially under Slackware.

This seems about the most interesting take:

https://gitlab.freedesktop.org/Netwo...r/-/issues/693

Sadly there was no follow up.

Thomas Haller suggested in his posts, there, to do this:

(the output files are around 500MB on my liveslak instance).

It's interesting to do that before and after removing NetworkManager then
grepping for:

Removing NetworkManager made the problem go away.

After reinstalling NetworkManager, I was also able to make the problem go away if I removed the libproxy network_networkmanager.so plugin/module.
Certainly less drastic than removing the whole of NetworkManager.

The problem, I think, is definitely as Thomas Haller suggests, but I'm not at all conversant with glib and how it works.

The problem never manifested on Slackware-current for me under xfce (with no NetworkManager running), but using the very lovely liveslak under KDE, it happened consistently.
(Though I was able to get alpine linux running in vb under liveslack running in another vb under current (bare metal), which made me smile!). Liveslak rocks!

I use a repackaged vb extracted from the .run file.

It would be nice to get to the bottom of this issue.

For testing I used this:

under liveslak (liveslak lean with a few additions) then deliberately checked for updates.

===Rich

1 members found this post helpful.

A new test build-6.1.33-revision-149998,
with extension pack-6.1.33-149980
and
a new development snapshot-6.1.97-revision-150113
with extension pack-6.1.97-150112
have been posted at,
https://www.virtualbox.org/wiki/Testbuilds

Hello everyone. I'm running virtualbox thanks to the packages of ppr:kut. Now I'm wondering why my guest os cannot detect usb flash drives plugged on my host so i checked the vm settings and noticed that my usb controller is 1.1. Could this be the reason? Is this normal? I remember seeing 2.0 and even 3.0 options from my previous virtualbox encounters on other distros during vm setup.

Attached Thumbnails

 

1 members found this post helpful.

did you install the virtualbox extension pack? ppk:rut has a slackbuild for it on SBo master branch.

2 members found this post helpful.