Slackware This 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.
Are you new to LinuxQuestions.org? Visit the following links:
Site Howto |
Site FAQ |
Sitemap |
Register Now
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.
|
 |
|
01-19-2021, 04:47 PM
|
#1
|
LQ Veteran
Registered: Feb 2007
Distribution: Slackware64-current with KDE4Town.
Posts: 9,711
|
VirtualBox for Slackware Users
They have yet to update their web site, but the tarball for VirtualBox 6.1.18 is available from this
link, http://download.virtualbox.org/virtu...6.1.18.tar.bz2
|
|
|
01-19-2021, 10:28 PM
|
#2
|
Member
Registered: Aug 2012
Distribution: Slackware64 15.0 (started with 13.37). Testing -current in a spare partition.
Posts: 968
|
Quote:
Originally Posted by cwizardone
|
Thanks  It's working with kernel 5.10.8 (installed from .run file).
|
|
3 members found this post helpful.
|
01-20-2021, 08:06 AM
|
#3
|
LQ Veteran
Registered: Feb 2007
Distribution: Slackware64-current with KDE4Town.
Posts: 9,711
Original Poster
|
Quote:
Originally Posted by Paulo2
Thanks  It's working with kernel 5.10.8 (installed from .run file).
|
Thanks. Good to know.
They updated their web site overnight.
The change log, https://www.virtualbox.org/wiki/Changelog-6.1#v18
The download link, https://www.virtualbox.org/wiki/Downloads
Edit in: Well..... I downloaded the 6.1.18 .run file and installed it and have the exact same problems as outlined in these two posts, https://www.linuxquestions.org/quest...ml#post6205854 and https://www.linuxquestions.org/quest...ml#post6206107.
It will not run as root, but using the information in this post https://www.linuxquestions.org/quest...ml#post6206107, I was able, as root, to installed the extension pack and then run VirtualBox as user.
As root it seg faults as per this post, https://www.linuxquestions.org/quest...ml#post6205854
Last edited by cwizardone; 01-21-2021 at 12:23 PM.
Reason: Typo.
|
|
1 members found this post helpful.
|
01-20-2021, 09:08 AM
|
#4
|
Senior Member
Registered: Dec 2005
Location: Springfield, MO
Distribution: Slackware64-15.0
Posts: 2,934
|
VirtualBox-6.1.18-142142-Linux_amd64.run is causing the segmentation fault bug that other people have reported above. It happens to me as both root and user. Dropping back down to the testbuild version VirtualBox-6.1.97-141967-Linux_amd64.run works fine for me.
|
|
2 members found this post helpful.
|
01-20-2021, 10:26 AM
|
#5
|
Member
Registered: Nov 2003
Location: NY
Distribution: slackware
Posts: 501
Rep: 
|
Quote:
Originally Posted by cwizardone
After installing today's -current updates VirtualBox-6.1.17-141968-Linux_amd64.run, no longer runs.
It will install, but it won't run.
It has worked just fine with the 5.10.y series, until now, so I booted back to the 5.10.5 and had the same problem. I'm guessing that means it is not the kernel(?).
Trying to run VirtualBox as root returns the following error,
|
Due to issues with VirtualBox and the 5.10 kernel I had decided to stay with kernel 5.4 until VBox at least runs in a more predictable / stable manner
In regards to the errors posted by @cwizardone
Quote:
/opt/VirtualBox# VirtualBox
(process:13893): GLib-GObject-WARNING **: 15:12:50.993: cannot register existing type 'NMAgentManagerError'
(process:13893): GLib-CRITICAL **: 15:12:50.993: g_once_init_leave: assertion 'result != 0' failed
(process:13893): GLib-GObject-WARNING **: 15:12:50.993: cannot retrieve class for invalid (unclassed) type '<invalid>'
Segmentation fault
|
Has anyone receiving this error tried the resolution (post #2) from https://www.linuxquestions.org/quest...lt-4175657749/ ??
|
|
1 members found this post helpful.
|
01-20-2021, 10:34 AM
|
#6
|
Member
Registered: Aug 2012
Distribution: Slackware64 15.0 (started with 13.37). Testing -current in a spare partition.
Posts: 968
|
Running -current (kernel 5.10.9 and multilib glibc 2.32) and Virtual Box works ok as user, but indeed login as root and running it in a terminal,
vbox crashes with segmentation fault. There isn't any other message.
edit- I realized that my root account isn't in the vboxusers group.
But adding root to that group and running 'VirtualBox' in a terminal
gives exactly what bitfuzzy posted above https://www.linuxquestions.org/quest...ml#post6209920
Last edited by Paulo2; 01-20-2021 at 10:45 AM.
|
|
1 members found this post helpful.
|
01-20-2021, 10:53 AM
|
#7
|
Member
Registered: Nov 2003
Location: NY
Distribution: slackware
Posts: 501
Rep: 
|
There is something definitely amiss, and I'm not sure Kernel 5.10 is the problem
Slackware -Current64 - Kernel 5.4.84 - VirtualBox 6.1.16 r140961
As Root w/ root added to vboxusers group
Quote:
virtualbox
(process:2736): GLib-GObject-WARNING **: 11:46:44.532: cannot register existing type 'NMAgentManagerError'
(process:2736): GLib-CRITICAL **: 11:46:44.532: g_once_init_leave: assertion 'result != 0' failed
(process:2736): GLib-GObject-WARNING **: 11:46:44.532: cannot retrieve class for invalid (unclassed) type '<invalid>'
Segmentation fault
|
|
|
1 members found this post helpful.
|
01-20-2021, 11:41 AM
|
#8
|
Member
Registered: Aug 2012
Distribution: Slackware64 15.0 (started with 13.37). Testing -current in a spare partition.
Posts: 968
|
Quote:
Originally Posted by bitfuzzy
There is something definitely amiss, and I'm not sure Kernel 5.10 is the problem
Slackware -Current64 - Kernel 5.4.84 - VirtualBox 6.1.16 r140961
As Root w/ root added to vboxusers group
|
Root can run VBox and create a vm in Slackware 14.2, I'm just creating a FreeBSD vm (VBox is 6.0.24).
(and root isn't in the vboxusers group)
Could it be some VirtualBox or kernel policy against? Or some problem with permissions.
|
|
1 members found this post helpful.
|
01-20-2021, 11:54 AM
|
#9
|
Member
Registered: Nov 2003
Location: NY
Distribution: slackware
Posts: 501
Rep: 
|
Quote:
Originally Posted by Paulo2
Root can run VBox and create a vm in Slackware 14.2, I'm just creating a FreeBSD vm (VBox is 6.0.24).
(and root isn't in the vboxusers group)
Could it be some VirtualBox or kernel policy against? Or some problem with permissions.
|
No custom policies, and it's not a problem really as I don't run VirtualBox as root anyway.
I was curious to see if root would run it without any issues (it didn't)
Root was added to the group after the first attempt to run as root resulted in errors, to see if it made a difference (it didn't)
|
|
1 members found this post helpful.
|
01-21-2021, 12:17 PM
|
#10
|
LQ Veteran
Registered: Feb 2007
Distribution: Slackware64-current with KDE4Town.
Posts: 9,711
Original Poster
|
OK. The test builds page has been updated and this is what I've found so far:
Test build 6.1.x revision 142299 along with its companion extension pack, does NOT fix the problem, i.e., it won't run as root, but once the extension pack is installed, see the last line in post #5 above, it runs as user.
Development revision 142300 and Extension Pack development revision 142298
WILL run both as root and as user.
https://www.virtualbox.org/wiki/Testbuilds
Last edited by cwizardone; 01-21-2021 at 12:52 PM.
|
|
2 members found this post helpful.
|
01-21-2021, 12:42 PM
|
#11
|
Member
Registered: Aug 2012
Distribution: Slackware64 15.0 (started with 13.37). Testing -current in a spare partition.
Posts: 968
|
Quote:
Originally Posted by cwizardone
OK. The test builds page has been updated and this is what I've found so far:
Test build 6.1.x revision 142299 along with its companion extension pack, does NOT fix the problem, i.e., it won't run as root, but once the extension pack is installed, see the last line in post #5 above, it runs as user.
Development revision 142300 and Extension Pack development revision 142298
will run both as root and as user.
https://www.virtualbox.org/wiki/Testbuilds
|
It seems that the problem is with VBox then, no worries about kernel or anything else.
VBox 6.1.18 works ok as user. I have a Debian vm for home banking that I save the state and
resume sometimes a month and it is working ok.
|
|
1 members found this post helpful.
|
01-21-2021, 01:02 PM
|
#12
|
Senior Member
Registered: Dec 2005
Location: Springfield, MO
Distribution: Slackware64-15.0
Posts: 2,934
|
Quote:
Originally Posted by cwizardone
OK. The test builds page has been updated and this is what I've found so far:
Test build 6.1.x revision 142299 along with its companion extension pack, does NOT fix the problem, i.e., it won't run as root, but once the extension pack is installed, see the last line in post #5 above, it runs as user.
Development revision 142300 and Extension Pack development revision 142298
WILL run both as root and as user.
https://www.virtualbox.org/wiki/Testbuilds
|
This version works for me as both root and user. Thanks for the heads up cwizardone.
|
|
1 members found this post helpful.
|
01-21-2021, 03:04 PM
|
#13
|
Member
Registered: Nov 2013
Location: Toronto, Ontario, Canada
Distribution: Slackware 15.0 64-bit & Current 64-bit
Posts: 154
Rep: 
|
I also have been experiencing this.
I had been running VirtualBox-6.1.97-141967 on a AMD Ryzen 5 3400G with Radeon Vega Graphics with 32 GB RAM on Slackware64 Current fully updated including Updates of Wed Jan 20 03:08:10 UTC 2021 and 5.10.9 huge kernel. Everything was working fine.
I updated to VirtualBox-6.1.18-142142 and have been experiencing Seg Faults for VirtualBox.
Jan 21 12:48:52 kyiv kernel: UINetworkReplyP[2448]: segfault at 10 ip 00007fa0981370c2 sp 00007fa04fffc850 error 4 in libnm.so.0.1.0[7fa0980fe000+a2000]
Jan 21 12:48:52 kyiv kernel: 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
Jan 21 12:49:19 kyiv kernel: UINetworkReplyP[2527]: segfault at 10 ip 00007fc23c5710c2 sp 00007fc213d8a850 error 4 in libnm.so.0.1.0[7fc23c538000+a2000]
Jan 21 12:49:19 kyiv kernel: 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
Jan 21 12:50:06 kyiv kernel: fuse: init (API version 7.32)
Jan 21 12:49:28 kyiv kernel: UINetworkReplyP[3180]: segfault at 10 ip 00007fa15458b0c2 sp 00007fa136d88850 error 4 in libnm.so.0.1.0[7fa154552000+a2000]
Jan 21 12:49:28 kyiv kernel: 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
I gather this is a Oracle issue.
|
|
1 members found this post helpful.
|
01-21-2021, 04:25 PM
|
#14
|
Member
Registered: Nov 2013
Location: Toronto, Ontario, Canada
Distribution: Slackware 15.0 64-bit & Current 64-bit
Posts: 154
Rep: 
|
And yet it works with 6.1.18-142142 if I remove NetworkManager-1.28.0-x86_64-2.txz
I did this before in December and had the same affect. Recompiling NetworkManager & libproxy did not resolve the problem. It is something deeper down that is affecting this in one of the dependent libraries.
In the end I went to the Development Stream and everything worked with the standard NetworkManager package installed.
At that particular time I tried the Test Build Stream and got
bash-5.1$ strace -o out-1.log virtualbox
(process:2516): GLib-GObject-WARNING **: 10:26:34.792: cannot register existing type 'NMAgentManagerError'
(process:2516): GLib-CRITICAL **: 10:26:34.792: g_once_init_leave: assertion 'result != 0' failed
(process:2516): GLib-GObject-WARNING **: 10:26:34.792: cannot retrieve class for invalid (unclassed) type '<invalid>'
Segmentation fault
but found I could go to the Development stream of VirtualBox and it worked and with the NetworkManager package installed.
There is something that the Testbuilds & 6.1.17 & 6.1.18 does not work well with the Slackware64 Current NetworkManager and/or one of it's dependencies.
Quote:
Originally Posted by slack-uke
I also have been experiencing this.
I had been running VirtualBox-6.1.97-141967 on a AMD Ryzen 5 3400G with Radeon Vega Graphics with 32 GB RAM on Slackware64 Current fully updated including Updates of Wed Jan 20 03:08:10 UTC 2021 and 5.10.9 huge kernel. Everything was working fine.
I updated to VirtualBox-6.1.18-142142 and have been experiencing Seg Faults for VirtualBox.
Jan 21 12:48:52 kyiv kernel: UINetworkReplyP[2448]: segfault at 10 ip 00007fa0981370c2 sp 00007fa04fffc850 error 4 in libnm.so.0.1.0[7fa0980fe000+a2000]
Jan 21 12:48:52 kyiv kernel: 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
Jan 21 12:49:19 kyiv kernel: UINetworkReplyP[2527]: segfault at 10 ip 00007fc23c5710c2 sp 00007fc213d8a850 error 4 in libnm.so.0.1.0[7fc23c538000+a2000]
Jan 21 12:49:19 kyiv kernel: 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
Jan 21 12:50:06 kyiv kernel: fuse: init (API version 7.32)
Jan 21 12:49:28 kyiv kernel: UINetworkReplyP[3180]: segfault at 10 ip 00007fa15458b0c2 sp 00007fa136d88850 error 4 in libnm.so.0.1.0[7fa154552000+a2000]
Jan 21 12:49:28 kyiv kernel: 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
I gather this is a Oracle issue.
|
|
|
1 members found this post helpful.
|
01-21-2021, 11:08 PM
|
#15
|
Senior Member
Registered: May 2004
Distribution: Slackware15.0 64-Bit Desktop, Debian 11 non-free Toshiba Satellite Notebook
Posts: 4,294
|
Quote:
Originally Posted by slack-uke
I also have been experiencing this.
I had been running VirtualBox-6.1.97-141967 on a AMD Ryzen 5 3400G with Radeon Vega Graphics with 32 GB RAM on Slackware64 Current fully updated including Updates of Wed Jan 20 03:08:10 UTC 2021 and 5.10.9 huge kernel. Everything was working fine.
I updated to VirtualBox-6.1.18-142142 and have been experiencing Seg Faults for VirtualBox.
Jan 21 12:48:52 kyiv kernel: UINetworkReplyP[2448]: segfault at 10 ip 00007fa0981370c2 sp 00007fa04fffc850 error 4 in libnm.so.0.1.0[7fa0980fe000+a2000]
Jan 21 12:48:52 kyiv kernel: 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
Jan 21 12:49:19 kyiv kernel: UINetworkReplyP[2527]: segfault at 10 ip 00007fc23c5710c2 sp 00007fc213d8a850 error 4 in libnm.so.0.1.0[7fc23c538000+a2000]
Jan 21 12:49:19 kyiv kernel: 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
Jan 21 12:50:06 kyiv kernel: fuse: init (API version 7.32)
Jan 21 12:49:28 kyiv kernel: UINetworkReplyP[3180]: segfault at 10 ip 00007fa15458b0c2 sp 00007fa136d88850 error 4 in libnm.so.0.1.0[7fa154552000+a2000]
Jan 21 12:49:28 kyiv kernel: 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
I gather this is a Oracle issue.
|
I am getting a similar error with VirtualBox 6.1.18 r142142 , however the kernel panic scrolls a few times so there all sorts of errors - so I could only get a screenshot - also after installing --Current - I was able to boot just fine, but the trouble started after installing the guest additions.
Last edited by Jeebizz; 01-21-2021 at 11:09 PM.
|
|
2 members found this post helpful.
|
All times are GMT -5. The time now is 06:13 AM.
|
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.
|
Latest Threads
LQ News
|
|