Ubuntu
debconf package

package debconf failed to install/upgrade: DbDriver "config": /var/cache/debconf/config.dat is locked by another process

Bug #281301 reported by Brian on 2008-10-10

This bug report is a duplicate of: Bug #349469: debconf: DbDriver "config": /var/cache/debconf/config.dat is locked by another process: Resource temporarily unavailable. Edit Remove

This bug affects 1 person

Affects		Status	Importance	Assigned to	Milestone
	debconf (Ubuntu)	Invalid	Undecided	Unassigned

Bug Description

Binary package hint: debconf

n/a

ProblemType: Package
Architecture: amd64
DistroRelease: Ubuntu 8.10
ErrorMessage: subprocess post-installation script returned error exit status 1
NonfreeKernelModules: nvidia
Package: debconf 1.5.23ubuntu2
PackageArchitecture: all
SourcePackage: debconf
Title: package debconf 1.5.23ubuntu2 failed to install/upgrade: subprocess post-installation script returned error exit status 1
Uname: Linux 2.6.27-6-generic x86_64

Tags:

Revision history for this message

Brian (bjc008) wrote on 2008-10-10:

Dependencies.txt Edit (317 bytes, text/plain; charset="utf-8")
DpkgTerminalLog.gz Edit (25.7 KiB, application/x-gzip)

Revision history for this message

Jean-Baptiste Lallement (jibel) wrote on 2008-10-20:

Thanks for your report. The error is:
=====
Setting up debconf (1.5.23ubuntu2) ...

debconf: DbDriver "config": /var/cache/debconf/config.dat is locked by another process: Resource temporarily unavailable

dpkg: error processing debconf (--configure):

subprocess post-installation script returned error exit status 1

=====

Revision history for this message

Jean-Baptiste Lallement (jibel) wrote on 2008-10-21:

If it's still an issue can you please provide the output of the following command:
fuser -v /var/cache/debconf/config.dat

Thanks.

Changed in debconf:
status:	New → Incomplete

Revision history for this message

Jean-Baptiste Lallement (jibel) wrote on 2008-11-15:

We are closing this bug report because it lacks the information we need to investigate the problem, as described in the previous comments. Please reopen it if you can give us the missing information, and don't hesitate to submit bug reports in the future. To reopen the bug report you can click on the current status, under the Status column, and change the Status back to "New". Thanks again!