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.
Distribution: Slackware64 15.0 (started with 13.37). Testing -current in a spare partition.
Posts: 934
Rep:
Quote:
Originally Posted by Paulo2
VBox 6.1.32 running OK in Slackware 15.0
Well, this is embarrassing. VBox 6.1.32 does run OK in my -current install.
But in a fresh install, VBox gives a segmentation fault started from terminal in two different machines.
Also 6.1.30 gives the same error.
Code:
bash-5.1$ VirtualBox
(process:1703): GLib-GObject-WARNING **: 10:59:54.973: cannot register existing type 'NMAgentManagerError'
(process:1703): GLib-CRITICAL **: 10:59:54.973: g_once_init_leave: assertion 'result != 0' failed
(process:1703): GLib-GObject-WARNING **: 10:59:54.973: cannot retrieve class for invalid (unclassed) type '<invalid>'
Segmentation fault
bash-5.1$
Is this related with multilib?
Both machines with fresh install don't have multilib installed.
My -current install has multilib installed.
Well, this is embarrassing. VBox 6.1.32 does run OK in my -current install.
But in a fresh install, VBox gives a segmentation fault started from terminal in two different machines.
Also 6.1.30 gives the same error.
Code:
bash-5.1$ VirtualBox
(process:1703): GLib-GObject-WARNING **: 10:59:54.973: cannot register existing type 'NMAgentManagerError'
(process:1703): GLib-CRITICAL **: 10:59:54.973: g_once_init_leave: assertion 'result != 0' failed
(process:1703): GLib-GObject-WARNING **: 10:59:54.973: cannot retrieve class for invalid (unclassed) type '<invalid>'
Segmentation fault
bash-5.1$
Is this related with multilib?
Both machines with fresh install don't have multilib installed.
My -current install has multilib installed.
Ahahaha, I'm getting screwed too
Code:
VBoxManage setextradata global GUI/UpdateDate never
Distribution: Slackware64-current with "True Multilib" and KDE4Town.
Posts: 9,154
Original Poster
Rep:
A new test build-6.1.33-revision-149396,
with extension pack-6.1.33-149396
and
a new development snapshot-6.1.97-revision-149426,
with extension pack-6.1.97-149425,
have been posted at, https://www.virtualbox.org/wiki/Testbuilds
Just to add my observations on my Slackware64-current main system with all patches and updates applied:
VirtualBox 6.1.32 works just find in Fluxbox sessions, but reproducibly crashes in KDE Plasma 5 full Wayland sessions. I have yet to try it with X11 or 'non-full' Wayland. Once crashed it cannot be restarted, even after manually killing all VirtualBox processes. Neither selecting it from the applications menu nor trying to start it using KRun (or is it KRunner?), nor entering "virtualbox" at the prompt in a Konsole windows wouldn't start it.
Maybe that helps to track the issue back to its root cause...
I published packages for virtualbox (OSE) in my package repo for -current. They are very close to the packages the SlackBuilds from SBo would create (since I maintain them there too), so should come with no surprises if you use them already. I explained a bit more about them here: https://www.liwjatan.org/blog/2022/01/virtualbox/
Hmm, after applying today's updates, VirtualBox seems to start and run just fine again in KDE Plasma 5 "full Wayland".
Although I don't know, which of the updates fixed the issue --- I don't see anything obviously related in the Changelog.
(Funfact: Now Libreoffice 7.2.5 from AlienBOB refuses to run with Fluxbox... The splashscreen pops up, and a LibO process is running after that, but no UI comes up. Not a big issue, as it works well in KDE Plasma 5, which is my preferred working environment anyway.)
I published packages for virtualbox (OSE) in my package repo for -current. They are very close to the packages the SlackBuilds from SBo would create (since I maintain them there too), so should come with no surprises if you use them already. I explained a bit more about them here: https://www.liwjatan.org/blog/2022/01/virtualbox/
I hope this is useful to some people, but I won't be offended if you stick to the .run installer
I have always used the .run installer, but I tried out your packages today and they were flawless. You obviously did a lot of work on these. Thanks for providing them!
I hope this is useful to some people, but I won't be offended if you stick to the .run installer
It just worked ( ͡° ͜ʖ ͡°)
installed slackpkg+
then added your repo to the list.
did an update/upgrade-all followed by installing your packages.
and voila, virtualbox is now working!
Your binaries are working great, but I tried compiling virtualbox from source using your SlackBuild today and ran into an error. This is basically a non-issue since your binaries work fine, but I just thought I would post the output to see if maybe you knew what the problem might be. If not no biggie.
Thanks.
The paste was too big for pastebin so I had to trim out some of the middle, I think I got the relevant info though. https://pastebin.com/9gNyeHeu
I compile the package with everything enabled that's possible, so some of the feature switches I still have on the SlackBuilds on SBo, I removed in mine.
In this case, it's the java bindings for the sdk you're stumbling over. I build the package with alienBOB's openjdk.
I compile the package with everything enabled that's possible, so some of the feature switches I still have on the SlackBuilds on SBo, I removed in mine.
In this case, it's the java bindings for the sdk you're stumbling over. I build the package with alienBOB's openjdk.
Yes, I forgot that I had openjre installed but not openjdk. That got me farther along in the build but then I ran into another error. Looking into this one now. It looks like it might be related to gsoap? I am double checking to make sure I got all the extra dependencies installed, vde2,gsoap,openjdk,
I install multilib glibc+gcc, openjdk, ant, gsoap and acpica to build the package. vde2 is just a runtime dependency, so that shouldn't be needed.
[EDIT] Quick google suggest an out-of-memory error. How much RAM are you working with? My build VMs get 16G so I kinda lose track what is needed exactly :-D
I install multilib glibc+gcc, openjdk, ant, gsoap and acpica to build the package. vde2 is just a runtime dependency, so that shouldn't be needed.
[EDIT] Quick google suggest an out-of-memory error. How much RAM are you working with? My build VMs get 16G so I kinda lose track what is needed exactly :-D
Yeah that could be the issue here. I decided to try compiling it in a clean environment so I booted up Alien Bob's Live Slackware64 with multilib, acpica, gsoap, and openjdk installed. I launched KDE System monitor and everything looked fine but then the compiling process completely ran away with all my RAM and froze the system for about 2 minutes then failed. This is odd since I am using a 5900x with 32gb of ram.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.
excuse me for posting that, probably it was discussed before but I missed it.
