[SOLVED]VBox update from 5.2 to 5.2.2 fails

Questions about virtualization software
Forum rules
Before you post please read how to get help
Post Reply
rlwa32
Level 1
Level 1
Posts: 31
Joined: Thu Aug 03, 2017 8:06 am

[SOLVED]VBox update from 5.2 to 5.2.2 fails

Post by rlwa32 » Thu Nov 30, 2017 7:41 am

I had previously installed VBox in LM 18.1 and had configured the system to use the VBox repository. When the 5.2 version became available, mintupdate worked flawlessly and VBox was updated from 5.1.x to 5.2. When attempting to update from 5.2 to 5.2.2 the update process failed and there was an error message in the terminal display area that an unexpected end of file was received on dpkg.new.

It may be coincidental, but before attempting the VBox update I had run mintupdate which installed a new version of dpkg.

I have no idea how to proceed and am reluctant to attempt the update again since I don't want to lose the currently installed 5.2 version which, so far, appears unaffected by the update failure.

Any guidance here would be greatly appreciated.
Last edited by rlwa32 on Fri Dec 15, 2017 10:57 am, edited 1 time in total.

mr_raider
Level 6
Level 6
Posts: 1320
Joined: Sun Jun 20, 2010 9:50 am
Location: Montreal, QC

Re: VBox update from 5.2 to 5.2.2 fails

Post by mr_raider » Thu Nov 30, 2017 11:15 am

Open a terminal and run

Code: Select all

apt update
then

Code: Select all

apt upgrade
What is the output of the 2nd command?

Post it here.
Image

rlwa32
Level 1
Level 1
Posts: 31
Joined: Thu Aug 03, 2017 8:06 am

Re: VBox update from 5.2 to 5.2.2 fails

Post by rlwa32 » Thu Nov 30, 2017 11:40 am

mr_raider wrote:Open a terminal and run

Code: Select all

apt update
then

Code: Select all

apt upgrade
What is the output of the 2nd command?

Post it here.
The only available updates that is shown in my up-to-date mintupdate gui is the VBox update and an unchecked Linux firmware update.

However, after running apt update the following list of available upgrades is shown by apt --list upgradable. I thought it wise to post the list before doing all of these upgrades which, for whatever reason, have been ignored by mintupdate.
Listing...
dbus/xenial-updates 1.10.6-1ubuntu3.3 amd64 [upgradable from: 1.10.6-1ubuntu3.1]
dbus-x11/xenial-updates 1.10.6-1ubuntu3.3 amd64 [upgradable from: 1.10.6-1ubuntu3.1]
grub-common/xenial-updates 2.02~beta2-36ubuntu3.14 amd64 [upgradable from: 2.02~beta2-36ubuntu3.2]
grub-pc/xenial-updates 2.02~beta2-36ubuntu3.14 amd64 [upgradable from: 2.02~beta2-36ubuntu3.2]
grub-pc-bin/xenial-updates 2.02~beta2-36ubuntu3.14 amd64 [upgradable from: 2.02~beta2-36ubuntu3.2]
grub2-common/xenial-updates 2.02~beta2-36ubuntu3.14 amd64 [upgradable from: 2.02~beta2-36ubuntu3.2]
libdbus-1-3/xenial-updates 1.10.6-1ubuntu3.3 amd64 [upgradable from: 1.10.6-1ubuntu3.1]
libegl1-mesa/xenial-updates 17.0.7-0ubuntu0.16.04.2 amd64 [upgradable from: 11.2.0-1ubuntu2.2]
libegl1-mesa-drivers/xenial-updates 12.0.6-0ubuntu0.16.04.1 amd64 [upgradable from: 11.2.0-1ubuntu2.2]
libgbm1/xenial-updates 17.0.7-0ubuntu0.16.04.2 amd64 [upgradable from: 11.2.0-1ubuntu2.2]
libgl1-mesa-dri/xenial-updates 17.0.7-0ubuntu0.16.04.2 i386 [upgradable from: 11.2.0-1ubuntu2.2]
libgl1-mesa-glx/xenial-updates 17.0.7-0ubuntu0.16.04.2 amd64 [upgradable from: 11.2.0-1ubuntu2.2]
libglapi-mesa/xenial-updates 17.0.7-0ubuntu0.16.04.2 i386 [upgradable from: 11.2.0-1ubuntu2.2]
libgles1-mesa/xenial-updates,xenial-updates 17.0.7-0ubuntu0.16.04.2 amd64 [upgradable from: 11.2.0-1ubuntu2.2]
libgles2-mesa/xenial-updates 17.0.7-0ubuntu0.16.04.2 amd64 [upgradable from: 11.2.0-1ubuntu2.2]
libpam-systemd/xenial-updates 229-4ubuntu21 amd64 [upgradable from: 229-4ubuntu12]
libsystemd0/xenial-updates 229-4ubuntu21 amd64 [upgradable from: 229-4ubuntu12]
libudev1/xenial-updates 229-4ubuntu21 amd64 [upgradable from: 229-4ubuntu12]
libwayland-egl1-mesa/xenial-updates 17.0.7-0ubuntu0.16.04.2 amd64 [upgradable from: 11.2.0-1ubuntu2.2]
libxatracker2/xenial-updates 17.0.7-0ubuntu0.16.04.2 amd64 [upgradable from: 11.2.0-1ubuntu2.2]
linux-firmware/xenial-updates,xenial-updates,xenial-security,xenial-security 1.157.13 all [upgradable from: 1.157.5]
systemd/xenial-updates 229-4ubuntu21 amd64 [upgradable from: 229-4ubuntu12]
systemd-sysv/xenial-updates 229-4ubuntu21 amd64 [upgradable from: 229-4ubuntu12]
udev/xenial-updates 229-4ubuntu21 amd64 [upgradable from: 229-4ubuntu12]
virtualbox-5.2/unknown 5.2.2-119230~Ubuntu~xenial amd64 [upgradable from: 5.2.0-118431~Ubuntu~xenial]
xserver-xorg-video-amdgpu/xenial-updates 1.1.2-0ubuntu0.16.04.1 amd64 [upgradable from: 1.1.0-1]

mr_raider
Level 6
Level 6
Posts: 1320
Joined: Sun Jun 20, 2010 9:50 am
Location: Montreal, QC

Re: VBox update from 5.2 to 5.2.2 fails

Post by mr_raider » Thu Nov 30, 2017 7:04 pm

The mesa update is holding back the virtualbox update. 5.2.2 depends on the libgl1-mesa-glx package. You need to process the level 4 updates or you will have issues for vbox and any other program that depends on mesa, like most games and wine.

You need to run

Code: Select all

sudo apt full-upgrade
Image

rlwa32
Level 1
Level 1
Posts: 31
Joined: Thu Aug 03, 2017 8:06 am

Re: VBox update from 5.2 to 5.2.2 fails

Post by rlwa32 » Sat Dec 02, 2017 5:25 pm

mr_raider wrote:The mesa update is holding back the virtualbox update. 5.2.2 depends on the libgl1-mesa-glx package. You need to process the level 4 updates or you will have issues for vbox and any other program that depends on mesa, like most games and wine.

You need to run

Code: Select all

sudo apt full-upgrade
Thank you for your feedback. After I tend to some matters that require a functioning system and get a full backup done I will circle back and let you know how the upgrade went.

rlwa32
Level 1
Level 1
Posts: 31
Joined: Thu Aug 03, 2017 8:06 am

Re: VBox update from 5.2 to 5.2.2 fails

Post by rlwa32 » Fri Dec 15, 2017 10:56 am

Well, I finally got back to updating VBox and the solution turned out to be unrelated to package upgrades. To make a long story short I eventually managed to track down some atypical system issues to a memory upgrade where it seems the DIMMs were defective. I re-installed the original DIMMS and then re-installed any packages that had been updated while the defective memory was present. The VBox update from 5.2 to 5.2.2 then proceeded smoothly.

Post Reply

Return to “Virtualization”