Slackwar64-current and VirtualBox 6.1.x, recurring errors w/NetworkManager, applet, libnma, etc...
by slvr32 from LinuxQuestions.org on (#5FQ2W)
Starting from a clean Slackware64-current (20210320) install, and then installing VirtualBox 6.1.18, the following seems to be a common path to a segfault that keeps VirtualBox from starting...
$ virtualbox
(process:27731): GLib-GObject-WARNING **: 23:21:10.670: cannot register existing type 'NMAgentManagerError'
(process:27731): GLib-CRITICAL **: 23:21:10.670: g_once_init_leave: assertion 'result != 0' failed
(process:27731): GLib-GObject-WARNING **: 23:21:10.670: cannot retrieve class for invalid (unclassed) type '<invalid>'
Segmentation fault
Uninstalling NetworkManager, network-manager-applet, and libnma... and then starting VirtualBox seems to (temporarily) solve the problem.
I happened to later install a newer VirtualBox testbuild, because I'm trying to resolve a different Win10 VM not booting/kernel mode trap issue on the VirtualBox linux hosts forum.
I rebooted my Slackware64-current system to tweak virtualization settings off/on in my Host BIOS, and I hibernated my system last night.
After resuming my system from hibernation, and starting VirtualBox a few times around the Win10 VM troubleshooting/logging, the VirtualBox/Glib error/segfault surfaced again, and kept me from starting VirtualBox again until I did another remove/reinstall of NetworkManager/network-manager-applet/libnma.
I"m not sure if the reboots or the hibernation are responsible from the VirtualBox/Glib segfault, and I don't know if the solution is to rebuild the NetworkManager/network-manager-applet/libnma stuff, but I'm bringing this up as a recurring issue.
FYI, the related VirtualBox threads...
https://forums.virtualbox.org/viewto...p?f=7&t=102257 (VBox/Glib segfault)
and
https://forums.virtualbox.org/viewto...p?f=7&t=102269 (Win10 VM not starting w/VBox 6.1.x, kernel 5.10.25, etc...)
$ virtualbox
(process:27731): GLib-GObject-WARNING **: 23:21:10.670: cannot register existing type 'NMAgentManagerError'
(process:27731): GLib-CRITICAL **: 23:21:10.670: g_once_init_leave: assertion 'result != 0' failed
(process:27731): GLib-GObject-WARNING **: 23:21:10.670: cannot retrieve class for invalid (unclassed) type '<invalid>'
Segmentation fault
Uninstalling NetworkManager, network-manager-applet, and libnma... and then starting VirtualBox seems to (temporarily) solve the problem.
I happened to later install a newer VirtualBox testbuild, because I'm trying to resolve a different Win10 VM not booting/kernel mode trap issue on the VirtualBox linux hosts forum.
I rebooted my Slackware64-current system to tweak virtualization settings off/on in my Host BIOS, and I hibernated my system last night.
After resuming my system from hibernation, and starting VirtualBox a few times around the Win10 VM troubleshooting/logging, the VirtualBox/Glib error/segfault surfaced again, and kept me from starting VirtualBox again until I did another remove/reinstall of NetworkManager/network-manager-applet/libnma.
I"m not sure if the reboots or the hibernation are responsible from the VirtualBox/Glib segfault, and I don't know if the solution is to rebuild the NetworkManager/network-manager-applet/libnma stuff, but I'm bringing this up as a recurring issue.
FYI, the related VirtualBox threads...
https://forums.virtualbox.org/viewto...p?f=7&t=102257 (VBox/Glib segfault)
and
https://forums.virtualbox.org/viewto...p?f=7&t=102269 (Win10 VM not starting w/VBox 6.1.x, kernel 5.10.25, etc...)