libnm.so.0.1.0 & VirtualBox TestBuild issue in Slackware64 Current
by slack-uke from LinuxQuestions.org on (#5C12A)
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.
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.