VirtualBox

[Gene Heskett]

On Sunday 19 October 2014 21:44:29 Saqman2060 did opine
And Gene did reply:
> Also remove the repositories that you added.
> 
> -----Original Message-----
> From: "Thomas Blasejewicz" <thomas at s7.dion.ne.jp>
> Sent: â€ژ10/â€ژ19/â€ژ2014 9:26 PM
> To: "ubuntu-users at lists.ubuntu.com" <ubuntu-users at lists.ubuntu.com>
> Subject: Re: VirtualBox
> 
> (2014/10/20 2:41), Nils Kassube wrote:
> > Thomas Blasejewicz wrote:
> >> So ... right now NO SUDO COMMAND whatsoever works ...
> > 
> > What do you mean by the statement above? Do you get an error message
> > if you try to run any sodo commands? Or do you mean that the result
> > of the commands you tried so far to make virtualbox work just wasn't
> > succeessful?
> > 
> > 
> > Nils
> 
> Good morning
> The machine causing all these troubles is at home and I am at work now,
> so that trying things will have to wait until evening.
> VirtualBox should be gone, because I removed it (successfully?)
> earlier.
> 
> When I run something like "sudo apt-get update", I get the output
> copied below, always ending with the same error.
> Meaning, as far as I can understand it, that I can type in ANY sudo
> command, but that is never executed successfully.
> I also tried to download, update, reinstall etc. the package seemingly
> causing the problems: "linux-image-3.13.0-37-generic".
> But so far nothing has helped.
> 
> zzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzz
> 
> (synaptic:7550): GLib-CRITICAL **: g_child_watch_add_full: assertion
> 'pid > 0' failed
> (Reading database ... 249973 files and directories currently
> installed.) Preparing to unpack
> .../linux-image-3.13.0-37-generic_3.13.0-37.64_i386.deb ...
> Done.
> Unpacking linux-image-3.13.0-37-generic (3.13.0-37.64) over
> (3.13.0-37.64) ...
> Examining /etc/kernel/postrm.d .
> run-parts: executing /etc/kernel/postrm.d/initramfs-tools
> 3.13.0-37-generic /boot/vmlinuz-3.13.0-37-generic
> run-parts: executing /etc/kernel/postrm.d/zz-extlinux 3.13.0-37-generic
> /boot/vmlinuz-3.13.0-37-generic
> P: Checking for EXTLINUX directory... found.
> P: Writing config for /boot/vmlinuz-3.13.0-37-generic...
> P: Writing config for /boot/vmlinuz-3.13.0-36-generic...
> P: Writing config for /boot/vmlinuz-3.13.0-35-generic...
> P: Installing debian theme... done.
> run-parts: executing /etc/kernel/postrm.d/zz-update-grub
> 3.13.0-37-generic /boot/vmlinuz-3.13.0-37-generic
> Setting up linux-image-3.13.0-37-generic (3.13.0-37.64) ...
> Running depmod.
> Failed to run depmod
> dpkg: error processing package linux-image-3.13.0-37-generic
> (--configure): subprocess installed post-installation script returned
> error exit status 1 Errors were encountered while processing:
>   linux-image-3.13.0-37-generic
> E: Sub-process /usr/bin/dpkg returned an error code (1)
> A package failed to install.  Trying to recover:
> Setting up linux-image-3.13.0-37-generic (3.13.0-37.64) ...

Can we see the output of:
depmod --version
sudo updatedb; locate depmod

And finally, using the full path reported above:
ls -l /full/path/to/depmod

I also note that the kernel you are trying to install is a .64 kernel.  If 
that means a 64 bit kernel, and the system install is 32 bit it would not 
surprise me to see depmod get a tummy ache and bail out.

Cheers, Gene Heskett
-- 
"There are four boxes to be used in defense of liberty:
 soap, ballot, jury, and ammo. Please use in that order."
-Ed Howdershelt (Author)
Genes Web page <http://geneslinuxbox.net:6309/gene>
US V Castleman, SCOTUS, Mar 2014 is grounds for Impeaching SCOTUS