LinuxQuestions.org
Welcome to the most active Linux Forum on the web.
Home Forums Tutorials Articles Register
Go Back   LinuxQuestions.org > Forums > Linux Forums > Linux - Distributions > Slackware
User Name
Password
Slackware This Forum is for the discussion of Slackware Linux.

Notices


Reply
  Search this Thread
Old 12-23-2020, 03:09 PM   #1
slack-uke
Member
 
Registered: Nov 2013
Location: Toronto, Ontario, Canada
Distribution: Slackware 15.0 64-bit & Current 64-bit
Posts: 85

Rep: Reputation: 88
libnm.so.0.1.0 & VirtualBox TestBuild issue in Slackware64 Current


Did anybody else encounter this oddity?

I was up to date in Slackware64-Current as of Tue Dec 22 20:45:03 UTC 2020 & running 5.10.2 kernel

I did a clean install of VirtualBox testbuild VirtualBox 6.1.17 r141968 installer, built 2020-12-18T22:03:34Z.

In Plasma 5 I started VirtualBox and and it crashed giving the error:

Dec 23 09:05:01 kyiv kernel: [ 1597.888653] UINetworkReplyP[5487]: segfault at 10 ip 00007f591050a0c2 sp 00007f58ea5879a0 error 4 in libnm.so.0.1.0[7f59104d1000+a2000]
Dec 23 09:05:01 kyiv kernel: [ 1597.888666] 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

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.
 
Old 12-24-2020, 05:13 AM   #2
burdi01
Member
 
Registered: Dec 2010
Location: The Netherlands
Distribution: Slackware Current64, PartedMagic, Xubuntu
Posts: 465

Rep: Reputation: 114Reputation: 114
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 ...
 
1 members found this post helpful.
Old 12-24-2020, 06:31 AM   #3
chrisretusn
Senior Member
 
Registered: Dec 2005
Location: Philippines
Distribution: Slackware64-current
Posts: 2,976

Rep: Reputation: 1552Reputation: 1552Reputation: 1552Reputation: 1552Reputation: 1552Reputation: 1552Reputation: 1552Reputation: 1552Reputation: 1552Reputation: 1552Reputation: 1552
Updated to Wed Dec 23 21:21:34 UTC 2020

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 View Post
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.
 
4 members found this post helpful.
Old 12-24-2020, 06:55 AM   #4
slack-uke
Member
 
Registered: Nov 2013
Location: Toronto, Ontario, Canada
Distribution: Slackware 15.0 64-bit & Current 64-bit
Posts: 85

Original Poster
Rep: Reputation: 88
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.
 
Old 12-29-2020, 10:10 AM   #5
slack-uke
Member
 
Registered: Nov 2013
Location: Toronto, Ontario, Canada
Distribution: Slackware 15.0 64-bit & Current 64-bit
Posts: 85

Original Poster
Rep: Reputation: 88
I did an strace and got

bash-5.1$ strace -o out.log virtualbox
(process:8639): GLib-GObject-WARNING **: 12:45:10.571: cannot register existing type 'NMAgentManagerError'
(process:8639): GLib-CRITICAL **: 12:45:10.571: g_once_init_leave: assertion 'result != 0' failed
(process:8639): GLib-GObject-WARNING **: 12:45:10.571: cannot retrieve class for invalid (unclassed) type '<invalid>'
Segmentation fault

Googled this and saw somebody else encountered this before:

https://www.linuxquestions.org/quest...lt-4175657749/

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.

My Bad.

I considered this resolved.
 
Old 01-14-2021, 07:54 AM   #6
linuxxer
Member
 
Registered: Apr 2011
Location: I have my own planet
Distribution: Slackware®
Posts: 257

Rep: Reputation: Disabled
Quote:
Originally Posted by slack-uke View Post
Did anybody else encounter this oddity?
Yesterday I also face the same problem. I removed NetworkManager. And VirtualBox-6.1.16 is started running. This works for me.
 
  


Reply



Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is Off
HTML code is Off



Similar Threads
Thread Thread Starter Forum Replies Last Post
Brightness function keys not working on Slackware64 & Slackware64 current Andersen Slackware 7 01-15-2018 04:27 AM
[SOLVED] ARM Current - perl: error while loading shared libraries: libnm.so.0 kazzan Slackware - ARM 1 09-21-2015 02:10 AM
[SOLVED] someone must know where libnm-gtk.so.0 is! Pedroski Fedora 3 10-05-2011 08:18 PM
Ph&#7909;c h&#7891;i d&#7919; li&#7879;u b&#7883; m&#7845;t???, c&#7913; pollsite General 1 06-27-2005 12:39 PM
Gotta love those &#1649;&#1649;&#1649;&#1649;&#1649;&#1649;&#1649;&# iLLuSionZ Linux - General 5 11-18-2003 07:14 AM

LinuxQuestions.org > Forums > Linux Forums > Linux - Distributions > Slackware

All times are GMT -5. The time now is 03:56 PM.

Main Menu
Advertisement
My LQ
Write for LQ
LinuxQuestions.org is looking for people interested in writing Editorials, Articles, Reviews, and more. If you'd like to contribute content, let us know.
Main Menu
Syndicate
RSS1  Latest Threads
RSS1  LQ News
Twitter: @linuxquestions
Open Source Consulting | Domain Registration