Announcement

**GreyGeek** · Jul 11, 2011, 08:08 PM

Re: There is a reoccurring error in virtualbox installation.

Originally posted by habakthanai

steven@Yeshuah:~$ sudo apt-get install /etc/init.d/vboxdrv setup

You have a misunderstanding of how to use apt-get to install software. You NEVER use a path to a file as the name of a package to install. You have already tried to install VBox, then you tried to uninstall it even though you were told that your package system was in a broken state.

Had you successfully installed VBox the kernel driver would have been installed had you used:

Code:

sudo /etc/init.d/vboxdrv setup

to do it.

Since VB 4.0 is not in the repository I suspect that you downloaded the *.deb package and used Gdebi to install it. So, it is now probably listed in Synaptic but the source would be "local".

Try these two commands, in rotation:
sudo apt-get -f install
sudo dpkg --configure -a
until, hopefully, they come clean.

If that doesn't work then perhaps someone here who is familiar with rebuilding the package cache and database can jump in and help you.

**Shabakthanai** · Jul 15, 2011, 12:44 PM

Re: There is a reoccurring error in virtualbox installation.

Originally posted by GreyGeek

Originally posted by habakthanai

steven@Yeshuah:~$ sudo apt-get install /etc/init.d/vboxdrv setup

First of all, I am so glad you responded, friend.

You have a misunderstanding of how to use apt-get to install software. You NEVER use a path to a file as the name of a package to install. Thank you. I was unaware. You have already tried to install VBox, then you tried to uninstall it even though you were told that your package system was in a broken state.

Had you successfully installed VBox the kernel driver would have been installed had you used: I did not attempt the following code "sudo /etc/init.d/vboxdrv setup" at this time, due to reoccurring error messages referring to VB.

Code:

sudo /etc/init.d/vboxdrv setup

to do it.

Since VB 4.0 is not in the repository I suspect that you downloaded the *.deb package and used Gdebi to install it. So, it is now probably listed in Synaptic but the source would be "local". I am not sure I understand what you mean by the repository, however, I used muon package manager and checked to see if Virtualbox 4.0 was included, and it was, and it also said that it is installed. Are not the packages in the package manager in the repository you mentioned?

I hope not in error again, but I attempted the following commands moments ago.

Try these two commands, in rotation:
sudo apt-get -f install
sudo dpkg --configure -a
until, hopefully, they come clean.

Here is what I got:

steven@Yeshuah:~$ sudo apt-get -f install
[sudo] password for steven:
Reading package lists... Done
Building dependency tree
Reading state information... Done
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
1 not fully installed or removed.
After this operation, 0 B of additional disk space will be used.
Setting up virtualbox-4.0 (4.0.10-72479~Ubuntu~natty) ...
dpkg: error processing virtualbox-4.0 (--configure):
subprocess installed post-installation script returned error exit status 127
Errors were encountered while processing:
virtualbox-4.0

I then opened Synaptic Package Manager, because I wanted to remove VB4.0 including dependencies; at completion of the Synaptic attempt, I got this error message:

An error occurred

The following details are provided:

E: virtualbox-r.0: subprocess installed pre-removal script returned error exit status 127

E: Sub-process /usr/bin/dpkg returned an error code (1)
steven@Yeshuah:~$ sudo dpkg --configure -a
steven@Yeshuah:~$

Since I don't seem to be able to remove the offending process by removing the application including dependency removal, I am at a loss how to proceed.I have tried to install a virtualbox or virtual machine for years. Much time lapses between attempts, however, I get to a similar point each time and am unable to understand the process or help from others. For years, this and another problem I have been attempting to resolve, always seem to fail.

If that doesn't work then perhaps someone here who is familiar with rebuilding the package cache and database can jump in and help you.

Thank you for the additional help, my friend.

**GreyGeek** · Jul 15, 2011, 01:38 PM

Re: There is a reoccurring error in virtualbox installation.

You might try the brute force hammer:

sudo dpkg --force-all --remove

**Shabakthanai** · Jul 17, 2011, 02:27 PM

Re: There is a reoccurring error in virtualbox installation.

Dear GreyGeek,

I tried your suggestion and get the following:

steven@Yeshuah:~$ sudo dpkg --force-all --remove
[sudo] password for steven:
dpkg: error: --remove needs at least one package name argument

Type dpkg --help for help about installing and deinstalling packages[*];
Use `dselect' or `aptitude' for user-friendly package management;
Type dpkg -Dhelp for a list of dpkg debug flag values;
Type dpkg --force-help for a list of forcing options;
Type dpkg-deb --help for help about manipulating *.deb files;

Options marked[*] produce a lot of output - pipe it through `less' or `more' !
steven@Yeshuah:~$

The following errors occurred while applying changes:

Package: virtualbox-4.0
Error: Package is in a very bad inconsistent state – you should reinstall it before attempting a removal.

Doing this puts me in a loop. I return with the same error messages. This VirtualBox problem affects other things I am doing. I am continually reminded that I need to fix something before I continue, and I attempt the suggestion given ending up it the loop, above mentioned. As you can see, even the 'Hammer' doesn't work. Thanks for your continued patience. perhaps I am not supposed to use a Virtual Machine. It is getting so frustrating, the thought of using a real Sledge Hammer has entered my thoughts.

Before I type in less or more, I wanted to get your advice how to proceed. Additionally, I tried to remove using Muon package manager. Here is what returned:

**GreyGeek** · Jul 17, 2011, 02:51 PM

Re: There is a reoccurring error in virtualbox installation.

My fault. I assumed that you understood that dpkg requires a target package. I just gave you the command and necessary parameters.

sudo dpkg --force-all --remove virtualbox-4.0

**Shabakthanai** · Jul 17, 2011, 04:15 PM

Re: There is a reoccurring error in virtualbox installation.

Sorry GreyGeek, I thought I noticed that particular command in the past. I suspect that I have done that many times, then failing without knowing why or what I omitted. When an expert gives advice, I just do what he says. Eventually I understand what is happening, but not always or usually until it is pointed out, like you just did. The result for your most recent suggestion is as follows:

steven@Yeshuah:~$ sudo dpkg --force-all --remove virtualbox-4.0
[sudo] password for steven:
dpkg: warning: overriding problem because --force enabled:
Package is in a very bad inconsistent state - you should
reinstall it before attempting a removal.
(Reading database ... 139226 files and directories currently installed.)
Removing virtualbox-4.0 ...
dpkg: error processing virtualbox-4.0 (--remove):
subprocess installed pre-removal script returned error exit status 127
dpkg: error while cleaning up:
subprocess installed post-installation script returned error exit status 127
Errors were encountered while processing:
virtualbox-4.0
steven@Yeshuah:~$

Where I changed the font to red, isn't that what we just attempted doing. It is why I have been suggesting a loop, and is the very reason for my frustration.

Each time I open the package manager to remove the virtualbox-4.0 and highlight 'virtualbox-4.0', I get 'removal' and 'upgrade' as the only options to proceed. Selecting 'upgrade' as the more like instructed 'install' option returns me to the loop.

In my post dated July 11th, I changed the font color to red as the area where I feel the problem is described, and my note in green, as a request for understanding. Please read that post and answer my statement. I need to know if my thought is just irrelevant or possibly something important that is overlooked.

Is it possible that I made an error in the partitioning process where I wanted to place my virtual machines and that this is where and why the installation cannot be either installed properly or removed completely? Probably a very dumb question, but it crossed my mind.

Thanks for your continuing patience, friend.

**Snowhog** · Jul 17, 2011, 04:32 PM

Re: There is a reoccurring error in virtualbox installation.

Have you attempted to reinstall the package? Muon does provide an option to reinstall a package that is already installed. At least it does in my version (1.1.2). What version of Muon are you using, and what version of Kubuntu (don't think you told us, and we haven't asked)?

If your Muon doesn't provide a Reinstallation button, then you can attempt to do so from a console:

Code:

sudo apt-get update && sudo apt-get install --reinstall virtualbox

Does Muon only report one instance of Virtualbox? Type virtualbox and then click on the By Status tab and choose Installed and note what Package name is identified and then click on Not Installed and note the Package name(s).

**Shabakthanai** · Jul 19, 2011, 01:16 AM

Re: There is a reoccurring error in virtualbox installation.

Hello, my friend,

Here is my muon version, 1.1.2 "Bullish Bandril"
Using KDE Development Platform 4.6.2 (4.6.2)

OS Version: Linux 2.6.38-8-generic KDE 4.6.2
Release: 11.04
Codename: Natty Norwall

Yes, I have attempted to install the package. I have also tried, using Synaptic, to remove all, including dependencies to try to completely remove everything previously installed. I have tried to force and purge also; I was following a comment I found from one of the forums. It did not work either. I foolishly did not enter notes on that attempt and am not sure I can remember the action accurately to relate it to you now. I only have a memory that I tried that. I also tried the 'reinstall' option. It provided the same result.

This is the current error after applying the command, "sudo apt-get update && sudo apt-get install --reinstall virtualbox",

E: The package virtualbox-4.0 needs to be reinstalled, but I can't find an archive for it.

Does this mean that when I use Muon to get a package, the package no longer exists in the archive? Or do I misunderstand the meaning of an archive and where we get our applications from?

Thanks for your thoughtful ongoing help and patience, Snowhog.

**GreyGeek** · Jul 19, 2011, 07:50 AM

Re: There is a reoccurring error in virtualbox installation.

One can redo "suto apt-get update" after replacing the existing status file with an earlier copy:
http://www.streamreader.org/askubunt...kg-status-file

Code:

Jim replied,

You should be able to work with a previous known good status file and update from there. 
Every time you do an install or a update, the status file is saved to a gzipped backup under /var/backups.
Doing an ls -l dpkg * on the directory shows:

-rw-r--r-- 1 root root  2266732 2010-09-30 08:35 dpkg.status.0
-rw-r--r-- 1 root root  624182 2010-09-29 08:49 dpkg.status.1.gz
-rw-r--r-- 1 root root  623844 2010-09-28 08:55 dpkg.status.2.gz
-rw-r--r-- 1 root root  620358 2010-09-24 11:04 dpkg.status.3.gz
-rw-r--r-- 1 root root  619021 2010-09-23 15:34 dpkg.status.4.gz
-rw-r--r-- 1 root root  619013 2010-09-23 08:03 dpkg.status.5.gz
-rw-r--r-- 1 root root  618968 2010-09-21 08:33 dpkg.status.6.gz

There's also a backup of the file created in the /var/lib/dpkg/ directory named status-old. 
Doing an ls -l status* on the directory shows:

-rw-r--r-- 1 root root 2266732 2010-09-30 08:35 status
-rw-r--r-- 1 root root 2267191 2010-09-30 08:35 status-old

So, to recover from a corruption, you should be able to do the following:

1. Make a backup of the corrupt status file:

mv /var/lib/dpkg/status /var/lib/dpkg/status_bkup

2. Copy an recent dpkg status file into place from either of the sources above:

either

cp /var/lib/dpkg/status-old /var/lib/dpkg/status

or

cp /var/backups/dpkg.status.#.gz /var/lib/dpkg/
gunzip -d /var/lib/dpkg/dpkg.status.#.gz 
mv /var/lib/dpkg/dpkg.status.# /var/lib/dpkg/status

3. Then run apt-get update:

sudo apt-get update

**Shabakthanai** · Jul 19, 2011, 02:22 PM

Re: There is a reoccurring error in virtualbox installation.

Dear GreyGeek,

I preface my response by stating that I am confused. Here is what I got when I typed 'ls -l status *' into the command line:

steven@Yeshuah:~$ ls -l status *
ls: cannot access status: No such file or directory

There was a long list of saved stuff from my '/home/steven' folders. Here is what is included that relates to Virtual Machine and VirtualBox:

-rwxr-xr-x 1 steven steven 101075736 2009-08-20 13:18 Vmware-Player-2.5.3-185404.i386.bundle

drwxr-xr-x 2 steven steven 4096 2011-07-11 15:39 VMwareDocs
-rw-r--r-- 1 steven steven 109162808 2011-07-11 15:47 VMware-player-3.1.1-282343.exe
-rw-r--r-- 1 steven steven 107025303 2011-07-11 15:46 VMware-Player-3.1.2-301548.i386.bundle
-rw-r--r-- 1 steven steven 102770460 2011-07-11 15:46 VMware-Player-3.1.2-301548.x86_64.bundle
-rw-r--r-- 1 steven steven 109206400 2011-07-11 15:40 VMware-player-3.1.3-324285.exe
-rw-r--r-- 1 steven steven 107374882 2011-07-11 15:42 VMware-Player-3.1.3-324285.i386.bundle
-rw-r--r-- 1 steven steven 103173173 2011-07-11 15:45 VMware-Player-3.1.3-324285.x86_64.bundle
-rw-r--r-- 1 steven steven 70738512 2011-07-11 15:45 VMware-VIX-1.10.2-331862.i386.bundle
-rw-r--r-- 1 steven steven 76018726 2011-07-11 15:45 VMware-VIX-1.10.2-331862.x86_64.bundle
-rw-r--r-- 1 steven steven 70734590 2011-07-11 15:39 Vmware-VIX-1.10.3-368992.i386.bundle

VirtualBox VMs:
total 8
drwxr-xr-x 4 steven steven 4096 2011-07-11 13:11 VB1
drwxr-xr-x 2 steven steven 4096 2011-07-11 17:10 VM1

When I typed 'ls -l status *' in the command line, this is all that printed:

steven@Yeshuah:~$ ls -l status*
ls: cannot access status*: No such file or directory

There were no .gz files or any other compressed files. Following this I opened 'dpkg.status.0' using kate. The amount of data was massive. I read for an hour or so, but progressed less than 1% of the data. I scanned a bit, but did not see failures in any of the installations. The very first entry was about a successful install of the VMMouse driver. It would take me days to read all the data, so I stopped. I will continue if it is advised, however, I did not see anything like you posted, where the various 'dpkg.status.?' were showing .gz files. What would a corrupt file look like? Would it print in another color, like red, to identify itself, or am I supposed to recognize it by it's content? I am not there yet in my understanding.

The following may or may not be related to my problem. I do not use Rekonq, because it crashes too often. I rarely use Facebook, however, when I get an email from their website, it always opens in Rekonk and is an inquiry from someone I know or who knows someone I know. In any event, the page invariably opens crashed. So today, I attempted to remove Rekonq hoping that a working browser would take over the job of default. I was unable to remove Rekonk. The process was stopped with a mention to Reinstall VirtualBox 4.0. My computer will neither allow me to successfully install or remove VirtualBox 4.0. I have used the command line approach, the sledgehammer command line approach and both Muon and Synaptic to make this happen. Rekonq is similar. It crashes every time I attempt to use it and refuses to be removed, until I resolve the VirtualBox issue.

I am suspicious that I am not to be able to have a VirtualBox or Virtual Machine. It seems so easy for others. Perhaps I am the exception and am too dumb or too old.

**GreyGeek** · Jul 19, 2011, 04:18 PM

Re: There is a reoccurring error in virtualbox installation.

The instructions were:

the status file is saved to a gzipped backup under /var/backups.
Doing an ls -l dpkg * on the directory

So, in a terminal you would type:

jerry@sonyvgnfw140e:~$ ls -l /var/backups/dpkg*

and here is what would be returned (except that the listing is for my /var/backups directory. Yours may be different.):

-rw-r--r-- 1 root root 2287679 2011-07-17 18:49 /var/backups/dpkg.status.0
-rw-r--r-- 1 root root 636577 2011-07-17 13:17 /var/backups/dpkg.status.1.gz
-rw-r--r-- 1 root root 636578 2011-07-15 14:34 /var/backups/dpkg.status.2.gz
-rw-r--r-- 1 root root 636547 2011-07-13 13:08 /var/backups/dpkg.status.3.gz
-rw-r--r-- 1 root root 636551 2011-07-12 08:36 /var/backups/dpkg.status.4.gz
-rw-r--r-- 1 root root 636550 2011-07-09 13:59 /var/backups/dpkg.status.5.gz
-rw-r--r-- 1 root root 636550 2011-07-07 14:41 /var/backups/dpkg.status.6.gz
jerry@sonyvgnfw140e:~$

Dumb? Hardly.
Not paying close attention to details? Probably so.
Too old? I'm 70 and without Google I have no memory at all.

**Shabakthanai** · Jul 19, 2011, 05:34 PM

Re: There is a reoccurring error in virtualbox installation.

Originally posted by GreyGeek

The instructions were:

the status file is saved to a gzipped backup under /var/backups.
Doing an ls -l dpkg * on the directory

The red print above has a space between dpkg (and) *; the red print below does not, is that significant?

So, in a terminal you would type:

jerry@sonyvgnfw140e:~$ ls -l /var/backups/dpkg*

and here is what would be returned (except that the listing is for my /var/backups directory. Yours may be different.):

-rw-r--r-- 1 root root 2287679 2011-07-17 18:49 /var/backups/dpkg.status.0
-rw-r--r-- 1 root root 636577 2011-07-17 13:17 /var/backups/dpkg.status.1.gz
-rw-r--r-- 1 root root 636578 2011-07-15 14:34 /var/backups/dpkg.status.2.gz
-rw-r--r-- 1 root root 636547 2011-07-13 13:08 /var/backups/dpkg.status.3.gz
-rw-r--r-- 1 root root 636551 2011-07-12 08:36 /var/backups/dpkg.status.4.gz
-rw-r--r-- 1 root root 636550 2011-07-09 13:59 /var/backups/dpkg.status.5.gz
-rw-r--r-- 1 root root 636550 2011-07-07 14:41 /var/backups/dpkg.status.6.gz
jerry@sonyvgnfw140e:~$

Dumb? Hardly.
Not paying close attention to details? Probably so.
Too old? I'm 70 and without Google I have no memory at all.

**Shabakthanai** · Jul 19, 2011, 06:24 PM

Re: There is a reoccurring error in virtualbox installation.

I am feeling pressure now, my friend. I have attempted to follow instructions and have come up with this. Can you see what I did wrong?

steven@Yeshuah:~$ ls -l /var/backups/dpkg*
-rw-r--r-- 1 root root 1650911 2011-07-19 02:13 /var/backups/dpkg.status.0
-rw-r--r-- 1 root root 442392 2011-07-17 17:44 /var/backups/dpkg.status.1.gz
-rw-r--r-- 1 root root 442123 2011-07-16 09:41 /var/backups/dpkg.status.2.gz
-rw-r--r-- 1 root root 430215 2011-07-14 15:07 /var/backups/dpkg.status.3.gz
-rw-r--r-- 1 root root 429692 2011-07-13 14:02 /var/backups/dpkg.status.4.gz
-rw-r--r-- 1 root root 427628 2011-07-13 00:33 /var/backups/dpkg.status.5.gz
-rw-r--r-- 1 root root 420806 2011-07-11 17:29 /var/backups/dpkg.status.6.gz
steven@Yeshuah:~$ ls -l /var/lib/dpkg/status*
-rw-r--r-- 1 root root 1650911 2011-07-19 02:13 /var/lib/dpkg/status_bkup
-rw-r--r-- 1 root root 1650911 2011-07-19 02:12 /var/lib/dpkg/status-old
steven@Yeshuah:~$ mv /var/lib/dpkg/status /var/lib/dpkg/status_bkup
mv: cannot stat `/var/lib/dpkg/status': No such file or directory
steven@Yeshuah:~$

**GreyGeek** · Jul 19, 2011, 07:50 PM

Re: There is a reoccurring error in virtualbox installation.

Commands against any file in any directory except your home directory must be prefaced with the "sudo" command. Or, using "kdesudo dolphin" in a Konsole, you can use the file manager to make the changes.

Announcement

There is a reoccurring error in virtualbox installation.

There is a reoccurring error in virtualbox installation.

Comment

Comment

Comment

Comment

Comment

Comment

Comment

Comment

Comment

Comment

Comment

Comment

Comment

Comment