Cannot uninstall virtualbox-ext-pack (version 5.1)

Hans

Member
Hi everyone,

I'm brand new to this forum, and very new to Linux itself. I mention that because up until now, I have been exclusively a GUI guy. I mean really exclusively. Therefore, for me to understand any helpful suggestions, it will have to be in the smallest baby-steps with no assumption that I know even the simple things like "run it from the root".

My problem is with fixing VirtualBox. I had version 5.1, and it worked pretty well until it stopped launching one day. I've looked online for suggestions, but I can't get past uninstalling the program. It tells me that I have one broken dependency, and to fix that first (virtualbox-ext-pack version 5.1.30-2). It gives me a message that is cut-off and the only thing I can view of it, tells me to get rid of any "third-party repositories" - but I don't know what a repository in Linux even is. Anyway, Synaptic Package Manager can't fix it, and I've tried several commands to purge everything with a Virtualbox label, but that one file keeps hanging on.

I downloaded Virtualbox 5.2 hoping maybe that might - I don't know - overwrite that bugger, but I don't understand how to install programs on Linux. I see the compressed download, but uncompressing it just leads me into a seeming infinite process of opening folders and looking for something that resembles an installer file. Basically, I get nowhere.

Any help would be appreciated : )
Thank you,
Hans
 


wizardfromoz

Super Moderator
Staff member
Gold Supporter
@Hans Hello and welcome to linux.org :)

I am just finding my way around Opera ... have not been there for a long long time ;)

I am not sure if friend @arochester is coming back to this, but did not want to keep you waiting too long.

We all work from different timezones and I am from Down Under, so make allowances, please.

I have installed Pearl so to better understand your circumstances. Interesting choice for a Newbie and I wonder how you found it, I had not made its acquaintance before, and I run 65 or so Linux, but I note that it has a look and feel of Mac OSX 'Snow Leopard' ... do you have a Mac background?

Anyway, I can't hang around much tonight, have to cook dinner, but this Distro is Ubuntu-based, on 17.10 Artful Aardvark, which I have, so it should not be rocket science how to advise you.

It may involve getting your hands dirty a little with Terminal (Ctrl-Alt-t). It may involve issuing a command eg

Code:
apt-get purge virtualbox
... not exact, so don't try it yet. But I will have a look-see tomorrow lunchtime or so my time. This command will rmeove not only Virtual Box but any dependencies which may include your problematic files/packages.

So I'll see you tomorrow, and if @arochester comes back with input in the meantime, by all means go with him, he knows a lot :D

Cheers

Wizard
 

JasKinasis

Well-Known Member
@Hans - I don't know about fixing the problem via the GUI. I'm not a particularly GUI-oriented person.

But if you open up a terminal, you can try this command:
Code:
sudo dpkg -f install
That will cause dpkg to attempt to automatically fix any dependency related issues.

If that works without futher errors, I'd recommend updating/upgrading the packages on your system. Either via synaptic, or via the terminal:
Code:
sudo apt update && sudo apt upgrade && sudo apt dist-upgrade
Once dpkg has fixed the problem and you have updated/upgraded the rest of the system,
you should be safe to remove virtualbox (or reinstall it from the Pearl repos) via the GUI using synaptic.

But if the initial dpkg command doesn't fix the problem, please make another post in this thread and include any error messages from dpkg. It would also be helpful if you can list the contents of the file:
/etc/apt/sources.list

And the content of any files in the following directory:
/etc/apt/sources.list.d/

Out of interest, how did you originally install virtualbox? Was it installed from the Pearl repos using synaptic? Or did you manually download and install it from elsewhere? (e.g. a standalone .deb package or installer from a 3rd party website or a PPA?).
 
Last edited:

Hans

Member
@Hans Hello and welcome to linux.org :)

I am just finding my way around Opera ... have not been there for a long long time ;)

I am not sure if friend @arochester is coming back to this, but did not want to keep you waiting too long.

We all work from different timezones and I am from Down Under, so make allowances, please.

I have installed Pearl so to better understand your circumstances. Interesting choice for a Newbie and I wonder how you found it, I had not made its acquaintance before, and I run 65 or so Linux, but I note that it has a look and feel of Mac OSX 'Snow Leopard' ... do you have a Mac background?

Anyway, I can't hang around much tonight, have to cook dinner, but this Distro is Ubuntu-based, on 17.10 Artful Aardvark, which I have, so it should not be rocket science how to advise you.

It may involve getting your hands dirty a little with Terminal (Ctrl-Alt-t). It may involve issuing a command eg

Code:
apt-get purge virtualbox
... not exact, so don't try it yet. But I will have a look-see tomorrow lunchtime or so my time. This command will rmeove not only Virtual Box but any dependencies which may include your problematic files/packages.

So I'll see you tomorrow, and if @arochester comes back with input in the meantime, by all means go with him, he knows a lot :D

Cheers

Wizard
@Hans Hello and welcome to linux.org :)

I am just finding my way around Opera ... have not been there for a long long time ;)

I am not sure if friend @arochester is coming back to this, but did not want to keep you waiting too long.

We all work from different timezones and I am from Down Under, so make allowances, please.

I have installed Pearl so to better understand your circumstances. Interesting choice for a Newbie and I wonder how you found it, I had not made its acquaintance before, and I run 65 or so Linux, but I note that it has a look and feel of Mac OSX 'Snow Leopard' ... do you have a Mac background?

Anyway, I can't hang around much tonight, have to cook dinner, but this Distro is Ubuntu-based, on 17.10 Artful Aardvark, which I have, so it should not be rocket science how to advise you.

It may involve getting your hands dirty a little with Terminal (Ctrl-Alt-t). It may involve issuing a command eg

Code:
apt-get purge virtualbox
... not exact, so don't try it yet. But I will have a look-see tomorrow lunchtime or so my time. This command will rmeove not only Virtual Box but any dependencies which may include your problematic files/packages.

So I'll see you tomorrow, and if @arochester comes back with input in the meantime, by all means go with him, he knows a lot :D

Cheers

Wizard
@Hans Hello and welcome to linux.org :)

I am just finding my way around Opera ... have not been there for a long long time ;)

I am not sure if friend @arochester is coming back to this, but did not want to keep you waiting too long.

We all work from different timezones and I am from Down Under, so make allowances, please.

I have installed Pearl so to better understand your circumstances. Interesting choice for a Newbie and I wonder how you found it, I had not made its acquaintance before, and I run 65 or so Linux, but I note that it has a look and feel of Mac OSX 'Snow Leopard' ... do you have a Mac background?

Anyway, I can't hang around much tonight, have to cook dinner, but this Distro is Ubuntu-based, on 17.10 Artful Aardvark, which I have, so it should not be rocket science how to advise you.

It may involve getting your hands dirty a little with Terminal (Ctrl-Alt-t). It may involve issuing a command eg

Code:
apt-get purge virtualbox
... not exact, so don't try it yet. But I will have a look-see tomorrow lunchtime or so my time. This command will rmeove not only Virtual Box but any dependencies which may include your problematic files/packages.

So I'll see you tomorrow, and if @arochester comes back with input in the meantime, by all means go with him, he knows a lot :D

Cheers

Wizard
Hello WizardFromOz, thanks so much for your response.

Thank you for installing Pearl to better understand my circumstances - that was kind of you. Regarding how I found Pearl, I was looking for a customizable OS (or, distro now), and read that Pearl (formerly Pear, which was to hint at being an alternative to Apple), was heavily customizable. I tried the version out at the time, but also tried Ubuntu (my 2nd favorite), Deepin, and Elementary OS. And, you were right - I have been a Mac user since 1996.

I felt that Apple, which I preffered over Microsoft, has changed too much, and in ways that have been veering away from why I elected to go with Mac instead of Windows. For me, those things include aesthetics, functionality, customizability, and intuitiveness. I have been happy to learn that Linux has alternatives to Mac and Windows OSs.

Thanks again for your reply, and I'll keep my eyes open for any suggestions you may have.

Hans
 

Hans

Member
@Hans - I don't know about fixing the problem via the GUI. I'm not a particularly GUI-oriented person.

But if you open up a terminal, you can try this command:
Code:
sudo dpkg -f install
That will cause dpkg to attempt to automatically fix any dependency related issues.

If that works without futher errors, I'd recommend updating/upgrading the packages on your system. Either via synaptic, or via the terminal:
Code:
sudo apt update && sudo apt upgrade && sudo apt dist-upgrade
Once dpkg has fixed the problem and you have updated/upgraded the rest of the system,
you should be safe to remove virtualbox (or reinstall it from the Pearl repos) via the GUI using synaptic.

But if the initial dpkg command doesn't fix the problem, please make another post in this thread and include any error messages from dpkg. It would also be helpful if you can list the contents of the file:
/etc/apt/sources.list

And the content of any files in the following directory:
/etc/apt/sources.list.d/

Out of interest, how did you originally install virtualbox? Was it installed from the Pearl repos using synaptic? Or did you manually download and install it from elsewhere? (e.g. a standalone .deb package or installer from a 3rd party website or a PPA?).
Thank you JasKinasis, I will try your suggestions : )

Hans
 

Hans

Member
@Hans - I don't know about fixing the problem via the GUI. I'm not a particularly GUI-oriented person.

But if you open up a terminal, you can try this command:
Code:
sudo dpkg -f install
That will cause dpkg to attempt to automatically fix any dependency related issues.

If that works without futher errors, I'd recommend updating/upgrading the packages on your system. Either via synaptic, or via the terminal:
Code:
sudo apt update && sudo apt upgrade && sudo apt dist-upgrade
Once dpkg has fixed the problem and you have updated/upgraded the rest of the system,
you should be safe to remove virtualbox (or reinstall it from the Pearl repos) via the GUI using synaptic.

But if the initial dpkg command doesn't fix the problem, please make another post in this thread and include any error messages from dpkg. It would also be helpful if you can list the contents of the file:
/etc/apt/sources.list

And the content of any files in the following directory:
/etc/apt/sources.list.d/

Out of interest, how did you originally install virtualbox? Was it installed from the Pearl repos using synaptic? Or did you manually download and install it from elsewhere? (e.g. a standalone .deb package or installer from a 3rd party website or a PPA?).
Hi JasKinasis,

Here are the results of the steps after I took them:

$ sudo dpkg -f install
dpkg-deb: error: failed to read archive 'install': No such file or directory

I got into the /etc/apt directory, did an ls, and it shows:

apt.conf.d sources.list.d trusted.gpg trusted.gpg.d
preferences.d sources.old trusted.gpg

But I don't see the "sources.list" file, just the "sources.list.d" file. Here is what's inside it:

appgrid-stable-artful.list rvm-smplayer-artful.list
official-package-repositories.list steam.list
opera-stable.list yannubuntu-boot-repair-artful.list


As for how I originally installed VirtualBox - I can't be sure. I know that at some point - maybe originally - I did uninstall and reinstall from Synaptic...

Thank you,
Hans
 

wizardfromoz

Super Moderator
Staff member
Gold Supporter
Hi Hans, just a holding Post until I can get pack to you (other commitments).

If you can give me 24 hours, I will have a whole lot more for you. I now have two of the Pearl, one standard-sized at 20 GiB and one for VBox at 60GiB.

There's good news and bad news, but more good than bad.

Also, you can totally uninstall the app by typing in at Terminal

Code:
sudo apt-get purge virtualbox
That will uninstall it along with all dependencies.

Reboot your computer following that, and in Synaptic you will find that the items are still there to be reinstalled, but they are not installed.

Another also is that with SPM (Synaptic) you can click File - History and drop the November or whatever arrow down and see what you have installed with Synaptic.

Cheers and back when I can

Wizard
 

wizardfromoz

Super Moderator
Staff member
Gold Supporter
Well, Hans, there is a lot to say, but I will try to keep it focused and brief.

First up, do you still have the installation file (.iso) of Pearl you downloaded? If so, is it called

PearlMATE-6.0-ALPHA-08-20-2017_amd64.iso

or

PearlMATE-6.0-10-19-17_amd64.iso ?

Scott Vandergrist is the developer of Pearl, and his site is a little confusing.

If you have downloaded the Alpha, then you will likely continue to encounter problems, as it is very developmental.

I have to switch Distros in order to get access to a better download mirror, but I will be back with more.

Wizard
 

wizardfromoz

Super Moderator
Staff member
Gold Supporter
Back again.

First, Jas (@JasKinasis) seldom makes mistakes, but one above is, that is for

Code:
sudo dpkg -f install
... and the error returned to you was appropriate.

The correct command is

Code:
sudo apt-get -f install
... and that should be issued immediately following dpkg having notified you of dependencies outstanding

eg

Code:
dpkg -i virtualbox-5.2_5.2.0-118431~Ubuntu~zesty_amd64.deb
... which is likely the file you downloaded, and when that is installed, if it tells you "these dependencies need installing", then you follow it immediately with

Code:
sudo apt-get -f install
... and Linux will resolve it.

HOWEVER, given you are a GUI man, I am guessing you double-clicked the downloaded .deb file, and then that action opened your Archive Manager (possibly Engrampa, I am not in that Distro at the moment) which invited you to extract?

That is why you are going around in circles trying to install 5.2.

In your Synaptic Package Manager, if you search for "gdebi" you will find one or more references. The check box to its left may be empty or contain an exclamation mark. If so, it is not installed, but may be upgradeable.

If it were installed, it would have a checkbox filled with a colour, or a checkmark (tick) in the box. In that event, when you doubleclicked the .deb file, GDebi would have opened and invited you to install.

But don't get ahead of me.

...- but I don't know what a repository in Linux even is....
When you are in Synaptic, you are viewing that Linux Distro's Repository (aka Repo) contents. Or in the case of Linux Mint, those of Mint AND Ubuntu.

Think of your Linux Distro as being your Business, and when you don't have something in stock that someone would like, you order it from the warehouse.

The stock in the warehouse meets a certain enforced standard, it is approved and certified. It has been tested, and it is considered stable. But it may not be the latest, cutting edge, version.

v5.2 of Virtualbox is not in the Repos yet, but version 5.1.30-2 is. Check at the bottom of your Synaptic window pane for mention of broken packages, if one or more is mentioned, go to Edit - Fix Broken Packages.

I have to sign off for tonight my time, but digest what I have said, and I'll be back to answer any questions I can.

Cheers all

Wizard
 
Last edited:

JasKinasis

Well-Known Member
Back again.

First, Jas (@JasKinasis) seldom makes mistakes, but one above is, that is for

Code:
sudo dpkg -f install
... and the error returned to you was appropriate.

The correct command is

Code:
sudo apt-get -f install
... and that should be issued immediately following dpkg having notified you of dependencies outstanding

eg

Code:
dpkg -i virtualbox-5.2_5.2.0-118431~Ubuntu~zesty_amd64.deb
... which is likely the file you downloaded, and when that is installed, if it tells you "these dependencies need installing", then you follow it immediately with

Code:
sudo apt-get -f install
... and Linux will resolve it.
Sorry all! And thanks for the correction Wiz! Once again, I was doing things from memory. I was at work (compiling!), so I posted during some compile time from my Windows PC at work. I didn't have my personal Linux laptop handy, otherwise I would have verified it before posting.....
I guess my memory isn't what it used to be..... Oops!
 
Last edited:

Hans

Member
Back again.

First, Jas (@JasKinasis) seldom makes mistakes, but one above is, that is for

Code:
sudo dpkg -f install
... and the error returned to you was appropriate.

The correct command is

Code:
sudo apt-get -f install
... and that should be issued immediately following dpkg having notified you of dependencies outstanding

eg

Code:
dpkg -i virtualbox-5.2_5.2.0-118431~Ubuntu~zesty_amd64.deb
... which is likely the file you downloaded, and when that is installed, if it tells you "these dependencies need installing", then you follow it immediately with

Code:
sudo apt-get -f install
... and Linux will resolve it.

HOWEVER, given you are a GUI man, I am guessing you double-clicked the downloaded .deb file, and then that action oped your Archive Manager (possibly Engrampa, I am not in that Distro at the moment) which invited you to extract?

That is why you are going around in circles trying to install 5.2.

In your Synaptic Package Manager, if you search for "gdebi" you will find one or more references. The check box to its left may be empty or contain an exclamation mark. If so, it is not installed, but may be upgradeable.

If it were installed, it would have a checkbox filled with a colour, or a checkmark (tick) in the box. In that event, when you doubleclicked the .deb file, GDebi would have opened and invited you to install.

But don't get ahead of me.



When you are in Synaptic, you are viewing that Linux Distro's Repository (aka Repo) contents. Or in the case of Linux Mint, those of Mint AND Ubuntu.

Think of your Linux Distro as being your Business, and when you don't have something in stock that someone would like, you order it from the warehouse.

The stock in the warehouse meets a certain enforced standard, it is approved and certified. It has been tested, and it is considered stable. But it may not be the latest, cutting edge, version.

v5.2 of Virtualbox is not in the Repos yet, but version 5.1.30-2 is. Check at the bottom of your Synaptic window pane for mention of broken packages, if one or more is mentioned, go to Edit - Fix Broken Packages.

I have to sign off for tonight my time, but digest what I have said, and I'll be back to answer any questions I can.

Cheers all

Wizard
Thank you Wizard! Using the sudo apt-get -f install command, it looks like virtualbox-ext-pack was finally released. I'm back to where it just doesn't launch, but hoping that may be an easy fix now that the vexing ext file has been released. Here is the outcome of the command:

~$ sudo apt-get -f install

Reading package lists... Done
Building dependency tree
Reading state information... Done
Correcting dependencies... Done
The following packages were automatically installed and are no longer required:
gir1.2-nm-1.0 gir1.2-nma-1.0 gir1.2-timezonemap-1.0 gir1.2-xkl-1.0 kbuild
ktexteditor-data ktexteditor-katepart libeditorconfig0 libgit2-24
libhttp-parser2.1 libkf5texteditor5 libkf5texteditor5-libjs-underscore
libkf5threadweaver5 libtimezonemap-data libtimezonemap1 module-assistant
unity-scopes-runner
Use 'sudo apt autoremove' to remove them.
The following additional packages will be installed:
virtualbox virtualbox-qt
Suggested packages:
vde2 virtualbox-guest-additions-iso
The following NEW packages will be installed:
virtualbox virtualbox-qt
0 upgraded, 2 newly installed, 0 to remove and 57 not upgraded.
1 not fully installed or removed.
Need to get 0 B/24.0 MB of archives.
After this operation, 102 MB of additional disk space will be used.
Do you want to continue? [Y/n] y
(Reading database ... 350607 files and directories currently installed.)
Preparing to unpack .../virtualbox_5.1.30-dfsg-1_amd64.deb ...
Unpacking virtualbox (5.1.30-dfsg-1) ...
Preparing to unpack .../virtualbox-qt_5.1.30-dfsg-1_amd64.deb ...
Unpacking virtualbox-qt (5.1.30-dfsg-1) ...
Processing triggers for mime-support (3.60ubuntu1) ...
Processing triggers for ureadahead (0.100.0-20) ...
Processing triggers for desktop-file-utils (0.23-1ubuntu3) ...
Processing triggers for menu (2.1.47ubuntu1) ...
Setting up virtualbox (5.1.30-dfsg-1) ...
Processing triggers for bamfdaemon (0.5.3+17.10.20170810-0ubuntu1) ...
Rebuilding /usr/share/applications/bamf-2.index...
Processing triggers for systemd (234-2ubuntu12.1) ...
Processing triggers for man-db (2.7.6.1-2) ...
Processing triggers for shared-mime-info (1.8-1) ...
Processing triggers for gnome-menus (3.13.3-6ubuntu5) ...
Processing triggers for hicolor-icon-theme (0.17-1) ...
Setting up virtualbox-qt (5.1.30-dfsg-1) ...
Setting up virtualbox-ext-pack (5.1.30-2) ...
Processing triggers for menu (2.1.47ubuntu1) ...
W: APT had planned for dpkg to do more than it reported back (10 vs 14).
Affected packages: virtualbox-ext-pack:amd64
~$


I tried starting virtualbox from the icon that now appears in my applications. I gave it time, but when it didn't launch, I restarted and tried again. Still not launching, but very thankful for your help in getting me this far. I'll try launching from a terminal window and see what happens.

If you have a suggestion for the app not starting, I'll be all ears. Thank you again : )
Hans
 

Hans

Member
Sorry all! And thanks for the correction Wiz! Once again, I was doing things from memory. I was at work (compiling!), so I posted during some compile time from my Windows PC at work. I didn't have my personal Linux laptop handy, otherwise I would have verified it before posting.....
I guess my memory isn't what it used to be..... Oops!
Hi JasKinasis,

Thanks for the help anyway, I appreciate it. The memory thing - yea, I'm right there with ya, hah.

Hans
 

Hans

Member
Thank you Wizard! Using the sudo apt-get -f install command, it looks like virtualbox-ext-pack was finally released. I'm back to where it just doesn't launch, but hoping that may be an easy fix now that the vexing ext file has been released. Here is the outcome of the command:

~$ sudo apt-get -f install

Reading package lists... Done
Building dependency tree
Reading state information... Done
Correcting dependencies... Done
The following packages were automatically installed and are no longer required:
gir1.2-nm-1.0 gir1.2-nma-1.0 gir1.2-timezonemap-1.0 gir1.2-xkl-1.0 kbuild
ktexteditor-data ktexteditor-katepart libeditorconfig0 libgit2-24
libhttp-parser2.1 libkf5texteditor5 libkf5texteditor5-libjs-underscore
libkf5threadweaver5 libtimezonemap-data libtimezonemap1 module-assistant
unity-scopes-runner
Use 'sudo apt autoremove' to remove them.
The following additional packages will be installed:
virtualbox virtualbox-qt
Suggested packages:
vde2 virtualbox-guest-additions-iso
The following NEW packages will be installed:
virtualbox virtualbox-qt
0 upgraded, 2 newly installed, 0 to remove and 57 not upgraded.
1 not fully installed or removed.
Need to get 0 B/24.0 MB of archives.
After this operation, 102 MB of additional disk space will be used.
Do you want to continue? [Y/n] y
(Reading database ... 350607 files and directories currently installed.)
Preparing to unpack .../virtualbox_5.1.30-dfsg-1_amd64.deb ...
Unpacking virtualbox (5.1.30-dfsg-1) ...
Preparing to unpack .../virtualbox-qt_5.1.30-dfsg-1_amd64.deb ...
Unpacking virtualbox-qt (5.1.30-dfsg-1) ...
Processing triggers for mime-support (3.60ubuntu1) ...
Processing triggers for ureadahead (0.100.0-20) ...
Processing triggers for desktop-file-utils (0.23-1ubuntu3) ...
Processing triggers for menu (2.1.47ubuntu1) ...
Setting up virtualbox (5.1.30-dfsg-1) ...
Processing triggers for bamfdaemon (0.5.3+17.10.20170810-0ubuntu1) ...
Rebuilding /usr/share/applications/bamf-2.index...
Processing triggers for systemd (234-2ubuntu12.1) ...
Processing triggers for man-db (2.7.6.1-2) ...
Processing triggers for shared-mime-info (1.8-1) ...
Processing triggers for gnome-menus (3.13.3-6ubuntu5) ...
Processing triggers for hicolor-icon-theme (0.17-1) ...
Setting up virtualbox-qt (5.1.30-dfsg-1) ...
Setting up virtualbox-ext-pack (5.1.30-2) ...
Processing triggers for menu (2.1.47ubuntu1) ...
W: APT had planned for dpkg to do more than it reported back (10 vs 14).
Affected packages: virtualbox-ext-pack:amd64
~$


I tried starting virtualbox from the icon that now appears in my applications. I gave it time, but when it didn't launch, I restarted and tried again. Still not launching, but very thankful for your help in getting me this far. I'll try launching from a terminal window and see what happens.

If you have a suggestion for the app not starting, I'll be all ears. Thank you again : )
Hans
I'm back - I just tried starting virtual box from inside the directory and it told me:

:/usr/lib/virtualbox$ virtualbox

VirtualBox: Error -610 in supR3HardenedMainInitRuntime!
VirtualBox: dlopen("/usr/lib/virtualbox/VBoxRT.so",) failed: <NULL>

VirtualBox: Tip! It may help to reinstall VirtualBox.
:/usr/lib/virtualbox$

...which is I think what got me into trouble in the first place with the ext-pak file, being one of the things I selected to install. I had encountered this message after Virtual Box stopped launching and then tried it from the terminal. What I think I did afterward was to go to the Pearl App Grid and install anything that showed up from a search of virtualbox.

I forgot to mention that I have the second file (PearlMATE-6.0-10-19-17_amd64.iso). And, thank you for educating me about the repositories; they make more sense now.
 

wizardfromoz

Super Moderator
Staff member
Gold Supporter
PEARL A LITTLE DIFFERENT IN CONFIGURATION

Just an FYI for Helpers and The Viewers alike that Pearl differs a little in its config, albeit it is based on Ubuntu.

With its Repositories, and its Sources, it is very similar, but differs just enough to confuse a little.

In /etc/apt , where mainstream Repos, PPAs (Personal Package Archives) &c can be accessed and edited/amended, naming conventions are different.

sources.list is known as sources.old , and a sources.list.saved is not (necessarily) generated through changes.

Under the Folder or Directory sources.list.d

But I don't see the "sources.list" file, just the "sources.list.d" file. Here is what's inside it:

appgrid-stable-artful.list rvm-smplayer-artful.list
official-package-repositories.list steam.list
opera-stable.list yannubuntu-boot-repair-artful.list
...these are appropriate, and the one I have highlighted is the one for day-to-day use if you change Software Sources, through Update Manager, it is reflected there.

Frenchman Yann's Boot Repair is not in mine, but is in Ubuntu 17.10 'Artful Aardvark' MATE I have, by default, it may have already been there, or the OP (Original Poster, that's you, Hans :D) may have added it.

Wizard

BTW - App Grid is a Pearl equivalent of Software Centre, for downloading and installing Apps.

Edited - added BTW
 

wizardfromoz

Super Moderator
Staff member
Gold Supporter
Hi all, again, and in particular, Hi @Hans ;)

These are of particular interest from your output above (& ta [Aussie for thanks] for providing same:)):

W: APT had planned for dpkg to do more than it reported back (10 vs 14).
Affected packages: virtualbox-ext-pack:amd64
and

0 upgraded, 2 newly installed, 0 to remove and 57 not upgraded.
1 not fully installed or removed.
and the last can be done later

Suggested packages:
vde2 virtualbox-guest-additions-iso
I have highlighted the parts I am concerned with.

These suggest to me, issues of dependencies, either conflicting or not yet installed.

The likely cause (not critical of you) is the introduction of v5.2 of Virtual Box into the picture.

You can fast-track us by checking in SPM (Synaptic) - search under virtual box, and where v5.1.3 appears, see if there is still reference to v5.2.

Since posting earlier, I have taken more of a look at v5.2, and it may be that you got it from one of 3 (or more) sites as follows:

https://pkgs.org/download/virtualbox-5.2

or

https://www.virtualbox.org/wiki/Linux_Downloads

or

http://download.virtualbox.org/virtualbox/5.2.0/

Does any of those look familiar?

If so, when you downloaded, you may have doubleclicked the file or opened GDebi, and it would have tried to install it for you.

You will likely need to remove all traces of that first, before v5.1.3 will run properly.

I have to take a road trip Thursday (tomorrow my time) and will be away for some time, but anyone whom is versed in Virtual Box should be able to help you from here, and I will check in when I get back.

Cheers, and you are doing very well, for someone whom is GUI-oriented, and ex-another OS, so take inspiration from that :D

Wizard
 

Hans

Member
Thanks for your help Wizard. I had tried deleting all of v5.1.3 but it still didn't help; I went ahead and partitioned my drive and installed Mac OS that way, so for now, I think I can let this problem go. Since this morning though, I have bigger problems - I installed all the recommended updates and when I rebooted - I get the "grub" screen. From there I can't get anywhere. I'm really in the dark on this one. Can you recommend anything for when this happens? Thanks again for your responses ~

Hans
 

Members online


Latest posts

Top