Continued error message when trying to install updates

If you have no space then changing the command options will not help. Try emptying your trash to make more space on your system. Does that help?

Okay, I emptied the trash, and tried running the command again and received
the same response:
No space left on device.

On Mon, Jul 14, 2008 at 11:40 AM, Duncan Lithgow <
<email address hidden>> wrote:

> Your question #39194 on gnome-terminal in ubuntu changed:
>
> https://answers.edge.launchpad.net/ubuntu/+source/gnome-terminal/+question/39194
>
> Status: Open => Needs information
>
> Duncan Lithgow requested for more information:
> If you have no space then changing the command options will not help.
> Try emptying your trash to make more space on your system. Does that
> help?
>
> --
> To answer this request for more information, you can either reply to
> this email or enter your reply at the following page:
>
> https://answers.edge.launchpad.net/ubuntu/+source/gnome-terminal/+question/39194
>
> You received this question notification because you are a direct
> subscriber of the question.
>

It's your boot partition that's full.
When you installed did you specify a separate boot partition?
Please type the command :

# df -h

and report the results.
(Note that # represents the system prompt, just type the command following it).

okay, here are the results of that command:
Filesystem Size Used Avail Use% Mounted on
/dev/sda3 184G 4.8G 170G 3% /
varrun 236M 100K 236M 1% /var/run
varlock 236M 0 236M 0% /var/lock
udev 236M 48K 236M 1% /dev
devshm 236M 24K 236M 1% /dev/shm
lrm 236M 38M 199M 16%
/lib/modules/2.6.24-18-generic/volatile
/dev/sda1 92M 86M 1.4M 99% /boot
The system was installed for me, so I don't know if a separate boot
partition was specified for it.

On Tue, Jul 15, 2008 at 12:50 PM, Andy Ruddock <
<email address hidden>> wrote:

> Your question #39194 on gnome-terminal in ubuntu changed:
> https://answers.launchpad.net/ubuntu/+source/gnome-terminal/+question/39194
>
> Status: Open => Needs information
>
> Andy Ruddock requested for more information:
> It's your boot partition that's full.
> When you installed did you specify a separate boot partition?
> Please type the command :
>
> # df -h
>
> and report the results.
> (Note that # represents the system prompt, just type the command following
> it).
>
> --
> To answer this request for more information, you can either reply to
> this email or enter your reply at the following page:
> https://answers.launchpad.net/ubuntu/+source/gnome-terminal/+question/39194
>
> You received this question notification because you are a direct
> subscriber of the question.
>

As you can see from the last line /dev/sda1, which is your boot partition, is full.
You've probably got older versions of your kernel installed, can you report the results from the command :

# ls /boot

We'll probably be able to uninstall older kernels and free up some space.

Thanks for your help, I am following your instructions, so here are the
results from the command:
abi-2.6.20-15-generic initrd.img-2.6.24-16-generic.bak
abi-2.6.22-14-generic initrd.img-2.6.24-17-generic
abi-2.6.24-16-generic initrd.img-2.6.24-17-generic.bak
abi-2.6.24-17-generic initrd.img-2.6.24-18-generic
abi-2.6.24-18-generic lost+found
config-2.6.20-15-generic memtest86+.bin
config-2.6.22-14-generic System.map-2.6.20-15-generic
config-2.6.24-16-generic System.map-2.6.22-14-generic
config-2.6.24-17-generic System.map-2.6.24-16-generic
config-2.6.24-18-generic System.map-2.6.24-17-generic
grub System.map-2.6.24-18-generic
initrd.img-2.6.20-15-generic vmlinuz-2.6.20-15-generic
initrd.img-2.6.20-15-generic.bak vmlinuz-2.6.22-14-generic
initrd.img-2.6.22-14-generic vmlinuz-2.6.24-16-generic
initrd.img-2.6.22-14-generic.bak vmlinuz-2.6.24-17-generic
initrd.img-2.6.24-16-generic vmlinuz-2.6.24-18-generic

On Thu, Jul 17, 2008 at 9:33 AM, Andy Ruddock <
<email address hidden>> wrote:

> Your question #39194 on gnome-terminal in ubuntu changed:
> https://answers.launchpad.net/ubuntu/+source/gnome-terminal/+question/39194
>
> Status: Open => Needs information
>
> Andy Ruddock requested for more information:
> As you can see from the last line /dev/sda1, which is your boot partition,
> is full.
> You've probably got older versions of your kernel installed, can you report
> the results from the command :
>
> # ls /boot
>
> We'll probably be able to uninstall older kernels and free up some
> space.
>
> --
> To answer this request for more information, you can either reply to
> this email or enter your reply at the following page:
> https://answers.launchpad.net/ubuntu/+source/gnome-terminal/+question/39194
>
> You received this question notification because you are a direct
> subscriber of the question.
>

Ok, you've got previous versions of the kernel installed here.
In a terminal type :

# apt-get remove --purge linux-image-2.6.20-15-generic linux-image-2.6.22-14-generic

Then that'll remove the oldest two kernels you have installed. After that you should be able to upgrade.

When you're running the latest kernel you could also remove 2.6.24-16 and 2.6.24-17 to free up a little more space.

Okay, typed that command in and this is what I got:
E: Could not open lock file /var/lib/dpkg/lock - open (13 Permission denied)
E: Unable to lock the administration directory (/var/lib/dpkg/), are you
root?
maggie@maggie-desktop:~$ image-2.6.22-14-generic

On Thu, Jul 17, 2008 at 12:53 PM, Andy Ruddock <
<email address hidden>> wrote:

> Your question #39194 on gnome-terminal in ubuntu changed:
> https://answers.launchpad.net/ubuntu/+source/gnome-terminal/+question/39194
>
> Status: Open => Answered
>
> Andy Ruddock proposed the following answer:
> Ok, you've got previous versions of the kernel installed here.
> In a terminal type :
>
> # apt-get remove --purge linux-image-2.6.20-15-generic linux-
> image-2.6.22-14-generic
>
> Then that'll remove the oldest two kernels you have installed. After
> that you should be able to upgrade.
>
> When you're running the latest kernel you could also remove 2.6.24-16
> and 2.6.24-17 to free up a little more space.
>
> --
> If this answers your question, please go to the following page to let us
> know that it is solved:
>
> https://answers.launchpad.net/ubuntu/+source/gnome-terminal/+question/39194/+confirm?answer_id=6
>
> If you still need help, you can reply to this email or go to the
> following page to enter your feedback:
> https://answers.launchpad.net/ubuntu/+source/gnome-terminal/+question/39194
>
> You received this question notification because you are a direct
> subscriber of the question.
>

Try the command from Andy with "sudo" in front of it. It should give you enough priviledges to complete the task.

Tried that and got this response:
Reading package lists... Done
Building dependency tree
Reading state information... Done
Package linux-image-2.6.20-15-generic is not installed, so not removed
Package linux is not installed, so not removed
The following packages were automatically installed and are no longer
required:
  xserver-xorg-video-amd libdns32
Use 'apt-get autoremove' to remove them.
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
maggie@maggie-desktop:~$ image-2.6.22-14-generic

On Thu, Jul 17, 2008 at 3:04 PM, Hans Spaans <
<email address hidden>> wrote:

> Your question #39194 on gnome-terminal in ubuntu changed:
> https://answers.launchpad.net/ubuntu/+source/gnome-terminal/+question/39194
>
> Status: Open => Answered
>
> Hans Spaans proposed the following answer:
> Try the command from Andy with "sudo" in front of it. It should give you
> enough priviledges to complete the task.
>
> --
> If this answers your question, please go to the following page to let us
> know that it is solved:
>
> https://answers.launchpad.net/ubuntu/+source/gnome-terminal/+question/39194/+confirm?answer_id=8
>
> If you still need help, you can reply to this email or go to the
> following page to enter your feedback:
> https://answers.launchpad.net/ubuntu/+source/gnome-terminal/+question/39194
>
> You received this question notification because you are a direct
> subscriber of the question.
>

Please give the result of this command:

dpkg -l | grep -i linux-image

Thenk you

Result:
rc linux-image-2.6.20-15-generic
2.6.20-15.27 Linux kernel image for version 2.6.20 on
x86/x86_64
ii linux-image-2.6.20-16-generic
2.6.20-16.33 Linux kernel image for version 2.6.20 on
x86/x86_64
ii linux-image-2.6.22-14-generic
2.6.22-14.52 Linux kernel image for version 2.6.22 on
x86/x86_64
ii linux-image-2.6.24-16-generic
2.6.24-16.30 Linux kernel image for version 2.6.24 on
x86/x86_64
ii linux-image-2.6.24-19-generic
2.6.24-19.36 Linux kernel image for version 2.6.24 on
x86/x86_64
ii linux-image-generic
2.6.24.19.21 Generic Linux kernel image

On Thu, Jul 17, 2008 at 5:31 PM, marcobra <
<email address hidden>> wrote:

> Your question #39194 on gnome-terminal in ubuntu changed:
> https://answers.launchpad.net/ubuntu/+source/gnome-terminal/+question/39194
>
> Status: Open => Needs information
>
> marcobra requested for more information:
> Please give the result of this command:
>
> dpkg -l | grep -i linux-image
>
> Thenk you
>
> --
> To answer this request for more information, you can either reply to
> this email or enter your reply at the following page:
> https://answers.launchpad.net/ubuntu/+source/gnome-terminal/+question/39194
>
> You received this question notification because you are a direct
> subscriber of the question.
>

Please open a Terminal from the menu Applications->Accessories->Terminal and type:

sudo apt-get --purge remove linux-image-2.6.22-14-generic linux-ubuntu-modules-2.6.22-14-generic linux-headers-2.6.22-14-generic
sudo apt-get --purge remove linux-image-2.6.22-16-generic linux-ubuntu-modules-2.6.22-16-generic linux-headers-2.6.22-16-generic

sudo dpkg --configure -a

sudo apt-get -f install

sudo apt-get clean all

give your user password when requested, you don't see nothing when you type it, then press enter.

Hope this helps

Please also don't reply via mail to launchpad messages regarding this question. Try to open the mail message and try to visit the reported question link, is into the mail.
Please answer using the browser.

Thank you

Okay, put those commands in the terminal and I still get the result:
dpkg was interrupted, you must manually run 'dpkg --configure -a' to correct the problem. Do you need all the info that was put on the terminal?

The please run as first command:

sudo dpkg --configure -a

but i think you came into a poor space loop.

To discover your running kernel please give me the result of

uname -r

command.

Thank you

Try to temporary move to /dev/sda3 184G 4.8G 170G 3% /

some files that are into your /boot partition ( near to be full )

/dev/sda1 92M 86M 1.4M 99% /boot

can you copy and paste the result of:

ls -la /boot/

here.

Thank you

Thanks for your help. Here is the result of the command ls -la/boot/
k
-rw-r--r-- 1 root root 7287273 2008-02-28 14:13 initrd.img-2.6.22-14-generic
-rw-r--r-- 1 root root 7286938 2008-02-18 08:52 initrd.img-2.6.22-14-generic.bak
-rw-r--r-- 1 root root 7602897 2008-04-29 14:08 initrd.img-2.6.24-16-generic
-rw-r--r-- 1 root root 7602940 2008-04-29 13:43 initrd.img-2.6.24-16-generic.bak
-rw-r--r-- 1 root root 7603269 2008-05-26 18:29 initrd.img-2.6.24-17-generic
-rw-r--r-- 1 root root 7603332 2008-05-26 18:26 initrd.img-2.6.24-17-generic.bak
-rw-r--r-- 1 root root 7603427 2008-06-05 12:33 initrd.img-2.6.24-18-generic
drwx------ 2 root root 12288 2008-01-01 01:25 lost+found
-rw-r--r-- 1 root root 103204 2007-09-28 03:06 memtest86+.bin
-rw-r--r-- 1 root root 806942 2007-04-15 01:08 System.map-2.6.20-15-generic
-rw-r--r-- 1 root root 823535 2008-02-12 03:39 System.map-2.6.22-14-generic
-rw-r--r-- 1 root root 899892 2008-04-10 09:51 System.map-2.6.24-16-generic
-rw-r--r-- 1 root root 905012 2008-05-01 10:59 System.map-2.6.24-17-generic
-rw-r--r-- 1 root root 905012 2008-05-28 19:39 System.map-2.6.24-18-generic
-rw-r--r-- 1 root root 1745100 2007-04-15 01:07 vmlinuz-2.6.20-15-generic
-rw-r--r-- 1 root root 1764536 2008-02-12 03:39 vmlinuz-2.6.22-14-generic
-rw-r--r-- 1 root root 1904248 2008-04-10 09:51 vmlinuz-2.6.24-16-generic
-rw-r--r-- 1 root root 1921944 2008-05-01 10:59 vmlinuz-2.6.24-17-generic
-rw-r--r-- 1 root root 1921528 2008-05-28 19:39 vmlinuz-2.6.24-18-generic

This is the result for the command you also requested: uname -r
2.6.24-18-generic

So, we know you're currently using the 2.6.24-18-generic kernel (that last command told us that).
If we move some of the other files out of your boot partition then we'll be able to finish this dpkg command and move on.
So, please enter :

mkdir /tmp/boot_backup
sudo mv *14* /tmp/boot_backup

You should then be able to run :

sudo dpkg --configure -a

Then report back and, assuming that was successful, we'll go through making a bit more space on the boot partition so this doesn't happen again.

As a result of entering the 1st command, this is what reported:
 mkdir /tmp/boot_backup
mkdir: cannot create directory `/tmp/boot_backup': File exists
maggie@maggie-desktop:~$ sudo mv *14* /tmp/boot_backup
mv: cannot stat `*14*': No such file or directory

I'm sorry, that should be :

mkdir /tmp/boot.backup
sudo mv /boot/*14* /tmp/boot.backup/

Tried new command and the result was:
 mkdir /tmp/boot.backup
mkdir: cannot create directory `/tmp/boot.backup': File exists
maggie@maggie-desktop:~$ sudo mv /boot/*14* /tmp/boot.backup/
mv: cannot stat `/boot/*14*': No such file or directory

Can you report back the results from :

ls -la /tmp /boot

Results:
 ls -la /tmp /boot
/boot:
total 63936
drwxr-xr-x 4 root root 3072 2008-07-18 10:00 .
drwxr-xr-x 21 root root 4096 2008-07-18 08:36 ..
-rw-r--r-- 1 root root 414210 2007-04-15 01:07 abi-2.6.20-15-generic
-rw-r--r-- 1 root root 422607 2008-04-10 09:51 abi-2.6.24-16-generic
-rw-r--r-- 1 root root 422667 2008-05-01 10:59 abi-2.6.24-17-generic
-rw-r--r-- 1 root root 422667 2008-05-28 19:39 abi-2.6.24-18-generic
-rw-r--r-- 1 root root 83234 2007-04-14 22:33 config-2.6.20-15-generic
-rw-r--r-- 1 root root 79964 2008-04-10 09:51 config-2.6.24-16-generic
-rw-r--r-- 1 root root 80071 2008-05-01 10:59 config-2.6.24-17-generic
-rw-r--r-- 1 root root 80071 2008-05-28 19:39 config-2.6.24-18-generic
drwxr-xr-x 2 root root 1024 2008-06-05 12:34 grub
-rw-r--r-- 1 root root 7175008 2008-01-01 02:00 initrd.img-2.6.20-15-generic
-rw-r--r-- 1 root root 6842512 2007-04-15 04:56 initrd.img-2.6.20-15-generic.bak
-rw-r--r-- 1 root root 7602897 2008-04-29 14:08 initrd.img-2.6.24-16-generic
-rw-r--r-- 1 root root 7602940 2008-04-29 13:43 initrd.img-2.6.24-16-generic.bak
-rw-r--r-- 1 root root 7603269 2008-05-26 18:29 initrd.img-2.6.24-17-generic
-rw-r--r-- 1 root root 7603332 2008-05-26 18:26 initrd.img-2.6.24-17-generic.bak
-rw-r--r-- 1 root root 7603427 2008-06-05 12:33 initrd.img-2.6.24-18-generic
drwx------ 2 root root 12288 2008-01-01 01:25 lost+found
-rw-r--r-- 1 root root 103204 2007-09-28 03:06 memtest86+.bin
-rw-r--r-- 1 root root 806942 2007-04-15 01:08 System.map-2.6.20-15-generic
-rw-r--r-- 1 root root 899892 2008-04-10 09:51 System.map-2.6.24-16-generic
-rw-r--r-- 1 root root 905012 2008-05-01 10:59 System.map-2.6.24-17-generic
-rw-r--r-- 1 root root 905012 2008-05-28 19:39 System.map-2.6.24-18-generic
-rw-r--r-- 1 root root 1745100 2007-04-15 01:07 vmlinuz-2.6.20-15-generic
-rw-r--r-- 1 root root 1904248 2008-04-10 09:51 vmlinuz-2.6.24-16-generic
-rw-r--r-- 1 root root 1921944 2008-05-01 10:59 vmlinuz-2.6.24-17-generic
-rw-r--r-- 1 root root 1921528 2008-05-28 19:39 vmlinuz-2.6.24-18-generic

/tmp:
total 56
drwxrwxrwt 13 root root 4096 2008-07-18 11:38 .
drwxr-xr-x 21 root root 4096 2008-07-18 08:36 ..
drwx------ 2 maggie maggie 4096 2008-07-18 11:37 .esd-1000
drwx------ 2 maggie maggie 4096 2008-07-18 11:37 .exchange-maggie
drwx------ 3 maggie maggie 4096 2008-07-18 11:37 gconfd-maggie
drwxrwxrwt 2 root root 4096 2008-07-18 11:37 .ICE-unix
drwx------ 2 maggie maggie 4096 2008-07-18 11:37 keyring-SlU7ML
drwx------ 2 maggie maggie 4096 2008-07-18 11:41 orbit-maggie
drwx------ 2 maggie maggie 4096 2008-07-18 11:37 pulse-maggie
drwx------ 2 maggie maggie 4096 2008-07-18 11:37 seahorse-TssiEW
-rw------- 1 root root 0 2008-07-18 11:36 tmp.rRKrsP5223
drwx------ 3 maggie maggie 4096 2008-07-18 11:38 Tracker-maggie.5451
drwx------ 2 maggie maggie 4096 2008-07-18 11:37 virtual-maggie.IRWoZg
-r--r--r-- 1 root root 11 2008-07-18 11:36 .X0-lock
drwxrwxrwt 2 root root 4096 2008-07-18 11:36 .X11-unix

I'm confused as to why you're getting a "file exists" error when you try to create a directory under /tmp.
Looking at your /boot directory I'm tempted just to delete those .bak files without even trying to back them up - I'm almost 100% sure that they'll not be in use, just taking up space - it's what I'd do, but it's not my system.
I'd just do :

sudo rm /boot/*.bak

If you're not sure about doing this, wait a short while and see if anybody else jumps into this thread with a better idea.
You could just try copying them to your home directory first :

cp /boot/*.bak ~

Ran the command sudo rm /boot/*.bak , and I still get
 sudo rm /boot/*.bak
rm: cannot remove `/boot/*.bak': No such file or directory
Thanks for trying to help

This is confusing :
The output from "ls /boot" shows files ending with .bak

Have you rebooted since last we looked at this problem?

I have only put in the commands that you requested and left for this past weekend, so I turned off the computer.

Ok, what's the output from "ls /boot" now?

abi-2.6.20-15-generic initrd.img-2.6.24-18-generic
abi-2.6.24-16-generic lost+found
abi-2.6.24-17-generic memtest86+.bin
abi-2.6.24-18-generic System.map-2.6.20-15-generic
config-2.6.20-15-generic System.map-2.6.24-16-generic
config-2.6.24-16-generic System.map-2.6.24-17-generic
config-2.6.24-17-generic System.map-2.6.24-18-generic
config-2.6.24-18-generic vmlinuz-2.6.20-15-generic
grub vmlinuz-2.6.24-16-generic
initrd.img-2.6.20-15-generic vmlinuz-2.6.24-17-generic
initrd.img-2.6.24-16-generic vmlinuz-2.6.24-18-generic
initrd.img-2.6.24-17-generic

Those .bak files which we saw earlier have gone!

Try to "sudo dpkg --configure -a" again.

Results:
Setting up initramfs-tools (0.85eubuntu39.1) ...
update-initramfs: deferring update (trigger activated)

Setting up linux-ubuntu-modules-2.6.24-18-generic (2.6.24-18.26) ...
update-initramfs: Generating /boot/initrd.img-2.6.24-18-generic

Setting up linux-image-generic (2.6.24.18.20) ...
Setting up linux-generic (2.6.24.18.20) ...
Processing triggers for initramfs-tools ...
update-initramfs: Generating /boot/initrd.img-2.6.24-18-generic

Please also remove the related modules and headers

sudo apt-get remove --purge linux-modules-2.6.20-15-generic
sudo apt-get remove --purge linux-modules-2.6.24-16-generic
sudo apt-get remove --purge linux-modules-2.6.24-17-generic

sudo apt-get remove --purge linux-headers-2.6.20-15-generic
sudo apt-get remove --purge linux-headers-2.6.24-16-generic
sudo apt-get remove --purge linux-headers-2.6.24-17-generic

sudo apt-get update
sudo apt-get upgrade
sudo apt-get dist-upgrade
sudo apt-get clean all

Hope this helps

Thanks Andy Ruddock, that solved my question.

Thanks to all for your help and continued persistence. The system is completely updated and previous versions that were taking up space are removed.

Evening,, I've been trying to resolve a update manager issue,, fairly new to Ubuntu, maybe a year, I'm running 10.4 and of late, Id say the last 5 weeks when I go to use update manager I get a list of needed or proposed updates, so far so good,but when I try and actually download or "do the updating, it simply goes back to the update screen and shows me the same updates, nothing really updates. so I have been reading and using terminal to stay current however would really like a solution or a direction. to date I've changed (back and forth) my software source, main to, server for the US, then back again,, not sure how to actually check all the current repositories. I've also read and used this https://help.ubuntu.com/community/PackageManagerTroubleshootingProcedure. not sure if it resolved the issue,, Thank you fellas..
Pappy