update manager problem

Execute this command in teminal
sudo rm /var/lib/apt/lists/* -f

this is what came up when did that:

[sudo] password for roy:
rm: cannot remove `/var/lib/apt/lists/partial': Is a directory
roy@roy-MM061:~$

ok, try to update using Update manager now

i tried to update and got these errors:

roy@roy-MM061:~$ aptitude update
The program 'aptitude' can be found in the following packages:
 * aptitude
 * aptitude-gtk
Try: sudo apt-get install <selected package>
roy@roy-MM061:~$ apt-get update
E: Could not open lock file /var/lib/apt/lists/lock - open (13: Permission denied)
E: Unable to lock directory /var/lib/apt/lists/
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?

Use "sudo" :

sudo aptitude update

roy@roy-MM061:~$ sudo aptitude update
[sudo] password for roy:
sudo: aptitude: command not found
roy@roy-MM061:

sudo apt-get update

[This post refers to other posts by numbers. They are numbered at https://answers.launchpad.net/ubuntu/+source/update-manager/+question/167222.]

The error reported in post #2 was not actually a problem; that output was indicative of a successful run of the command given in post #1. So it's possible your problem has been solved since then. Maxim Petrov's instructions in post #3 were to try updating with the Update Manager.

If you want to update from the Terminal instead, you can run apt-get as root with sudo, or you can install aptitude (it's not installed by default) and run it as root with sudo. But if you are going to install aptitude from the command-line, you should update your local package information from the command-line first, which means you should run:

sudo apt-get update

That has the same effect as "sudo aptitude update" (it's only in upgrading, installation, and removal that aptitude sometimes makes different decisions from apt-get), but you cannot run "sudo aptitude update" successfully because you don't have aptitude installed.

Please note that it might not actually be necessary for you to run *anything* from the command-line, at this point. Your problem may have already been fixed. I recommend going into the Update Manager and seeing if the problem has gone away (or, if you have already done that, please let us know).

Thanks Sam_, that solved my question.