# “debconf: DbDriver ”config“: config.dat is locked by another process: Resource temporarily unavailable” while installing packages

I'm trying to install the flashybrid but when I enter the apt-get install flashybrid command, I get this error:

root@user-desktop:/home/user# apt-get install flashybrid
Building dependency tree
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
1 not fully installed or removed.
After this operation, 0B of additional disk space will be used.
debconf: DbDriver "config": /var/cache/debconf/config.dat is locked by another process: Resource temporarily unavailable
Setting up flashybrid (0.15+nmu2) ...
debconf: DbDriver "config": /var/cache/debconf/config.dat is locked by another process: Resource temporarily unavailable
dpkg: error processing flashybrid (--configure):
subprocess post-installation script returned error exit status 1
Errors were encountered while processing:
flashybrid
E: Sub-process /usr/bin/dpkg returned an error code (1)


I also tried this one to find what is already using that file:

root@user-desktop:/home/user# lsof | grep /var/cache/debconf/config.dat
lsof: WARNING: can't stat() fuse.gvfs-fuse-daemon file system /home/user/.gvfs
Output information may be incomplete.
dpkg-prec 4672 root 4rW REG 8,6 39658 1697827 /var/cache/debconf/config.dat


But I don't know how to fix this.

-

This is more simple one command

I just did

sudo rm /var/cache/debconf/*.dat


After i run the apt-get install and (i was installing curl ) and it worked restored the db manual pages

PS: i removed something with apt-get and i did have this probleme . but solved it simply thank also to @rajagenupula

-
I used sudo \rm -v /var/cache/debconf/*.dat – Mark Stewart Jan 27 '14 at 5:03
This worked sooo nice. Thanks! – Ionică Bizău Mar 6 '14 at 17:23
@lonica You're welcome :) – ucefkh Mar 7 '14 at 22:58
Don't do this... you can break your system. The correct answer is to use fuser and kill the process, as in Sayed's answer below. – Ryan P Oct 29 '15 at 18:30

A solution to this locking problem is detailed in the wiki:

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


Will show you what process is holding the lock:

                     USER        PID ACCESS COMMAND
/var/cache/debconf/config.dat:
root      18210 F.... dpkg-preconfigu


Then you simply need to note down the PID and kill it like so:

sudo kill PID
sudo kill -9 PID  # if the first doesn't work

-
This worked fantastic! Thanks a bunch, I didn't know of 'fuser'! – stolsvik Jan 1 '14 at 22:54
+1 for fuser command – pylover Sep 5 '14 at 0:01
fuser also has the option switch -k which kills the found process that uses the file: sudo fuser -v -k /var/cache/debconf/config.dat will kill the process right away – minni Dec 30 '15 at 9:30
2. open the location /var/cache/debconf with gksu nautilus
3. move (cut/paste) all of the .dat files to another backup directory.
4. attempt to run again (will likely get a different error)
5. restore those dat files from the aforementioned backup directory.
6. Then try again what you were doing (should work this time).
-
thanks a lot... – Dimitris7 May 17 '12 at 10:14
I had a similar problem and I just deleted all the files in the debconf folder. – Agmenor Jul 16 '12 at 22:25
i said there at point 3 . a file with password and with extension . ok now what you're getting . could you post them here by pastebin link . – Raja Jul 17 '12 at 13:07
same problem, I needed to remove all files in debconf folder – equivalent8 Nov 7 '12 at 12:11
I was getting really quite angry, saw your answer and suddenly there's progress. Thank you. – David Carboni Feb 1 '14 at 11:00
sudo fuser -vik /var/cache/debconf/config.dat


Will display the process and ask if you want to terminate it.

-

There is a process still running blocking debconf. You should wait until it finish. Or find out how it got stuck, since in some cases it will be try to ask you a question but since you don't have a scope to see it. If you wait sometime and things doesn't change you may need to reboot the system, or terminate the process.

sudo kill 4672


or

sudo killall dpkg-prec


This will assure you that your database will not get damaged and will prevent further problems.

-
I think it's pointless to use process id 4672 in your first command example. Somebody might use that command as-is, but it won't work as he would very likely have a different process id. – user205301 Nov 6 '13 at 16:56
@user205301 that's what the second is for ;) – Braiam Nov 6 '13 at 17:09