Need help properly configuring VirtualBox and guest additions

[Shabakthanai]

Admin note. This is a fork of the thread Want to remove LibreOffice and install OpenOffice Kubuntu 12.10. The posts involving VirtualBox problems and solutions have been moved out of that thread and into this one.

---------------------------------------------------------------------------------------------------------------

Kubuntu 12.10 KDE 4.9.3

I attempted to install Synaptic Package Manager, however when I attempted to open Synaptic, the following error message appears:

E: Type 'Reading' is not known on line 1 in source list
/etc/apt/sources.list.d/virtualbox.list

E: The list of sources could not be read.

Go to the repository dialog to correct the problem.

E: _cache->open() failed, please report.

I recently failed to install VirtualBox on my computer. I also removed VirtualBox including "Purge". Nonetheless, the above error refers to /etc/apt/sources.list.d/virtualbox.list. When I looked at the file, I noticed another VirtualBox text document as well. I do not understand how to repair the apparent error! Do I remove the line? Do I remove the Text files that relate to VirtualBox? They seem to remain after purge of the application and are obviously negatively affecting other packages.

Where is the "repository dialog" and how do I correct the problem once there? To whom do I report "cache->open() failed?

In any event, I would love VirtualBox to work, but I am unable to do so, even with help. So as a result, I would like to have VirtualBox unable to screw up any other applications I use. I would like to be able to edit a document too. And I would like to be able to open Synaptic, if they have OpenOffice in their library.

I am sorry to appear frustrated, but when things change and I have no idea of how or why, I get frustrated. Thanks for any help toward a solution.

[pauly]

Virtualbox is in the repositories so you should be able to find it with muon. If you want the latest stable version they have an easy deb installer on the following page.

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

synaptic will not change the packages available. Muon and Synaptic use the same source list. The source list is determined by your distribution.

[SteveRiley]

Separately, let's clean up your failed VirtualBox attempt. To begin, please show the output of

tail -n +1 /etc/apt/sources.list.d/*

and

dpkg -l | grep -i virtualbox

[Shabakthanai]

Hi Pauly, There wasn't any line containing anything about vurtualbox. I ran sudo apt-get update anyway and got the following:

steven@Yeshuah:~$ sudo apt-get update
[sudo] password for steven:
E: Type 'Reading' is not known on line 1 in source list /etc/apt/sources.list.d/virtualbox.list
E: The list of sources could not be read.
steven@Yeshuah:~$

OpenOffice is currently downloading, however at a very slow rate, currently 120KB/s. 321mb remaining. It is going to take a while. I am posting ahead of installation in case my current situation may reveal something to you that makes no sense to me. It seems to me that this problem relating to VB is why I have trouble installing VB. Should I attempt installing VB now anyway, or wait for a solution to the entry the computer keeps referring to. I appreciate your help. Couldn't return to my computer until right now. Additionally, I upgraded to KDE 4.9.4 before reading your post. Thanks again, my friend.QUOTE=pauly;320210]open muon and click on settings, click configure software sources and find the virtualbox repository and remove it. Then update.

or type

Find the line containing virtualbox and remove it. Save the file.

Then run

then

then

then
not sure that is going to be a better option but if that is what you want it should work.[/QUOTE]

[Shabakthanai]

Actually this was relating to Office replacement. Nonetheless, virtualbox came up when working that problem, and I have been trying to get a virtual machine working for years now. I suspect it has to do with my limited computing abilities, but I still want the Virtual Machine capability. I recently spent days working that problem to an unsuccessful conclusion again. I have used so much of the forum's time, I thought to give it a rest for a while, but to readdress the issue again later. I am not going to give up on getting a Virtual Machine. I don't know how you guys do it. Every person I know on the Internet seems to have an easy time of installing VB or VM. It is an enigma for me. I am wondering if this line the computer is referring to is the whole problem, yet when I search for it, I can not find it. By the way thanks for your help; I see your icon all the time. You are one of the special people that help slow people like me. Don't know what we would do without you.

The original post appears to describe two unrelated problems: replacing LibreOffice with OpenOffice and fixing a broken VirtualBox install. Is my reading correct?

[Shabakthanai]

steven@Yeshuah:~$ sudo tail -n +1 /etc/apt/sources.list.d/*
[sudo] password for steven:
==> /etc/apt/sources.list.d/ehoover-compholio-quantal.list <==
deb http://ppa.launchpad.net/ehoover/compholio/ubuntu quantal main
# deb-src http://ppa.launchpad.net/ehoover/compholio/ubuntu quantal main

==> /etc/apt/sources.list.d/ehoover-compholio-quantal.list.save <==
deb http://ppa.launchpad.net/ehoover/compholio/ubuntu quantal main
# deb-src http://ppa.launchpad.net/ehoover/compholio/ubuntu quantal main

==> /etc/apt/sources.list.d/medibuntu.list <==
## Please report any bug on https://bugs.launchpad.net/medibuntu/
deb http://packages.medibuntu.org/ quantal free non-free #Medibuntu - Ubuntu 12.10 "quantal quetzal"
# deb-src http://packages.medibuntu.org/ quantal free non-free #Medibuntu (source) - Ubuntu 12.10 "quantal quetzal"

==> /etc/apt/sources.list.d/medibuntu.list.save <==
## Please report any bug on https://bugs.launchpad.net/medibuntu/
deb http://packages.medibuntu.org/ quantal free non-free #Medibuntu - Ubuntu 12.10 "quantal quetzal"
# deb-src http://packages.medibuntu.org/ quantal free non-free #Medibuntu (source) - Ubuntu 12.10 "quantal quetzal"

==> /etc/apt/sources.list.d/upubuntu-com-office-quantal.list <==
deb http://ppa.launchpad.net/upubuntu-com/office/ubuntu quantal main
# deb-src http://ppa.launchpad.net/upubuntu-com/office/ubuntu quantal main

==> /etc/apt/sources.list.d/upubuntu-com-office-quantal.list.save <==
deb http://ppa.launchpad.net/upubuntu-com/office/ubuntu quantal main
# deb-src http://ppa.launchpad.net/upubuntu-com/office/ubuntu quantal main

==> /etc/apt/sources.list.d/virtualbox.list <==
Reading package lists...
Building dependency tree...
Reading state information...

==> /etc/apt/sources.list.d/virtualbox.list.save <==
Reading package lists...
Building dependency tree...
Reading state information...
steven@Yeshuah:~$ sudo dpkg -l | grep -i virtualbox
ii virtualbox-4.2 4.2.6-82870~Ubuntu~quantal amd64 Oracle VM VirtualBox
rc virtualbox-guest-utils 4.1.18-dfsg-1ubuntu1.1 amd64 x86 virtualization solution - non-X11 guest utilities
rc virtualbox-guest-x11 4.1.18-dfsg-1ubuntu1.1 amd64 x86 virtualization solution - X11 guest utilities
rc virtualbox-qt 4.1.18-dfsg-1ubuntu1.1 amd64 x86 virtualization solution - Qt based user interface
steven@Yeshuah:~$

Since I don't know what this will accomplish, I will wait for your review and response. Thanks for your patience.

Separately, let's clean up your failed VirtualBox attempt. To begin, please show the output of

tail -n +1 /etc/apt/sources.list.d/*

and

dpkg -l | grep -i virtualbox

[Shabakthanai]

I didn't give up, it was getting me so upset and disappointed with myself, I needed a break from it. I have been trying to get VB installed for years. It is quite embarrassing.

yes I know but I had given him the command to install the open office ppa. So it would have been there assuming he did. But alas we are helping someone who started a thread and gave up.

[pauly]

I know someone with more experience could suggest a better solution but I have had a problem like this before using ppa purge and the way I fixed it was to add the ppa in again and remove it a different way. Your gonna want to add the same virtual box ppa you added the last time. Then instead of using ppa purge open muon and click settings, click configure software sources. Goto the other software sources tab, select the virtual box ppa and click remove. Then run sudo apt-get update.

[SteveRiley]

By the way thanks for your help; I see your icon all the time. You are one of the special people that help slow people like me. Don't know what we would do without you.

Thank you. I'm catching up on the thread here and will reply with more information soon.

[SteveRiley]

Let's now consider your VirtualBox issue.

I still want the Virtual Machine capability. I recently spent days working that problem to an unsuccessful conclusion again. I have used so much of the forum's time, I thought to give it a rest for a while, but to readdress the issue again later. I am not going to give up on getting a Virtual Machine. I don't know how you guys do it. Every person I know on the Internet seems to have an easy time of installing VB or VM. It is an enigma for me.

First things first: there's no need to apologize for using the forum's time. This forum exists precisely to help folks work through challenges and improve their understanding of Kubuntu and Linux. We do this because we want to.

I'm curious why you want to set up a virtual machine. What do you intend to do with it?

= = =

when I search for it, I can not find it.

It's because a particular file in your computer is malformed. Continue reading. I'm going to create a mini-tutorial along the way.

There wasn't any line containing anything about vurtualbox. I ran sudo apt-get update anyway and got the following:

steven@Yeshuah:~$  sudo apt-get update
[sudo] password for steven: 
E: Type 'Reading' is not known on line 1 in source list /etc/apt/sources.list.d/virtualbox.list
E: The list of sources could not be read.

The error message gives us a clue. When you add PPAs and other third-party repositories to your software sources, each PPA or repository creates a file in the subdirectory /etc/apt/sources.list.d. This file tells APT, the low-level package manager for Ubuntu (and other Debian-based Linuxes), where to obtain packages from. At some point in time, you did something to create this file. But, as I shall explain, your copy of this file contains something very unusual. In fact, I've never seen your particular situation before.

In the quote below, the command I had you type results in an output that lists the name of and the contents of every file in /etc/apt/sources.list.d.

steven@Yeshuah:~$ sudo tail -n +1 /etc/apt/sources.list.d/*
[sudo] password for steven: 
==> /etc/apt/sources.list.d/ehoover-compholio-quantal.list <==
deb [url]http://ppa.launchpad.net/ehoover/compholio/ubuntu[/url] quantal main
# deb-src [url]http://ppa.launchpad.net/ehoover/compholio/ubuntu[/url] quantal main

The above file is properly formed. In fact, with two exceptions, all of your files are properly formed.

The malformed files -- the two exceptions -- are:

==> /etc/apt/sources.list.d/virtualbox.list <==
Reading package lists...
Building dependency tree...
Reading state information...

==> /etc/apt/sources.list.d/virtualbox.list.save <==
Reading package lists...
Building dependency tree...
Reading state information...

Somehow, and I really can't predict why, these files no longer contain pointers to Oracle's VirtualBox repository but instead contain the output of what you'd normally see on the screen when running apt-get dist-upgrade! How this happened is rather a mystery. If you go back and look at the first line of the error message:

E: Type 'Reading' is not known on line 1 in source list /etc/apt/sources.list.d/virtualbox.list

You'll see that it's complaining about the word "Reading" in the file virtualbox.list.

Finally, the following information:

steven@Yeshuah:~$ sudo dpkg -l | grep -i virtualbox
ii  virtualbox-4.2                                              4.2.6-82870~Ubuntu~quantal                amd64        Oracle VM VirtualBox
rc  virtualbox-guest-utils                                      4.1.18-dfsg-1ubuntu1.1                    amd64        x86 virtualization solution - non-X11 guest utilities
rc  virtualbox-guest-x11                                        4.1.18-dfsg-1ubuntu1.1                    amd64        x86 virtualization solution - X11 guest utilities
rc  virtualbox-qt                                               4.1.18-dfsg-1ubuntu1.1                    amd64        x86 virtualization solution - Qt based user interface

tells me that the core of VirtualBox 4.2 is installed. Other components were once installed but have been removed while their configuration files still exist on the system.

I'll end this post now, and follow up with steps to clean up and get VirtualBox installed properly.

[SteveRiley]

To install VirtualBox, you have two choices. The Ubuntu repository contains the necessary packages, but they are usually a number of releases behind. The Oracle repository always contains the most up-to-date version. I'd recommend the latter.

I will take you step-by-step through the installation process. I would like to do this all at the command line, too. I'd further recommend, as you complete each step, that you copy-paste the lines below rather than retype them.


Step 1. Remove the currently installed packages and lingering configuration files. Run:

sudo dpkg --purge virtualbox-4.2 virtualbox-guest-utils virtualbox-guest-x11 virtualbox-qt

This may actually trigger a number of processes, including (I think) creating a new initramfs (part of the collection of files that help your computer start). I'd suggest rebooting once the purge finishes.


Step 2. Eliminate remaining package traces. Run:

sudo rm /var/lib/apt/lists/*virtualbox*

sudo apt-get clean && sudo apt-get update

Step 3. Edit. I just noticed your PM to me. That stuff about having to use RAR and the resulting file names imply that you've downloaded a prebuilt virtual machine? Since I'm having you start from scratch, I'd also like for you to clear out any existing VMs, since they probably aren't functioning correctly anyway. I believe the dpkg --remove command above will prompt you for this; if so, then tell it "yes." Also, clean out your VirtualBox data directory. Since I can't remember whether it's upper or lower case, I'll be broad with my commands. Run:

rm -rfv ~/.VirtualBox/* ~/.virtualbox/*

rm -rfv ~/VirtualBox/* ~/virtualbox/*

(Yes, the first one has dots and the second one does not.)


Step 4. Fix your VirtualBox repository software source file. Choose one of the following two methods:

* Edit the existing file by following the parts in blue: step 4, path A
* Replace the file with a new one by following the parts in green: step 4, path B.

Step 4, Path A. To edit the existing file, run:

sudo nano /etc/apt/sources.list.d/virtualbox.list

Welcome to the command line text editor! Don't worry, this one is rather easy. Delete every line in the file: repeatedly press Ctrl+K until all lines are gone. Now type the following:

deb http://download.virtualbox.org/virtualbox/debian quantal contrib

To save the file, press Ctrl+X. Answer y to the prompt.

Step 4 is complete; skip the green part (Path B) and continue at Step 5.

Step 4, Path B. (Do this only if you decided not to follow the blue part, Path A.) To replace the file with a new one, run:

echo "deb http://download.virtualbox.org/virtualbox/debian quantal contrib" | sudo tee /etc/apt/sources.list.d/virtualbox.list

Step 5. Obtain Oracle's package signing key. This allows APT to verify the digital signatures of the downloaded packages. Run:

wget -q http://download.virtualbox.org/virtualbox/debian/oracle_vbox.asc -O- | sudo apt-key add -

Step 6. Update your package list again, to incorporate the Oracle repository. Run:

sudo apt-get update

Step 7. VirtualBox requires certain kernel modules to run, and these must be updated each time the kernel is updated. Fortunately, VirtualBox can do this automatically using a service called dynamic kernel module support. You probably already have this installed, but let's get it again. Run:

sudo apt-get install --reinstall dkms

Step 8. Install VirtualBox. Run:

sudo apt-get install virtualbox-4.2

Step 9. Finally, download the VirtualBox extensions:

wget http://download.virtualbox.org/virtualbox/4.2.6/Oracle_VM_VirtualBox_Extension_Pack-4.2.6-82870.vbox-extpack

At this point, you should be able to run the VirtualBox Manager, install the extensions file, and then create a virtual machine. Let us know how it goes.

[Shabakthanai]

xxx

To install VirtualBox, you have two choices. The Ubuntu repository contains the necessary packages, but they are usually a number of releases behind. The Oracle repository always contains the most up-to-date version. I'd recommend the latter.

I will take you step-by-step through the installation process. I would like to do this all at the command line, too. I'd further recommend, as you complete each step, that you copy-paste the lines below rather than retype them.

First, remove the currently installed packages and lingering configuration files. Run:

sudo dpkg --purge virtualbox-4.2 virtualbox-guest-utils virtualbox-guest-x11 virtualbox-qt

This may actually trigger a number of processes, including (I think) creating a new initramfs (part of the collection of files that help your computer start). I'd suggest rebooting once the purge finishes.

Next, eliminate remaining package traces. Run:

sudo rm /var/lib/apt/lists/*virtualbox*

sudo apt-get clean && sudo apt-get update

steven@Yeshuah:~$ sudo dpkg --purge virtualbox-4.2 virtualbox-guest-utils virtualbox-guest-x11 virtualbox-qt
[sudo] password for steven:
(Reading database ... 189239 files and directories currently installed.)
Removing virtualbox-4.2 ...
* Stopping VirtualBox kernel modules [ OK ]
Purging configuration files for virtualbox-4.2 ...
Removing virtualbox-guest-utils ...
Purging configuration files for virtualbox-guest-utils ...
Removing virtualbox-guest-x11 ...
Purging configuration files for virtualbox-guest-x11 ...
Removing virtualbox-qt ...
Purging configuration files for virtualbox-qt ...
Processing triggers for hicolor-icon-theme ...
Processing triggers for shared-mime-info ...
Unknown media type in type 'all/all'
Unknown media type in type 'all/allfiles'
Unknown media type in type 'uri/mms'
Unknown media type in type 'uri/mmst'
Unknown media type in type 'uri/mmsu'
Unknown media type in type 'uri/pnm'
Unknown media type in type 'uri/rtspt'
Unknown media type in type 'uri/rtspu'
Processing triggers for ureadahead ...
ureadahead will be reprofiled on next reboot
steven@Yeshuah:~$ sudo rm /var/lib/apt/lists/*virtualbox*
rm: cannot remove `/var/lib/apt/lists/*virtualbox*': No such file or directory
steven@Yeshuah:~$ sudo apt-get clean && sudo apt-get update
E: Type 'Reading' is not known on line 1 in source list /etc/apt/sources.list.d/virtualbox.list
E: The list of sources could not be read.
steven@Yeshuah:~$

Edit. I just noticed your PM to me. That stuff about having to use RAR and the resulting file names imply that you've downloaded a prebuilt virtual machine? Since I'm having you start from scratch, I'd also like for you to clear out any existing VMs, since they probably aren't functioning correctly anyway. I believe the dpkg --remove command above will prompt you for this; if so, then tell it "yes." Also, clean out your VirtualBox data directory. Since I can't remember whether it's upper or lower case, I'll be broad with my commands. Run:
[code]rm -rfv ~/.VirtualBox/* ~/.virtualbox/*

steven@Yeshuah:~$ [code]rm -rfv ~/.VirtualBox/* ~/.virtualbox/*

rm: command not found
steven@Yeshuah:~$

rm -rfv ~/VirtualBox/* ~/virtualbox/*

(Yes, the first one has dots and the second one does not.)

steven@Yeshuah:~$ [code]rm -rfv ~/.VirtualBox/* ~/.virtualbox/*

rm: command not found
steven@Yeshuah:~$ 
steven@Yeshuah:~$ rm -rfv ~/VirtualBox/* ~/virtualbox/*

steven@Yeshuah:~$


Next, fix your VirtualBox repository software source file. Run:

sudo nano /etc/apt/sources.list.d/virtualbox.list

steven@Yeshuah:~$

sudo nano /etc/apt/sources.list.d/virtualbox.list

[code]sudo: command not found
steven@Yeshuah:~$


Looking back, I am probably supposed to exclude the words "[code]", however the next instruction also confuses me too. You may have noticed that the "E: Type 'Reading' is not known on line 1 in source list /etc/apt/sources.list.d/virtualbox.list" remained after the removal and purging process was entered. That confused me too.

Next, you talk about a command line editor with instructions to remove a lot of lines of data; how do I get those lines to appear? Then, do I highlight the lines and press "Ctrl+K" without the quotes?

I am thinking I had better wait for you to correct me here, before I continut. The answer about downloading an additional complete download, it was recommended I go to a page where that was exactly the thing to do. On that page, they suggested the 64bit version was not yet available, so I downloaded the 12.10 i386 package. I have an AMD processor, so I suppose downloading the i386 package was OK to do.

In answer to why I wanted to have a virtual machine, I have two reasons. I am told that I can create a VB that contains Netflix that works great. And the second reason, is I wanted to install the Kubuntu 13.04 64bit beta, so that I could learn, in advance of the rc of that package release, by working with it in a safe environment. I have wanted to do that for several previous releases.


Welcome to the command line text editor! Don't worry, this one is rather easy. Delete every line in the file: repeatedly press Ctrl+K until all lines are gone. Now type the following:

deb http://download.virtualbox.org/virtualbox/debian quantal contrib

To save the file, press Ctrl+X. Answer y to the prompt.

(Alternately, you could have deleted the file and created a new one. Instead, I had you edit the file, so that you could gain a bit of new experience.)

Next, obtain Oracle's package signing key. This allows APT to verify the digital signatures of the downloaded packages. Run:

wget -q http://download.virtualbox.org/virtualbox/debian/oracle_vbox.asc -O- | sudo apt-key add -

Now, update your package list again, to incorporate the Oracle repository. Run:

sudo apt-get update

VirtualBox requires certain kernel modules to run, and these must be updated each time the kernel is updated. Fortunately, VirtualBox can do this automatically using a service called dynamic kernel module support. You probably already have this installed, but let's get it again. Run:

sudo apt-get install --reinstall dkms

Next, install VirtualBox. Run:

sudo apt-get install virtualbox-4.2

Finally, download the VirtualBox extensions:

wget http://download.virtualbox.org/virtualbox/4.2.6/Oracle_VM_VirtualBox_Extension_Pack-4.2.6-82870.vbox-extpack

At this point, you should be able to run the VirtualBox Manager, install the extensions file, and then create a virtual machine. Let us know how it goes.

[SteveRiley]

I need to fix up your quoting in the message above. One sec.

[Shabakthanai]

You can see where I stopped my attempt to follow you above. Next I entered your code instructions without the bracketed [code] and was successful, I believe. I removed the three lines and entered "y". Next I attempted to enter the repository, I believe and got this:

steven@Yeshuah:~$ deb http://download.virtualbox.org/virtualbox/debian quantal contrib
No command 'deb' found, did you mean:
Command 'debc' from package 'devscripts' (main)
Command 'derb' from package 'libicu-dev' (main)
Command 'dab' from package 'bsdgames' (universe)
Command 'debi' from package 'devscripts' (main)
Command 'xdeb' from package 'xdeb' (universe)
Command 'dwb' from package 'dwb' (universe)
deb: command not found
steven@Yeshuah:~$ sudo deb http://download.virtualbox.org/virtualbox/debian quantal contrib
sudo: deb: command not found
steven@Yeshuah:~$

I tried first by copying and pasting then tried same with sudo; neither succeeded, so I am waiting for additional instruction before I continue. Sorry to be so stupid. Please continue your patience, I am learning, but slowly.

[SteveRiley]

Looking back, I am probably supposed to exclude the words "[code]"

I'm curious about something. Can you describe how you're viewing the forum? It's highly unusual that you should see the [ CODE ] tag unless you're in the middle of manipulating a quoted portion that contains one. Normally, you should see something like the following, which is a screen shot of a portion of my post:



Copy each line from inside the box and paste it where the cursor is blinking in the Konsole, then press Enter. I suspect you're clicking the forum's Reply button and working from there, which will produce incorrect results.

You may have noticed that the "E: Type 'Reading' is not known on line 1 in source list /etc/apt/sources.list.d/virtualbox.list" remained after the removal and purging process was entered. That confused me too.

That's OK, because we aren't done with the cleanup process just yet.

Next, you talk about a command line editor with instructions to remove a lot of lines of data; how do I get those lines to appear? Then, do I highlight the lines and press "Ctrl+K" without the quotes?

The command that begins with sudo nano starts the text editor and loads the file specified after the word nano. Based on the output of one of the commands I had you run earlier, you will see these three lines:

Reading package lists...
Building dependency tree...
Reading state information...

That stuff shouldn't be there. I'm having you use the text editor to delete that and replace it with the correct entries. You do not need to highlight any lines. Ctrl+K deletes whatever line the cursor is sitting on. If you follow my instructions exactly, you'll be fine.

The answer about downloading an additional complete download, it was recommended I go to a page where that was exactly the thing to do. On that page, they suggested the 64bit version was not yet available, so I downloaded the 12.10 i386 package. I have an AMD processor, so I suppose downloading the i386 package was OK to do.

Processor naming conventions can be confusing. I'll spare you the history and give you the quick list:

* "i386" and "x86" mean 32-bit processors, from Intel and from AMD
* "amd64" and "x86_64" mean 64-bit processors, from Intel and from AMD

When setting up VirtualBox, you have to match the architecture of VirtualBox to that of your computer. How can you know what your computer is? The following command will let you know:

uname -a

For example, mine is:

steve@t520:~$ uname -a
Linux t520 3.7.3-030703-generic #201301171415 SMP Thu Jan 17 19:16:23 UTC 2013 x86_64 x86_64 x86_64 GNU/Linux

The presence of "x86_64" in the output indicates that I'm running a 64-bit operating system. Thus, my VirtualBox software must be 64-bit. However, inside VirtualBox, I can choose to run both 64-bit and 32-bit virtual machines. Yet another item to be aware of.