Not all changes and updates succeeded? Help!

[Hopkins132]

Basically, I get this error every time I try to update something, or install a package.
It is the first time I use Linux Mint 11 (and Linux in general).
Can anyone help?
Here is the error I get.

An error occurred
The following details are provided:

E: libpam0g: subprocess installed post-installation script returned error exit status 1
_____________________________________________________________________
Then I click ok and this pops up:

Update is complete
Not all changes and updates succeeded. For further details of the failuer, please expand the "Details" panel below.

debconf: DbDriver "config": /var/cache/debconf/config.dat is locked by another process: Resource temporarily unavailable
Setting up libpam0g (1.1.2-2ubuntu8.3) ...
debconf: DbDriver "config": /var/cache/debconf/config.dat is locked by another process: Resource temporarily unavailable
dpkg: error processing libpam0g (--configure):
subprocess installed post-installation script returned error exit status 1
Errors were encountered while processing:
libpam0g
E: Sub-process /usr/bin/dpkg returned an error code (1)
A package failed to install. Trying to recover:
Setting up man-db (2.5.9-4) ...
debconf: DbDriver "config": /var/cache/debconf/config.dat is locked by another process: Resource temporarily unavailable
dpkg: error processing man-db (--configure):
subprocess installed post-installation script returned error exit status 1
Setting up libpam0g (1.1.2-2ubuntu8.3) ...
debconf: DbDriver "config": /var/cache/debconf/config.dat is locked by another process: Resource temporarily unavailable
dpkg: error processing libpam0g (--configure):
subprocess installed post-installation script returned error exit status 1
Errors were encountered while processing:
man-db
libpam0g

[Roken]

in a terminal type

Code: Select all

fuser -v /var/cache/debconf/config.dat 

This should show you what process is locking the file. Then

Code: Select all

sudo killall process

Where process is the name of the process from the first step. If that completes successsfully, try the update again. If all goes well, I'd be tempted to reboot after the updates.

[Hopkins132]

Sorry if this sounds stupid...but...what is a terminal?

And will I have to do this for every update?

Thanks again.

[Roken]

If you go to the menu/accessories and select terminal it will open the terminal for you. It's a scary looking black box, but don't panic. Just type the commands as I've shown them. The second one will ask for your password which you should enter when prompted.

You shouldn't need to do it for every update, but if you post the output of the first command here we can offer a more qualified opinion.

[Hopkins132]

Lol...Linux is harder 2 use than it seemed...its so rainbows fast but its real hard 2 use...+ you cant find as much stuff as in windows...I might just go back and maybe use Linux in the future.

Oh btw, I opened the terminal but when I enter the first command it says:

Cannot stat file /proc/3387/fd/40: Stale NFS file handle
Cannot stat file /proc/3387/fd/41: Stale NFS file handle
Cannot stat file /proc/3387/fd/42: Stale NFS file handle
Cannot stat file /proc/3387/fd/43: Stale NFS file handle
Cannot stat file /proc/3387/fd/44: Stale NFS file handle
Cannot stat file /proc/3387/fd/46: Stale NFS file handle
Cannot stat file /proc/3387/fd/48: Stale NFS file handle
Cannot stat file /proc/3387/fd/49: Stale NFS file handle
Cannot stat file /proc/3782/fd/10: Stale NFS file handle
Cannot stat file /proc/3782/fd/12: Stale NFS file handle
Cannot stat file /proc/3782/fd/13: Stale NFS file handle

And its a scary white box too =( with a moose lol.

[Hopkins132]

bump

[Roken]

It looks as though something may have crashed. Go to the menu/System Tools/System Monitor which will open a window not unlike Windows task manager. There will be a column headed "Pid". Look down that column for each of 3387 and 3782. That will tell you what appears to be the problem programs. You can right click on them in the system monitor window and select "Kill" there. Once done, try your update again. In this case you shouldn't need the second command from my original reply.

As for it being hard, honestly it isn't, just different, and this little problem actually demonstrates one of the big advantages that Linux has over Windows, in that if a program or process misbehaves in Windows it can be extremely difficult to actually identify what is misbehaving in order to try to fix it. In Linux you can find it, fix it, and make sure that everything else is saved or updated (without bringing the whole system down) before you get to the inevitable reboot.

Give it a little more time. There are differences, but having been a Windows user for more years than I care to admit to, and a Linux "player", I now find myself disappointed when I have to boot Windows for something, simply because it feels so slow and clunky (and I really miss compiz ) Honestly, don't give up at the first hurdle.

[Hopkins132]

That didnt help it...

Anyway thanks, I might come back to Linux when I have a bit more time...

I find it hard because I find all computers hard lol

I really like Linux because as I said it is soooo much faster but I think Im going to stick with Windows for the time being...
Im going to be using Linux this week to test it out a bit more, maybe not worrying about the updates as they dont do anything.

What I dont like about Linux at the moment is that things are so much different...I found that many programs I had on Windows cant run on Linux.
Although there probably are substitutes, as I said, Im very "stupid" with computers and I cant imagine how long it would take me to figure it out.

Thanks again,
Hopkins132.

[Roken]

There are many sites listing alternatives to Windows programs. Here's one to get you started:

http://www.linuxscrew.com/2007/11/22/wi ... -software/

[jungle_boy]

Go to /var/cache/debconf/ open as administrator, and delet the locker (something.lock, or only lock), and try again update...

[jungle_boy]

look another answer posted by Roken;


New postby Roken on Mon Jun 13, 2011 9:53 am
in a terminal type

Code: Select all
fuser -v /var/cache/debconf/config.dat



This should show you what process is locking the file. Then

Code: Select all
sudo killall process



Where process is the name of the process from the first step. If that completes successsfully, try the update again. If all goes well, I'd be tempted to reboot after the updates.