[SOLVED] libnm.so.0.1.0 & VirtualBox TestBuild issue in Slackware64 Current
SlackwareThis Forum is for the discussion of Slackware Linux.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
Funny thing is that rc.networkmanager was not enabled but gather something in either Plasma 5 or VirtualBox tried to access it.
Just in case there was corruption with the NetworkManager-1.28.0-x86_64-1 package, I downloaded it again and re-installed it. Same thing happened. I started rc.networkmanager, same thing.
Doing a "slackpkg remove NetworkManager-1.28.0-x86_64-1" allowed me to run VirtualBox with no issues.
What is it about libnm.so library that caused the issue? In essence it is just a wrapper for handling D-Bus.
So is it a VirtualBox issue or a Slackware64-Current issue?
A colleague of mine was running Slackware64-Current with the same VirtualBox testbuild & 5.10.2 kernel but with the NetworkManager-1.26.4-x86_64-1 package with no issues.
Yes, I encountered that segfault too -- when I was testing once more for https://www.virtualbox.org/ticket/20021 and https://www.virtualbox.org/ticket/20084
I resolved the problem but I do not remember how -- it was very late yesterday evening. Was it reinstalling the 141968 testbuild or installing 141967 development snapshot? Or was it installing the extension?
Sorry ...
I upgraded to VirtualBox-6.1.17-141968 from VirtualBox-6.1.16-140961
I am not encountering this. Launching VirtualBox from Plasma5 is normal.
Quote:
Originally Posted by slack-uke
Funny thing is that rc.networkmanager was not enabled but gather something in either Plasma 5 or VirtualBox tried to access it.
Just in case there was corruption with the NetworkManager-1.28.0-x86_64-1 package, I downloaded it again and re-installed it. Same thing happened. I started rc.networkmanager, same thing.
Doing a "slackpkg remove NetworkManager-1.28.0-x86_64-1" allowed me to run VirtualBox with no issues.
What is it about libnm.so library that caused the issue? In essence it is just a wrapper for handling D-Bus.
So is it a VirtualBox issue or a Slackware64-Current issue?
A colleague of mine was running Slackware64-Current with the same VirtualBox testbuild & 5.10.2 kernel but with the NetworkManager-1.26.4-x86_64-1 package with no issues.
I have rc.networkmanager enabled. In the spirit of testing, I disabled rc.networkmanager and reboot, VirtualBox still starts with no errors.
Distribution: Slackware 15.0 64-bit & Current 64-bit
Posts: 85
Original Poster
Rep:
I had compiled a 5.4.85 kernel as a backup kernel for booting.
I re-installed NetworkManager-1.28.0-x86_64-1 and booted into 5.4.85 kernel. Started up Plasma 5 and tried starting VirtualBox testbuild VirtualBox 6.1.17 r141968 installer, built 2020-12-18T22:03:34Z.
It crashed with the 5.4.85 kernel & Slackware64-Current patched to & including the Tue Dec 22 20:45:03 UTC 2020 patches
This was the message in /var/log/messages
Dec 24 07:27:27 kyiv vboxdrv.sh: Starting VirtualBox services.
Dec 24 07:27:27 kyiv vboxdrv.sh: Building VirtualBox kernel modules.
Dec 24 07:28:04 kyiv vboxdrv.sh: VirtualBox kernel modules built.
Dec 24 07:28:04 kyiv kernel: [ 165.320461] vboxdrv: TSC mode is Invariant, tentative frequency 3693043667 Hz
Dec 24 07:28:04 kyiv vboxdrv.sh: VirtualBox services started.
Dec 24 07:28:04 kyiv ntpdate[5651]: ntpdate 4.2.8p15@1.3728-o Sun Nov 8 22:06:46 UTC 2020 (1)
Dec 24 07:28:25 kyiv ntpdate[5651]: step time server 132.246.11.227 offset +13.722826 sec
Dec 24 07:28:36 kyiv elogind-daemon[1382]: New session 1 of user gwk.
Dec 24 07:28:40 kyiv acpid: client connected from 5702[0:100]
Dec 24 07:28:40 kyiv acpid: 1 client rule loaded
Dec 24 07:28:47 kyiv dbus-daemon[5723]: [session uid=1002 pid=5721] Activating service name='org.kde.KSplash' requested by ':1.0' (uid=1002 pid=5719 comm="startplasma-x11 ")
Dec 24 07:28:50 kyiv dbus-daemon[5723]: [session uid=1002 pid=5721] Successfully activated service 'org.kde.KSplash'
Dec 24 07:29:07 kyiv dbus-daemon[5723]: [session uid=1002 pid=5721] Activating service name='org.kde.kglobalaccel' requested by ':1.6' (uid=1002 pid=5773 comm="/usr/bin/kded5 ")
Dec 24 07:29:07 kyiv dbus-daemon[5723]: [session uid=1002 pid=5721] Successfully activated service 'org.kde.kglobalaccel'
Dec 24 07:29:07 kyiv dbus-daemon[1367]: [system] Activating service name='org.freedesktop.UDisks2' requested by ':1.7' (uid=1002 pid=5773 comm="/usr/bin/kded5 ") (using servicehelper)
Dec 24 07:29:07 kyiv dbus-daemon[5723]: [session uid=1002 pid=5721] Activating service name='org.kde.ActivityManager' requested by ':1.8' (uid=1002 pid=5777 comm="/usr/bin/kwin_x11 ")
Dec 24 07:29:08 kyiv dbus-daemon[5723]: [session uid=1002 pid=5721] Successfully activated service 'org.kde.ActivityManager'
Dec 24 07:29:08 kyiv dbus-daemon[1367]: [system] Activating service name='org.freedesktop.PolicyKit1' requested by ':1.8' (uid=0 pid=5785 comm="/usr/libexec/udisks2/udisksd ") (using servicehelper)
Dec 24 07:29:09 kyiv polkitd[5804]: Started polkitd version 0.118
Dec 24 07:29:11 kyiv dbus-daemon[5723]: [session uid=1002 pid=5721] Activating service name='ca.desrt.dconf' requested by ':1.18' (uid=1002 pid=5833 comm="/usr/bin/gsettings set org.gnome.desktop.a11y.appl")
Dec 24 07:29:11 kyiv dbus-daemon[5723]: [session uid=1002 pid=5721] Successfully activated service 'ca.desrt.dconf'
Dec 24 07:29:13 kyiv dbus-daemon[5723]: [session uid=1002 pid=5721] Activating service name='org.freedesktop.Notifications' requested by ':1.16' (uid=1002 pid=5826 comm="/usr/lib64/kdeconnectd ")
Dec 24 07:29:16 kyiv dbus-daemon[1367]: [system] Successfully activated service 'org.freedesktop.PolicyKit1'
Dec 24 07:29:20 kyiv dbus-daemon[1367]: [system] Activating service name='org.freedesktop.UPower' requested by ':1.25' (uid=1002 pid=5894 comm="/usr/lib64/org_kde_powerdevil ") (using servicehelper)
Dec 24 07:29:20 kyiv dbus-daemon[1367]: [system] Successfully activated service 'org.freedesktop.UDisks2'
Dec 24 07:29:22 kyiv dbus-daemon[1367]: [system] Successfully activated service 'org.freedesktop.UPower'
Dec 24 07:29:22 kyiv dbus-daemon[1367]: [system] Activating service name='org.kde.powerdevil.discretegpuhelper' requested by ':1.25' (uid=1002 pid=5894 comm="/usr/lib64/org_kde_powerdevil ") (using servicehelper)
Dec 24 07:29:23 kyiv dbus-daemon[1367]: [system] Successfully activated service 'org.kde.powerdevil.discretegpuhelper'
Dec 24 07:29:23 kyiv dbus-daemon[1367]: [system] Activating service name='org.kde.powerdevil.chargethresholdhelper' requested by ':1.25' (uid=1002 pid=5894 comm="/usr/lib64/org_kde_powerdevil ") (using servicehelper)
Dec 24 07:29:23 kyiv dbus-daemon[1367]: [system] Successfully activated service 'org.kde.powerdevil.chargethresholdhelper'
Dec 24 07:29:23 kyiv dbus-daemon[1367]: [system] Activating service name='org.kde.powerdevil.backlighthelper' requested by ':1.25' (uid=1002 pid=5894 comm="/usr/lib64/org_kde_powerdevil ") (using servicehelper)
Dec 24 07:29:23 kyiv dbus-daemon[1367]: [system] Successfully activated service 'org.kde.powerdevil.backlighthelper'
Dec 24 07:29:24 kyiv NetworkManager[1397]: <info> [1608812964.0607] agent-manager: agent[9f5392de315cf5b3,:1.7/org.kde.plasma.networkmanagement/1002]: agent registered
Dec 24 07:29:24 kyiv dbus-daemon[5723]: [session uid=1002 pid=5721] Activating service name='org.kde.KScreen' requested by ':1.20' (uid=1002 pid=5894 comm="/usr/lib64/org_kde_powerdevil ")
Dec 24 07:29:24 kyiv dbus-daemon[5723]: [session uid=1002 pid=5721] Successfully activated service 'org.kde.KScreen'
Dec 24 07:29:30 kyiv dbus-daemon[1367]: [system] Activating service name='org.kde.kded.smart' requested by ':1.7' (uid=1002 pid=5773 comm="/usr/bin/kded5 ") (using servicehelper)
Dec 24 07:29:30 kyiv dbus-daemon[1367]: [system] Successfully activated service 'org.kde.kded.smart'
Dec 24 07:29:31 kyiv dbus-daemon[5723]: [session uid=1002 pid=5721] Activating service name='org.bluez.obex' requested by ':1.6' (uid=1002 pid=5773 comm="/usr/bin/kded5 ")
Dec 24 07:29:31 kyiv dbus-daemon[5723]: [session uid=1002 pid=5721] Activating service name='org.kde.KSplash' requested by ':1.2' (uid=1002 pid=5733 comm="/usr/bin/plasma_session ")
Dec 24 07:29:31 kyiv obexd[6121]: OBEX daemon 5.55
Dec 24 07:29:31 kyiv dbus-daemon[5723]: [session uid=1002 pid=5721] Successfully activated service 'org.bluez.obex'
Dec 24 07:29:49 kyiv dbus-daemon[5723]: [session uid=1002 pid=5721] Successfully activated service 'org.freedesktop.Notifications'
Dec 24 07:30:20 kyiv kernel: [ 288.025321] UINetworkReplyP[6458]: segfault at 10 ip 00007fc25408b0c2 sp 00007fc20a3159a0 error 4 in libnm.so.0.1.0[7fc254052000+a2000]
Dec 24 07:30:20 kyiv kernel: [ 288.025327] Code: ff ff e9 54 ff ff ff 90 41 57 41 56 49 89 f6 41 55 41 89 fd 48 89 d7 41 54 55 53 48 81 ec d8 00 00 00 e8 31 b3 fc ff 49 89 c7 <8b> 40 10 85 c0 74 49 31 db 49 89 e4 66 90 89 d8 4c 89 f1 be c8 00
Dec 24 07:30:30 kyiv dbus-daemon[5723]: [session uid=1002 pid=5721] Activated service 'org.kde.KSplash' failed: Process org.kde.KSplash exited with status 1
Also I am running a Ryzen 5 system:
Motherboard:
Manufacturer: ASUSTeK COMPUTER INC.
Product Name: PRIME B450M-A
Version: Rev X.0x
CPU:
Socket Designation: AM4
Type: Central Processor
Family: Zen
Manufacturer: Advanced Micro Devices, Inc.
ID: 81 0F 81 00 FF FB 8B 17
Signature: Family 23, Model 24, Stepping 1
Version: AMD Ryzen 5 3400G with Radeon Vega Graphics
and 32 GB RAM
What appears to work as a "short term dirty" solution is removing the NetworkManager Package and running the 5.10.2 kernel.
Okay, it appears I installed the testbuild [ VirtualBox-6.1.17-141968-Linux_amd64.run ] instead of the development build [ VirtualBox-6.1.97-141967-Linux_amd64.run ] and replaced the extensionpack with the development version and sure enough everything works perfectly fine.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.