I just updated to 18.10 and believe I had my 2ndary hard drive crash... it was one on which I used to keep my VBox images. I think I removed any references to it from VirtualBox but on install of 5.2.22, I keep getting a segmentation fault in libc-2.28.so and systemd says it's freezing execution. The install appears to complete eventually but not sure why I am getting a seg fault or if it's stable. These are the install logs (what's on the screen during install):
kbarlow@atlantia:~/Downloads$ sudo dpkg -i virtualbox-5.2_5.2.22-126460_Ubuntu_bionic_amd64.deb
Selecting previously unselected package virtualbox-5.2.
(Reading database ... 388797 files and directories currently installed.)
Preparing to unpack virtualbox-5.2_5.2.22-126460_Ubuntu_bionic_amd64.deb ...
Unpacking virtualbox-5.2 (5.2.22-126460~Ubuntu~bionic) ...
Setting up virtualbox-5.2 (5.2.22-126460~Ubuntu~bionic) ...
addgroup: The group `vboxusers' already exists as a system group. Exiting.
Broadcast message from systemd-journald@atlantia (Wed 2018-12-05 21:03:33 EST):
systemd[1]: Caught <SEGV>, dumped core as pid 5094.
Broadcast message from systemd-journald@atlantia (Wed 2018-12-05 21:03:33 EST):
systemd[1]: Freezing execution.
Failed to enable unit: Failed to activate service 'org.freedesktop.systemd1': timed out (service_start_timeout=25000ms)
Failed to enable unit: Failed to activate service 'org.freedesktop.systemd1': timed out (service_start_timeout=25000ms)
Failed to enable unit: Failed to activate service 'org.freedesktop.systemd1': timed out (service_start_timeout=25000ms)
Failed to enable unit: Connection timed out
Failed to start vboxdrv.service: Failed to activate service 'org.freedesktop.systemd1': timed out (service_start_timeout=25000ms)
See system logs and 'systemctl status vboxdrv.service' for details.
Failed to start vboxballoonctrl-service.service: Connection timed out
See system logs and 'systemctl status vboxballoonctrl-service.service' for details.
Failed to start vboxautostart-service.service: Failed to activate service 'org.freedesktop.systemd1': timed out (service_start_timeout=25000ms)
See system logs and 'systemctl status vboxautostart-service.service' for details.
Failed to start vboxweb-service.service: Connection timed out
See system logs and 'systemctl status vboxweb-service.service' for details.
Processing triggers for systemd (239-7ubuntu10.4) ...
Failed to reload daemon: Failed to activate service 'org.freedesktop.systemd1': timed out (service_start_timeout=25000ms)
Processing triggers for ureadahead (0.100.0-20) ...
ureadahead will be reprofiled on next reboot
Processing triggers for gnome-menus (3.13.3-11ubuntu2) ...
Processing triggers for desktop-file-utils (0.23-3ubuntu3) ...
Processing triggers for mime-support (3.60ubuntu1) ...
Processing triggers for hicolor-icon-theme (0.17-2) ...
Processing triggers for shared-mime-info (1.10-1) ...
kbarlow@atlantia:~/Downloads$
kinghat@kinghat-kubuntu:/media/kinghat/Staging/New Files$ sudo ./VirtualBox-5.2.23-126798-Linux_amd64.run
[sudo] password for kinghat:
Verifying archive integrity... All good.
Uncompressing VirtualBox for Linux installation.............
VirtualBox Version 5.2.23 r126798 (2018-11-20T16:12:47Z) installer
Installing VirtualBox to /opt/VirtualBox
Python found: python, installing bindings...
Broadcast message from systemd-journald@kinghat-kubuntu (Thu 2018-12-06 16:33:50 CST):
systemd[1]: Caught <SEGV>, dumped core as pid 5201.
Broadcast message from systemd-journald@kinghat-kubuntu (Thu 2018-12-06 16:33:50 CST):
systemd[1]: Freezing execution.
Failed to enable unit: Failed to activate service 'org.freedesktop.systemd1': timed out (service_start_timeout=25000ms)
Failed to enable unit: Failed to activate service 'org.freedesktop.systemd1': timed out (service_start_timeout=25000ms)
Failed to enable unit: Failed to activate service 'org.freedesktop.systemd1': timed out (service_start_timeout=25000ms)
Failed to enable unit: Connection timed out
Failed to start vboxdrv.service: Failed to activate service 'org.freedesktop.systemd1': timed out (service_start_timeout=25000ms)
See system logs and 'systemctl status vboxdrv.service' for details.
Failed to start vboxballoonctrl-service.service: Connection timed out
See system logs and 'systemctl status vboxballoonctrl-service.service' for details.
Failed to start vboxautostart-service.service: Connection timed out
See system logs and 'systemctl status vboxautostart-service.service' for details.
Failed to start vboxweb-service.service: Connection timed out
See system logs and 'systemctl status vboxweb-service.service' for details.
VirtualBox has been installed successfully.
You will find useful information about using VirtualBox in the user manual
/opt/VirtualBox/UserManual.pdf
and in the user FAQ
[b]cant post this because of account age[/b]
We hope that you enjoy using VirtualBox.
i am also on kubuntu 18.10. i have always had a really slow install and maybe even errors on 18.10 but i dont think i recorded them. i also cant get the VMs i have to launch after a reboot and get these errors:
image.png (112.86 KiB) Viewed 2222 times
i end up having other system issues after i have run vbox and usually require a reboot.
here is a ubuntu bug report: bugs.launchpad . net/ubuntu/+source/virtualbox/+bug/1807286
Thanks... Is that a dev build? Where do you get those?
I downloaded from the downloads page and got 5.2.22-126460 which also appears to be the version available via APT. Trying to install via APT I get a dependency that cannot be met:
kbarlow@atlantia:~$ sudo apt-get install virtualbox-5.2
Reading package lists... Done
Building dependency tree
Reading state information... Done
Some packages could not be installed. This may mean that you have
requested an impossible situation or if you are using the unstable
distribution that some required packages have not yet been created
or been moved out of Incoming.
The following information may help to resolve the situation:
The following packages have unmet dependencies:
virtualbox-5.2 : Depends: libcurl3 (>= 7.16.2) but it is not installable
Depends: libvpx4 (>= 1.6.0) but it is not installable
E: Unable to correct problems, you have held broken packages.
kbarlow@atlantia:~$ sudo apt-get install libcurl3
Reading package lists... Done
Building dependency tree
Reading state information... Done
Package libcurl3 is not available, but is referred to by another package.
This may mean that the package is missing, has been obsoleted, or
is only available from another source
However the following packages replace it:
libcurl4:i386 libcurl4
E: Package 'libcurl3' has no installation candidate
Maybe that's why trying to install the deb file directly is seg faulting?
As far as using apt-get, did you make the VirtualBox repository available, as described in the Linux downloads page?
Do NOT send me Personal Messages (PMs) for troubleshooting, they are simply deleted.
Do NOT reply with the "QUOTE" button, please use the "POST REPLY", at the bottom of the form.
If you obfuscate any information requested, I will obfuscate my response. These are virtual UUIDs, not real ones.
Eh... I had the source in /etc/apt/sources.list but was pointed at artful instead of cosmic. That appeared to have solve the dependencies problem but not the SEGV. I tried the test build and that appeared to go in cleanly:
kbarlow@atlantia:~/Downloads$ sudo ./VirtualBox-5.2.23-127309-Linux_amd64.run
Verifying archive integrity... All good.
Uncompressing VirtualBox for Linux installation.............
VirtualBox Version 5.2.23 r127309 (2018-12-08T13:13:52Z) installer
Installing VirtualBox to /opt/VirtualBox
Python found: python, installing bindings...
VirtualBox has been installed successfully.
You will find useful information about using VirtualBox in the user manual
/opt/VirtualBox/UserManual.pdf
and in the user FAQ
http://www.virtualbox.org/wiki/User_FAQ
We hope that you enjoy using VirtualBox.
It fired up though I don't currently have a VM defined to run so I'll have to play with it later. So far looks good though.