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

Bug #349469 reported by chocka on 2009-03-27
This bug affects 657 people
Affects Status Importance Assigned to Milestone
Ambasa
New
Undecided
Unassigned
Debconf
New
Undecided
Unassigned
aptdaemon (Ubuntu)
Medium
Unassigned
debconf (Ubuntu)
Medium
Unassigned

Bug Description

Upgrading packages that use debconf sometimes fail with the following error:

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

chocka (chocka) wrote :
Till Kamppeter (till-kamppeter) wrote :

Looks like that all packages which use debconf are affected here. Perhaps apt or dpkg should check whether /var/cache/debconf/config.dat is locked before starting an update.

Setting up ufw (0.23.3) ...
debconf: DbDriver "config": /var/cache/debconf/config.dat is locked by another process: Resource temporarily unavailable
dpkg: error processing ufw (--configure):
 subprocess post-installation script returned error exit status 1
Setting up cups (1.3.9-2ubuntu8) ...
debconf: DbDriver "config": /var/cache/debconf/config.dat is locked by another process: Resource temporarily unavailable
dpkg: error processing cups (--configure):
 subprocess post-installation script returned error exit status 1

summary: - package cups 1.3.9-2ubuntu8 failed to install/upgrade: subprocess post-
- installation script returned error exit status 1
+ debconf: DbDriver "config": /var/cache/debconf/config.dat is locked by
+ another process: Resource temporarily unavailable
Colin Watson (cjwatson) wrote :

It would be entirely unhelpful if dpkg checked the debconf lock; you'd just get much the same failure slightly further up.

Maybe apt could check, but I think this might be more realistic for something that's intended to be much smarter, such as update-manager, so reassigning there. However, note that it is not actually possible to check this correctly outside debconf right now, as debconf does not necessarily use the same database in all installations. I recommend not fixing this in haste.

affects: dpkg (Ubuntu) → update-manager (Ubuntu)
Colin Watson (cjwatson) wrote :

Well, you might be able to check it by starting a debconf-communicate process and seeing whether it exits 1 or 127. (I'm not quite sure why it's 127 for "did nothing"; weird.)

Matt Zimmerman (mdz) on 2009-03-30
affects: update-manager (Ubuntu) → apt (Ubuntu)
Changed in apt (Ubuntu):
importance: Undecided → Medium
status: New → Triaged
Julian Mehnle (jmehnle) wrote :

As a resolution to the immediate lock problem, https://wiki.edubuntu.org/DebuggingInstallationIssues recommends using `fuser -v /var/cache/debconf/config.dat` to determine the process holding the lock and then killing it.

Thank you...

Julian Mehnle wrote:
> As a resolution to the immediate lock problem,
> https://wiki.edubuntu.org/DebuggingInstallationIssues recommends using
> `fuser -v /var/cache/debconf/config.dat` to determine the process
> holding the lock and then killing it.
>
>

Thank you, works great.

Gary

On Mon, Mar 8, 2010 at 7:24 AM, Kevin S
<email address hidden>wrote:

> Thank you...
>
> Julian Mehnle wrote:
> > As a resolution to the immediate lock problem,
> > https://wiki.edubuntu.org/DebuggingInstallationIssues recommends using
> > `fuser -v /var/cache/debconf/config.dat` to determine the process
> > holding the lock and then killing it.
> >
> >
>
> --
> debconf: DbDriver "config": /var/cache/debconf/config.dat is locked by
> another process: Resource temporarily unavailable
> https://bugs.launchpad.net/bugs/349469
> You received this bug notification because you are a direct subscriber
> of a duplicate bug.
>

affects: apt (Ubuntu) → debconf (Ubuntu)

I had the same problem:
This solved it for me:
sudo rm -rf /var/cache/debconf/*
sudo apt-get install -f

patpat (masottaus) wrote :

the same thing here on 8.04 tryng to run a humble debconf script...

the proposed solution didn't work , the file has no one locking it...
I've reinstalled debconf & debconf-utils... so far no luck...

Meng Jiao (meng1usa) wrote :

#8, Thomas's method fixed my problem

tags: added: iso-testing
Changed in debconf (Ubuntu):
assignee: nobody → Ubuntu Foundations Team (ubuntu-foundations-team)
Colin Watson (cjwatson) wrote :

I recommend against Thomas' method in comment #8. While it is technically a cache, removing it removes all saved answers to debconf questions, and you'll have to answer them all again on future upgrades!

Simply rebooting, while inelegant, would be much less destructive.

Thanks, Colin...I'll give it a go

cheers

kate

On 22 June 2011 10:43, Colin Watson <email address hidden> wrote:
> I recommend against Thomas' method in comment #8.  While it is
> technically a cache, removing it removes all saved answers to debconf
> questions, and you'll have to answer them all again on future upgrades!
>
> Simply rebooting, while inelegant, would be much less destructive.
>
> --
> You received this bug notification because you are subscribed to a
> duplicate bug report (719784).
> https://bugs.launchpad.net/bugs/349469
>
> Title:
>  debconf: DbDriver "config": /var/cache/debconf/config.dat is locked by
>  another process: Resource temporarily unavailable
>
> Status in “debconf” package in Ubuntu:
>  Triaged
>
> Bug description:
>  Binary package hint: cups
>
>  Crash detection report attached.
>
>  ProblemType: Package
>  Architecture: i386
>  DistroRelease: Ubuntu 8.10
>  ErrorMessage: subprocess post-installation script returned error exit status 1
>  NonfreeKernelModules: nvidia
>  Package: cups 1.3.9-2ubuntu8
>  SourcePackage: cups
>  Title: package cups 1.3.9-2ubuntu8 failed to install/upgrade: subprocess post-installation script returned error exit status 1
>  Uname: Linux 2.6.27-11-generic i686
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/ubuntu/+source/debconf/+bug/349469/+subscriptions
>

--
make tea...not war

Il 22/06/2011 19:43, Colin Watson ha scritto:
> I recommend against Thomas' method in comment #8. While it is
> technically a cache, removing it removes all saved answers to debconf
> questions, and you'll have to answer them all again on future upgrades!
>
> Simply rebooting, while inelegant, would be much less destructive.
>
>
thanx so much!!
I love my linux!!!

gianlu, Italy

tags: added: debconf-config-locked

Thanks!!!! Very very thanks too xD

2011/6/23, Brian Murray <email address hidden>:
> ** Tags added: debconf-config-locked
>
> --
> You received this bug notification because you are subscribed to a
> duplicate bug report (545106).
> https://bugs.launchpad.net/bugs/349469
>
> Title:
> debconf: DbDriver "config": /var/cache/debconf/config.dat is locked by
> another process: Resource temporarily unavailable
>
> Status in “debconf” package in Ubuntu:
> Triaged
>
> Bug description:
> Binary package hint: cups
>
> Crash detection report attached.
>
> ProblemType: Package
> Architecture: i386
> DistroRelease: Ubuntu 8.10
> ErrorMessage: subprocess post-installation script returned error exit
> status 1
> NonfreeKernelModules: nvidia
> Package: cups 1.3.9-2ubuntu8
> SourcePackage: cups
> Title: package cups 1.3.9-2ubuntu8 failed to install/upgrade: subprocess
> post-installation script returned error exit status 1
> Uname: Linux 2.6.27-11-generic i686
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/ubuntu/+source/debconf/+bug/349469/+subscriptions
>

--
Atte. Mia

dan hawk (yellowbronco) wrote :

i tried reboot and went back to the begining , didnt fix it

the problem for me appeared to be that software center was open while installing using the command line apt-get... but I'm not sure it was really related. I closed it and removed/installed the package again and it worked.

Colin Watson (cjwatson) wrote :

On Thu, Jul 28, 2011 at 03:41:52PM -0000, Leonardo Santagada @ Proge.com.br wrote:
> the problem for me appeared to be that software center was open while
> installing using the command line apt-get... but I'm not sure it was
> really related.

This is indeed a classic reason for getting this kind of error. You can
only use one package management program at a time.

Steve Langasek (vorlon) wrote :

On Thu, Jul 28, 2011 at 04:09:35PM -0000, Colin Watson wrote:
> On Thu, Jul 28, 2011 at 03:41:52PM -0000, Leonardo Santagada @ Proge.com.br wrote:
> > the problem for me appeared to be that software center was open while
> > installing using the command line apt-get... but I'm not sure it was
> > really related.

> This is indeed a classic reason for getting this kind of error. You can
> only use one package management program at a time.

Isn't it a bit strange to hit a debconf error in that case, however? You
should run into locking problems with either apt or dpkg well before debconf
is involved.

--
Steve Langasek Give me a lever long enough and a Free OS
Debian Developer to set it on, and I can move the world.
Ubuntu Developer http://www.debian.org/
<email address hidden> <email address hidden>

Erick Brunzell (lbsolost) wrote :

I got this just after quitting a live install of an Lubuntu Oneiric Beta 2 "candidate" to collect some bug info, including screenshots.

Since Lubuntu has no screenshot tool installed by default I had used synaptic to install the xfce screenshot tool.

I'm posting this mostly so I can follow up on it myself.

No major worries, but I wish we could roll back to a sane ubiquity ....... circa Lucid ;^)

Tongue. In. Cheek.

Just smile.

tags: added: rls-mgr-p-tracking

I got this in an update with Oneiric Beta today.

a cursory review of the existing commentary here leads me reconsider my speculation over the source of this issue, as manifest on /my/ system. Please indulge my narrative concerning the unusual approach to package-management I whimsically employed with this Lubuntu flavour of Ubuntu "Natty" (11.04?).

Over the past 10 - 14 months or so, I've installed at least a handful of different Linux distributions on as many HDD's (embarking upon something new with each instance of Win XP / .NET incompatibility surfacing, as essentially renders the MS sys in a /broken/ state), from classic GNOME-based Ubuntu, Xubuntu, to OpenSUSE including a full-blown KDE setup, to my current favourite, the LXDE-based "Lubuntu" variant of the 'buntu.

Somewhere along the line, i discovered the Pandora's Box of pkg mgt in the application known as (cover your ears, kids!) /Eveinstaller/. Once I started down that path, I threw caution to the wind and pulled out all the stops just to see if this software could actually perform as well as it presents a veritable plethora of software not likely to be found via default Canonical + Partner repos (e.g. deb http://archive.ubuntu.com/ubuntu natty main restricted universe multiverse). If I had to summarize it into one sentence, I'm inclined to phrase the experience as "Eve___ basically wrecked my sources, if not the entire dpkg functionality, such that-- I'd have to have paid much closer attention to the changes to /etc/apt/sources.list.d/ (vs those repos i might have added, for example, the Banshee media player, launchpad repos , or other software repos added through the convenient PPA method (e.g. sudo add-apt-repository ppa:user/ppa-name ).

The bottom-line, as far as I'm concerned: I realise I've damaged my system's /default/ package manager configuration. The fact that I've experienced this error-- well-- I guess you could say, I'm not surprised; i've been expecting it.

If my anecdote lends insight to anyone; should the reader wish to learn more about the results of the effect of EveInstaller on my system, I'm happy to provide whatever information I can to assist in your own learning; debugging; etc.

I apologise for my verbosity; indeed, i've come to acknowledge the degenerative mentals and, proportionally-- as the community participation history might corroborate-- i hold my tongue by an increasingly exponential factor of instances of contribution (I regret, as my enthusiasm for the spirit of community at Launchpad in general; 'buntu in particular, has not waned in balance).

best regards,
NoviceNotes.Net (the author)

Steve Langasek (vorlon) on 2011-10-26
tags: added: rls-p-tracking
Steve Langasek (vorlon) on 2011-10-28
description: updated
ebvigmo (erik-vigmostad) wrote :

No output...

On 10/28/2011 12:53 PM, Steve Langasek wrote:
> ** Description changed:
>
> + If you have encountered this bug, please run:
> +
> + sudo fuser /var/cache/debconf/config.dat
> +
> + for each of the shown process IDs, please run:
> +
> + pstree -s $pid
> +
> + and report the output to this bug.
> +
> Binary package hint: cups
>
> Crash detection report attached.
>
> ProblemType: Package
> Architecture: i386
> DistroRelease: Ubuntu 8.10
> ErrorMessage: subprocess post-installation script returned error exit status 1
> NonfreeKernelModules: nvidia
> Package: cups 1.3.9-2ubuntu8
> SourcePackage: cups
> Title: package cups 1.3.9-2ubuntu8 failed to install/upgrade: subprocess post-installation script returned error exit status 1
> Uname: Linux 2.6.27-11-generic i686
>

Wow...

I got this from oneric amd64 live installer environment. ...

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

I am running UBUNTU 11.10

My machine is HP Compaq Presario V3239TU and has nothing to do with AMD

I get the error in crossplatformui.

I may please be dropped from this bug list.

Steve Langasek (vorlon) wrote :

On Fri, Nov 04, 2011 at 04:15:16AM -0000, Satyapriyananda wrote:
> My machine is HP Compaq Presario V3239TU and has nothing to do with AMD

> I get the error in crossplatformui.

What is crossplatformui?

> I may please be dropped from this bug list.

You would need to drop yourself using the launchpad web interface.

--
Steve Langasek Give me a lever long enough and a Free OS
Debian Developer to set it on, and I can move the world.
Ubuntu Developer http://www.debian.org/
<email address hidden> <email address hidden>

hayig2000 (hayig2000) wrote :

i got this error upon failure to update grub, so frontend process kept open

Dan Devor (ddevor) wrote :

On 11/06/2011 03:02 PM, hayig2000 wrote:
> i got this error upon failure to update grub, so frontend process kept
> open
>
[Bug 349469] Re: debconf: DbDriver "config":
/var/cache/debconf/config.dat is locked by another process: Resource
temporarily unavailable

Please remove my name from the distribution list for this problem. I get
far to many messages unrelated to my bug report.

Brad M (mannrb) wrote :
Download full text (3.6 KiB)

I cannot get WINE1.3 to uninstall, Software Center and Synaptic Pkg Manager have become completely useless until I get around this :

debconf: DbDriver "config": /var/cache/debconf/config.dat is locked by another process: Resource temporarily unavailable
dpkg: error while cleaning up:
 subprocess new post-removal script returned error exit status 1
Processing triggers for desktop-file-utils ...
Processing triggers for gnome-menus ...
Processing triggers for bamfdaemon ...
Rebuilding /usr/share/applications/bamf.index...
Processing triggers for hicolor-icon-theme ...
Errors were encountered while processing:
 /var/cache/apt/archives/wine1.3_1.3.36-0ubuntu1~ppa1~oneiric1_i386.deb
E: Sub-process /usr/bin/dpkg returned an error code (1)

pstree -s $pid
init─┬─/usr/bin/termin─┬─/usr/bin/termin
     │ ├─bash───pstree
     │ └─3*[{/usr/bin/termi}]
     ├─NetworkManager─┬─dhclient
     │ └─2*[{NetworkManager}]
     ├─accounts-daemon───{accounts-daemo}
     ├─acpid
     ├─apache2─┬─apache2
     │ └─2*[apache2───26*[{apache2}]]
     ├─aptd
     ├─atd
     ├─avahi-daemon───avahi-daemon
     ├─bluetoothd
     ├─colord───2*[{colord}]
     ├─console-kit-dae───64*[{console-kit-da}]
     ├─cron
     ├─cupsd
     ├─2*[dbus-daemon]
     ├─dbus-launch
     ├─dconf-service───2*[{dconf-service}]
     ├─dpkg───frontend─┬─preinst
     │ └─whiptail
     ├─firefox─┬─plugin-containe───9*[{plugin-contain}]
     │ └─25*[{firefox}]
     ├─gconfd-2
     ├─6*[getty]
     ├─gnome-keyring-d───4*[{gnome-keyring-}]
     ├─gsd-printer───{gsd-printer}
     ├─gvfs-afc-volume───{gvfs-afc-volum}
     ├─gvfs-fuse-daemo───3*[{gvfs-fuse-daem}]
     ├─gvfs-gdu-volume
     ├─gvfs-gphoto2-vo
     ├─gvfsd
     ├─gvfsd-burn
     ├─gvfsd-http───2*[{gvfsd-http}]
     ├─gvfsd-metadata
     ├─gvfsd-trash
     ├─irqbalance
     ├─lightdm─┬─Xorg
     │ ├─gnome-session─┬─applet.py
     │ │ ├─bluetooth-apple───{bluetooth-appl}
     │ │ ├─deja-dup-monito───2*[{deja-dup-monit}]
     │ │ ├─gdu-notificatio
     │ │ ├─gnome-fallback-───2*[{gnome-fallback}]
     │ │ ├─gnome-panel───2*[{gnome-panel}]
     │ │ ├─gnome-settings-───2*[{gnome-settings}]
     │ │ ├─gnome-sound-app───{gnome-sound-ap}
     │ │ ├─metacity───2*[{metacity}]
     │ │ ├─nautilus───2*[{nautilus}]
     │ │ ├─nm-applet───{nm-applet}
     │ │ ├─polkit-gnome-au───2*[{polkit-gnome-a}]
     │ │ ├─ssh-agent
     │ │ ├─telepathy-indic───{telepathy-indi}
     │ │ ├─update-notifier───3*[{update-notifie}]
     │ │ ├─zeitgeist-datah───{zeitgeist-data}
     │ │ └─3*[{gnome-session}]
     │ └─2*[{lightdm}]
     ├─mission-control
     ├─modem-manager
     ├─notify-osd───2*[{notify-osd}]
     ├─oneconf-service───2*[{oneconf-servic}]
     ├─polkitd───{polkitd}
     ├─pulseaudio─┬─gconf-helper
     │ ...

Read more...

Steve Langasek (vorlon) wrote :

Brad, your pstree output shows an orphaned dpkg process:

     ├─dpkg───frontend─┬─preinst
     │ └─whiptail

Do you know how this process was launched? Did you run apt-get or dpkg from a terminal and then close the terminal?

Thomas Hood (jdthood) wrote :

* In one of the dupes (#380491) the submitter says that running tasksel (not as root) simultaneously with "dpkg --configure --pending" (as root) results in the error message.

* In #419100 the submitter suggests that update-manager is conflicting with itself when spawned in "Automatic update / Install security updates without confirmation" mode.

* In #482523 the submitter says that the installer was also running.

* I am able to trigger the message ("debconf: DbDriver "config": /var/cache/debconf/config.dat is locked by another process: Resource temporarily unavailable") by doing the following:

    while : ; do dpkg-reconfigure -pcritical <package-that-calls-debconf> ; done & update-manager # Then agree to Install Updates

#434286 also mentions use of dpkg-reconfigure.

(So far I have read the dupes up through the six hundred thousands.)

I agree with Steve Langasek who wrote in #18, "You should run into locking problems with either apt or dpkg well before debconf
is involved." Not only in the sense "I'd expect..." but in the sense "It would be better if...": the error messages printed by apt and dpkg are likely to give the user a better idea of what is going wrong (namely, that two processes are trying to carry out package management actions at the same time) than debconf's low-level "/var/cache/debconf/config.dat is locked by another process".

Can this+dupes therefore be considered bugs in dpkg-reconfigure, tasksel and other programs not taking the right locks?

Steve Langasek (vorlon) wrote :

dpkg-reconfigure in fact does not invoke either apt or dpkg, so it's normal that it doesn't take the locks. I think it would be very strange if either dpkg-reconfigure or tasksel accounted for the very many reports of this bug however, as both interfaces are very low-level and I would expect at least one of the bug submitters before now to have mentioned they were running such a command if so.

I think the duplicate bug count/frequency is a sign that something is going wrong and invoking debconf on behalf of the user *without* being initiated from the commandline.

I think I also have to say that, if this really comes down to dpkg-reconfigure or tasksel, rather than having these tools claim apt or dpkg locks directly, we should probably regard the failure as user error and arrange to suppress the error reporting.

Scott Kitterman (kitterman) wrote :

Where I've seen this sort of thing (and I'm sure it's buried in the dupes) is on postfix package installs. Perhaps it would be worth while to examine it's use of debconf and see if it's doing anything troubling/likely to cause such problems. That might lead to a hint for the more general case.

Thomas Hood (jdthood) wrote :

There is no shortage of duplicates of this report. I am inclined to guess that in many cases faulty package scripts are leaving processes around which fail to release the config.dat lock under some circumstances.

In order to test this hypothesis I'd like to go back in time and in each of the 400-odd cases find the rogue process and then figure out why it's running on the user's system. Obviously that's impossible. But perhaps we will have chances to do this in the future.

I certainly don't think that the *majority* of cases has arisen from a package management command being run from a terminal while another package management process runs. I was just asking in #30 whether or not there are higher-level locks that should be taken by such commands, resulting in earlier and more useful error messages. It seems not. In that case I'd say that for now the error message ("debconf: DbDriver "config": /var/cache/debconf/config.dat is locked by another process: Resource temporarily unavailable") should be extended to give some advice about how to fix the problem... and possibly also to ask for information to be contributed here.

Clint Byrum (clint-fewbar) wrote :

Excerpts from Thomas Hood's message of Wed Mar 21 21:12:53 UTC 2012:
> There is no shortage of duplicates of this report. I am inclined to
> guess that in many cases faulty package scripts are leaving processes
> around which fail to release the config.dat lock under some
> circumstances.
>
> In order to test this hypothesis I'd like to go back in time and in each
> of the 400-odd cases find the rogue process and then figure out why it's
> running on the user's system. Obviously that's impossible. But perhaps
> we will have chances to do this in the future.
>
> I certainly don't think that the *majority* of cases has arisen from a
> package management command being run from a terminal while another
> package management process runs. I was just asking in #30 whether or
> not there are higher-level locks that should be taken by such commands,
> resulting in earlier and more useful error messages. It seems not. In
> that case I'd say that for now the error message ("debconf: DbDriver
> "config": /var/cache/debconf/config.dat is locked by another process:
> Resource temporarily unavailable") should be extended to give some
> advice about how to fix the problem... and possibly also to ask for
> information to be contributed here.
>

Perhaps an apport bug pattern could be written which would look for what
processes are holding the locks?

Pierre Greiner (mailpiegr) wrote :

init───aptd───aptd───sh───dpkg-preconfigu─┬─dpkg-preconfigu
                                          └─matlab-support.

Thomas Hood (jdthood) wrote :

Can you please describe the circumstances under which you obtained that pstree?

Michał Borsuk (michal-borsuk) wrote :

On 27.04.2012 11:36, Thomas Hood wrote:
> Can you please describe the circumstances under which you obtained that
> pstree?
>
Hi. Sorry, after the transition to Unity I no longer consider Ubuntu a
work-stable system, therefore I have no business to help you, especially
because the transition to another system cost me a lot of time.

--
Best regards, mit freundlichen Grüssen, meilleurs sentiments, Pozdrowienia,

Michał Borsuk

I am sorry but I do not remember that anymore.
Got the problem while trying to install Ubuntu on a Lenovo laptop, but for
other reasons had to switch to Win 7.

Regards,

From: Thomas Hood <email address hidden>
To: Emile Wintraeken/Netherlands/Contr/IBM@IBMNL
Date: 27-04-12 11:46
Subject: [Bug 349469] Re: debconf: DbDriver "config":
/var/cache/debconf/config.dat is locked by another process: Resource
temporarily unavailable
Sent by: <email address hidden>

Can you please describe the circumstances under which you obtained that
pstree?

--
You received this bug notification because you are subscribed to a
duplicate bug report (663863).
https://bugs.launchpad.net/bugs/349469

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

Status in ?debconf? package in Ubuntu:
  Triaged

Bug description:
  If you have encountered this bug, please run:

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

  for each of the shown process IDs, please run:

    pstree -s $pid

  and report the output to this bug.

  Binary package hint: cups

  Crash detection report attached.

  ProblemType: Package
  Architecture: i386
  DistroRelease: Ubuntu 8.10
  ErrorMessage: subprocess post-installation script returned error exit
status 1
  NonfreeKernelModules: nvidia
  Package: cups 1.3.9-2ubuntu8
  SourcePackage: cups
  Title: package cups 1.3.9-2ubuntu8 failed to install/upgrade: subprocess
post-installation script returned error exit status 1
  Uname: Linux 2.6.27-11-generic i686

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/debconf/+bug/349469/+subscriptions

Tenzij hierboven anders aangegeven: / Unless stated otherwise above:
IBM Nederland B.V.
Gevestigd te Amsterdam
Inschrijving Handelsregister Amsterdam Nr. 33054214

El 27/04/12 06:50, Michał Borsuk escribió:
> On 27.04.2012 11:36, Thomas Hood wrote:
>> Can you please describe the circumstances under which you obtained that
>> pstree?
>>
> Hi. Sorry, after the transition to Unity I no longer consider Ubuntu a
> work-stable system, therefore I have no business to help you, especially
> because the transition to another system cost me a lot of time.
>
that was a long time ago... sorry I do not remember...

minhdai (tranminhdai13) wrote :

update-alternatives: using /usr/bin/lupdate-qt4 to provide /usr/bin/lupdate (lupdate) in auto mode.
update-alternatives: using /usr/bin/lrelease-qt4 to provide /usr/bin/lrelease (lrelease) in auto mode.
Setting up qt4-qmake (4:4.8.1-0ubuntu4.1) ...
update-alternatives: using /usr/bin/qmake-qt4 to provide /usr/bin/qmake (qmake) in auto mode.
Setting up libqt4-dev (4:4.8.1-0ubuntu4.1) ...
update-alternatives: using /usr/bin/moc-qt4 to provide /usr/bin/moc (moc) in auto mode.
update-alternatives: using /usr/bin/uic-qt4 to provide /usr/bin/uic (uic) in auto mode.
update-alternatives: warning: skip creation of /usr/share/man/man1/uic.1.gz because associated file /usr/share/man/man1/uic-qt4.1.gz (of link group uic) doesn't exist.
Setting up phonon-backend-null (4:4.7.0really4.6.0-0ubuntu1) ...
debconf: DbDriver "config": /var/cache/debconf/config.dat is locked by another process: Resource temporarily unavailable
dpkg: error processing phonon-backend-null (--configure):
 subprocess installed post-installation script returned error exit status 1
dpkg: dependency problems prevent configuration of libphonon-dev:
 libphonon-dev depends on phonon-backend-null | phonon; however:
  Package phonon-backend-null is not configured yet.
  Package phonon is not installed.
dpkg: error processing libphonon-dev (--configure):
 dependency problems - leaving unconfigured
Setting up libqt4-opengl-dev (4:4.8.1-0ubuntu4.1) ...
No apport report written because the error message indicates its a followup error from a previous failure.
                          Setting up libqtwebkit-dev (2.2.1-1ubuntu4) ...
Setting up libx11-doc (2:1.4.99.1-0ubuntu2) ...
Setting up libxi-dev (2:1.6.0-0ubuntu2) ...
Setting up x11proto-record-dev (1.14.1-2) ...
Setting up libxtst-dev (2:1.2.0-4) ...
Processing triggers for libc-bin ...
ldconfig deferred processing now taking place
>>>>>>>>>>>>>>>>>>>Errors were encountered while processing:
>>>>>>>>>>>>>>>>>>> man-db
>>>>>>>>>>>>>>>>>>>phonon-backend-null
>>>>>>>>>>>>>>>>>>> libphonon-dev
>>>>>>>>>>>>>>>>>>>E: Sub-process /usr/bin/dpkg returned an error code (1)

what is the error and how to fix it? Please help! :(

tags: added: precise
Steve Langasek (vorlon) on 2012-05-30
Changed in aptdaemon (Ubuntu):
importance: Undecided → Medium
Changed in aptdaemon (Ubuntu):
status: New → Confirmed
description: updated
Changed in aptdaemon (Ubuntu):
assignee: nobody → abdelilah (abdelilah51992)
Karma Dorje (taaroa) on 2012-11-27
Changed in aptdaemon (Ubuntu):
assignee: abdelilah (abdelilah51992) → nobody
description: updated
45 comments hidden view all 125 comments
taoma (1585641394-n) wrote :

I solve the problem by Thomas Zahreddin (thomas-zahreddin) way! very thanks!
I am chinese new hand to study ubuntu,welcome to communication!

2 comments hidden view all 125 comments
徐梦阳 (chxumengyang) wrote :

affected today ,by install and reinstall apache~

6 comments hidden view all 125 comments
codeslinger (codeslinger) wrote :

I just hit this bug while installing 12.04 from a flashdrive

basically it was a simple case of user error, however it is also a program error too, because it is not effective for a program to crash as a means to tell the user that they did something wrong.

if a program has a choice between crashing or checking to see if a file is locked, then it should certainly do the check... this allows the program to exit gracefully and clean-up and most especially it allows for proper informational notices. The alternative is that the user is left perplexed, the bug database gets flooded, and users are forced to reboot because of a simple error....

Steps to Repro (this is only one of many possible scenarios)

1) Start the Installer (ubiquity)

2) While on the "Welcome" choose language screen, open a terminal

3) sudo apt-get install lm-sensors (or any other not currently installed program)

result: crash

expected: error message telling me the resource is locked

note: after quiting the installer... find that system is in unusable state and must reboot

someone needs to give that program a dose of Ubuntu Community Spirit :-)

Mike Miller (akf-mike-nw2) wrote :

Wow, this has been around for quite sometime and to still be affecting an LTS release is interesting. Bump +1 happened when I was trying to install gnome-system-tools and most of the packs recommended by apt to go along with it and got this error several times during installation and application of changes after downloads.

Txopi (txopi) wrote :

Like #16 I executed an apt-get install while software-center was running. That seems to be the cause of the crash.

Ibra_dee (deemas-666) on 2013-06-28
Changed in aptdaemon (Ubuntu):
assignee: nobody → Ibra_dee (deemas-666)
Arv Evans (arvid-evans) wrote :

I was installing ssmtp in Ubuntu 12.04
no other apt-gets or software center or synaptic was running at the time.

SYSTEM: AMD 2X64-3800 with 4GB RAM and 1TB HD. Ubuntu 12.04 is up to date.

Arv Evans (arvid-evans) wrote :

While installing ssmtp...seems to point to a broken install of exim4 or exim4-config.
dpkg was messed up and required "apt-get install -f" to fix.

Jennifer (heck-jennifer) on 2013-11-24
Changed in aptdaemon (Ubuntu):
assignee: Ibra_dee (deemas-666) → Jennifer (heck-jennifer)
Changed in debconf (Ubuntu):
assignee: Ubuntu Foundations Team (ubuntu-foundations-team) → nobody
Changed in aptdaemon (Ubuntu):
status: Confirmed → Fix Released
Steve Langasek (vorlon) on 2013-11-29
Changed in aptdaemon (Ubuntu):
assignee: Jennifer (heck-jennifer) → nobody
Steve Langasek (vorlon) on 2013-11-29
Changed in aptdaemon (Ubuntu):
status: Fix Released → Confirmed

thanks to all the comment. actually, what i'm doing is, i format the PC
again. n I can use it

On Sat, Nov 30, 2013 at 7:17 AM, Steve Langasek <
<email address hidden>> wrote:

> ** Changed in: aptdaemon (Ubuntu)
> Status: Fix Released => Confirmed
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/349469
>
> Title:
> debconf: DbDriver "config": /var/cache/debconf/config.dat is locked by
> another process: Resource temporarily unavailable
>
> Status in Ambasa Operating System:
> New
> Status in Debconf:
> New
> Status in “aptdaemon” package in Ubuntu:
> Confirmed
> Status in “debconf” package in Ubuntu:
> Triaged
>
> Bug description:
> Upgrading packages that use debconf sometimes fail with the following
> error:
>
> debconf: DbDriver "config": /var/cache/debconf/config.dat is locked by
> another process: Resource temporarily unavailable
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/ambasa/+bug/349469/+subscriptions
>

--
'the more u give, the more that u get''

Nur Sabrina Binti Risman
Biochip and Medical SoC Laboratory,
Faculty of Biosciences and Medical Engineering,
Universiti Teknologi Malaysia.
Tel : 013 791 4623

LinkedIn
------------

Bug,

I'd like to add you to my professional network on LinkedIn.

- Kate

Kate Dyson
CEO at Poe and Stell's Dag Biscuits
British Columbia, Canada

Confirm that you know Kate Dyson:
https://www.linkedin.com/e/-iagsrj-hp5xp4xu-5v/isd/18675747669/AtTp8LgC/?hs=false&tok=2I69kUJC1WKm01

--
You are receiving Invitation to Connect emails. Click to unsubscribe:
http://www.linkedin.com/e/-iagsrj-hp5xp4xu-5v/qN7mur3mdZqLfU8msuzwOfWmBa82Nfnz-KUbBMQ/goo/349469%40bugs%2Elaunchpad%2Enet/20061/I6091572473_1/?hs=false&tok=3dO3-F_hRWKm01

(c) 2012 LinkedIn Corporation. 2029 Stierlin Ct, Mountain View, CA 94043, USA.

drink (martin-espinoza) wrote :

extlinux install hung so I killed dpkg. fuser -v /var/cache/debconf/config.dat returns nothing. but I'm still getting this error.

denise (denise-gies) on 2014-04-19
Changed in aptdaemon (Ubuntu):
assignee: nobody → denise (denise-gies)
Changed in aptdaemon (Ubuntu):
status: Confirmed → Triaged
David Roberts (david.roberts) wrote :

I hit this issue during a 12.04 to 14.04 distribution upgrade. SInce it forces package installation to continue even when it encounters errors, I was left with a decent chunk of the system unconfigured (which I had to fix manually afterwards).

I think I found something else that might be slightly related. I first came across this error when I was removing some packages remotely via ssh. There seems to be a problem with man-db. See the terminal output below from when I removed a package. Look carefully at the last few lines.

karatekid@MGD-Server:~$ sudo apt-get remove parole
[sudo] password for karatekid:
no talloc stackframe at ../source3/param/loadparm.c:4864, leaking memory
Reading package lists... Done
Building dependency tree
Reading state information... Done
The following packages will be REMOVED:
  parole
0 upgraded, 0 newly installed, 1 to remove and 3 not upgraded.
1 not fully installed or removed.
After this operation, 1,800 kB disk space will be freed.
Do you want to continue? [Y/n] y
debconf: DbDriver "config": /var/cache/debconf/config.dat is locked by another process: Resource temporarily unavailable
(Reading database ... 231413 files and directories currently installed.)
Removing parole (0.6.1-0ubuntu3.1) ...
Processing triggers for gnome-menus (3.10.1-0ubuntu2) ...
Processing triggers for bamfdaemon (0.5.1+14.04.20140409-0ubuntu1) ...
Rebuilding /usr/share/applications/bamf-2.index...
Processing triggers for desktop-file-utils (0.22-1ubuntu1) ...
Processing triggers for mime-support (3.54ubuntu1) ...
Processing triggers for hicolor-icon-theme (0.13-1) ...
Setting up man-db (2.6.7.1-1) ...
debconf: DbDriver "config": /var/cache/debconf/config.dat is locked by another process: Resource temporarily unavailable
dpkg: error processing package man-db (--configure):
 subprocess installed post-installation script returned error exit status 1
E: Sub-process /usr/bin/dpkg returned an error code (1)
karatekid@MGD-Server:~$

Changed in debconf (Ubuntu):
assignee: nobody → erick samonte (erick-samonte4)
swaroop (sschakri123928) on 2014-12-28
Changed in aptdaemon (Ubuntu):
status: Triaged → Confirmed
assignee: denise (denise-gies) → nobody
Changed in debconf (Ubuntu):
assignee: erick samonte (erick-samonte4) → nobody

I wanted to update my freshly installed 15.04.

tags: added: vivid

Confirmed on Trusty (14.04.2)

It crashed my update of 15.04 MATE.

I am going to have to re-install Ubuntu. This bug completely corrupted my system

Gustav Ekner (gustav-ekner) wrote :

Bug confirmed on 15.04

I got this error on Ubuntu 14.04 after the "Add printer driver"-thingie crashed while trying to add openprinting-gutenprint.

I tried many things including the suggestions here but the solution was to

sudo apt-get install openprinting-gutenprint --reinstall

The problem was that the program was half-installed so apt-get install and apt-get remove both failed. So did apt-get upgrade. I found my solution here: http://askubuntu.com/questions/245477/half-installed-package-error

Changed in debconf (Ubuntu):
assignee: nobody → Julio Alexander Sieg (julio-sieg)
Renate (yollywau) wrote :

I wanted to install unetbootin. The error message came with extlinux

Unsubscribe

Sent from my Samsung device

-------- Original message --------
From: Renate <email address hidden>
Date: 27/08/2015 07:26 (GMT+00:00)
To: Julian Brunt <email address hidden>
Subject: [Bug 349469] Re: debconf: DbDriver "config": /var/cache/debconf/config.dat is locked by another process: Resource temporarily unavailable

I wanted to install unetbootin. The error message came with extlinux

--
You received this bug notification because you are subscribed to a
duplicate bug report (787507).
https://bugs.launchpad.net/bugs/349469

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

Status in Ambasa:
  New
Status in Debconf:
  New
Status in aptdaemon package in Ubuntu:
  Confirmed
Status in debconf package in Ubuntu:
  Triaged

Bug description:
  Upgrading packages that use debconf sometimes fail with the following
  error:

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

To manage notifications about this bug go to:
https://bugs.launchpad.net/ambasa/+bug/349469/+subscriptions

Vinicius (v1n1c1u3gdm) wrote :

It happened to me when trying to install my Epson XP214 printer. I downloaded epson's official drivers

epson-inkjet-printer-escpr_1.6.0-1lsb3.2_amd64.deb
iscan_2.30.1-1~usb0.1.ltdl7_amd64.deb
iscan-data_1.36.0-1_all.deb
iscan-network-nt_1.1.1-1_amd64.deb

but epson-inkjet-printer-escpr_1.6.0-1lsb3.2_amd64.deb failed due to lsb being misconfigured. I tryed to repair it but it breaks everytime after a simple "apt-get install lsb" on 15.04

Vinicius (v1n1c1u3gdm) wrote :
Download full text (12.3 KiB)

The whole procedure

vinicius@vinicius-iron:~/Downloads/epson$ sudo dpkg -i epson-inkjet-printer-201304w_1.0.0-1lsb3.2_amd64.deb 5
[sudo] password for vinicius:
Selecting previously unselected package epson-inkjet-printer-201304w.
(Reading database ... 229356 files and directories currently installed.)
Preparing to unpack epson-inkjet-printer-201304w_1.0.0-1lsb3.2_amd64.deb ...
Unpacking epson-inkjet-printer-201304w (1.0.0-1lsb3.2) ...
dpkg: error processing archive 5 (--install):
 cannot access archive: No such file or directory
dpkg: dependency problems prevent configuration of epson-inkjet-printer-201304w:
 epson-inkjet-printer-201304w depends on lsb (>= 3.2); however:
  Package lsb is not installed.

dpkg: error processing package epson-inkjet-printer-201304w (--install):
 dependency problems - leaving unconfigured
Errors were encountered while processing:
 5
 epson-inkjet-printer-201304w
vinicius@vinicius-iron:~/Downloads/epson$ sudo apt-get -f install
Reading package lists... Done
Building dependency tree
Reading state information... Done
Correcting dependencies... Done
The following extra packages will be installed:
  alien at debugedit lib32z1 libjpeg62 libpod-plainer-perl librpmbuild3
  librpmsign1 lsb lsb-core lsb-cxx lsb-desktop lsb-graphics lsb-languages
  lsb-multimedia lsb-printing lsb-security ncurses-term pax rpm
Suggested packages:
  rpm-i18n elfutils rpmlint rpm2html
Recommended packages:
  libqt3-mt
The following NEW packages will be installed:
  alien at debugedit lib32z1 libjpeg62 libpod-plainer-perl librpmbuild3
  librpmsign1 lsb lsb-core lsb-cxx lsb-desktop lsb-graphics lsb-languages
  lsb-multimedia lsb-printing lsb-security ncurses-term pax rpm
0 upgraded, 20 newly installed, 0 to remove and 3 not upgraded.
1 not fully installed or removed.
Need to get 806 kB of archives.
After this operation, 4.719 kB of additional disk space will be used.
Do you want to continue? [Y/n] y
Get:1 http://br.archive.ubuntu.com/ubuntu/ vivid/main at amd64 3.1.16-1ubuntu1 [37,6 kB]
Get:2 http://br.archive.ubuntu.com/ubuntu/ vivid/main ncurses-term all 5.9+20140712-2ubuntu2 [248 kB]
Get:3 http://br.archive.ubuntu.com/ubuntu/ vivid/main pax amd64 1:20140703-2 [78,8 kB]
Get:4 http://br.archive.ubuntu.com/ubuntu/ vivid/main librpmbuild3 amd64 4.11.3-1.1 [58,0 kB]
Get:5 http://br.archive.ubuntu.com/ubuntu/ vivid/main librpmsign1 amd64 4.11.3-1.1 [8.062 B]
Get:6 http://br.archive.ubuntu.com/ubuntu/ vivid/main debugedit amd64 4.11.3-1.1 [15,8 kB]
Get:7 http://br.archive.ubuntu.com/ubuntu/ vivid/main rpm amd64 4.11.3-1.1 [115 kB]
Get:8 http://br.archive.ubuntu.com/ubuntu/ vivid/main alien all 8.93 [54,0 kB]
Get:9 http://br.archive.ubuntu.com/ubuntu/ vivid/main lib32z1 amd64 1:1.2.8.dfsg-2ubuntu1 [52,9 kB]
Get:10 http://br.archive.ubuntu.com/ubuntu/ vivid/main lsb-security amd64 4.1+Debian11ubuntu8 [4.884 B]
Get:11 http://br.archive.ubuntu.com/ubuntu/ vivid/main lsb-core amd64 4.1+Debian11ubuntu8 [27,4 kB]
Get:12 http://br.archive.ubuntu.com/ubuntu/ vivid/main lsb-graphics amd64 4.1+Debian11ubuntu8 [2.894 B]
Get:13 http://br.archive.ubuntu.com/ubuntu/ vivid/main lsb-cxx amd64 4.1+Debian11ubuntu8 [2.868 B]
Get:14 http://br.archive.ubuntu.com...

I was trying to install Printer drivers with the package dpkg when I found it

Rune Philosof (olberd) wrote :

As in #111 but on 15.10.
I got this error after the "Add printer driver"-UI hanged while trying to add openprinting-gutenprint.

This is the process locking the config.dat:
        |-aptd-+-aptd-+-dpkg
        | | `-sh---dpkg-preconfigu---dpkg-preconfigu

I had tried to install the printer driver three times.
So when I found this bug report two days later, I had to run `sudo fuser -vik /var/cache/debconf/config.dat` three times.
Apparently they were waiting in some queue and locked the file (and then hanged) when I kill the current locking process.

Rune Philosof (olberd) wrote :

Might it be because it wants to ask some debconf question but the graphical ui with the question doesn't show.
So it might be waiting for user input which the user has no way to give?

Rune Philosof (olberd) wrote :

However, when I next ran apt-get install, to install something else, it completed the install of lsb* and openprinting-gutenprint without any questions:
Setting up lsb-core (4.1+Debian11ubuntu8) ...
Setting up lsb-graphics (4.1+Debian11ubuntu8) ...
Setting up lsb-cxx (4.1+Debian11ubuntu8) ...
Setting up lsb-multimedia (4.1+Debian11ubuntu8) ...
Setting up lsb-desktop (4.1+Debian11ubuntu8) ...
Setting up lsb-printing (4.1+Debian11ubuntu8) ...
Setting up lsb-languages (4.1+Debian11ubuntu8) ...
Setting up lsb (4.1+Debian11ubuntu8) ...
Setting up openprinting-gutenprint (5.2.7-1lsb3.2) ...

Changed in debconf (Ubuntu):
status: Triaged → Invalid
status: Invalid → Confirmed
Steve Langasek (vorlon) on 2016-01-19
Changed in debconf (Ubuntu):
status: Confirmed → Triaged
assignee: Julio Alexander Sieg (julio-sieg) → nobody
Brad Chesney (bradchesney79) wrote :

If you want to see this in action I have a set of provisioning scripts that reprocuce the problem in an automated way...

On a brand new Debian 8.1 linode, if you run my script it will prompt you for a mysql password-- the thing is I tried to pre-set the mysql password with debconf.

git clone https://github.com/bradchesney79/2015DebianJessieWebserverProject.git
pushd 2015DebianJessieWebserverProject-master/
git checkout ef2dd6e396c0b88652c47c39f2cf692d562d9d23
popd
mkdir -p /root/bin
cp -R /root/2015DebianJessieWebserverProject-master/* /root/bin/
./root/bin/build-script.sh

The system will begin to build.

<CTRL> + <Z> the password prompt to get back to the command line.

I try to run the debconf command after the fact:

root@server/root/# echo "mysql-server mysql-server/root_password select passw0rd" | debconf-set-selections

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

root@server/root/# fuser -v /var/cache/debconf/config.dat

<Output>
                     USER PID ACCESS COMMAND
/var/cache/debconf/config.dat:
                     root 19165 F.... frontend
</Output>

root@server/root/# kill 19165

Succeeds.

root@server/root/# echo "mysql-server mysql-server/root_password select passw0rd" | debconf-set-selections

Succeeds.

Steve Langasek (vorlon) wrote :

On Wed, Jan 20, 2016 at 03:42:23AM -0000, Brad Chesney wrote:
> If you want to see this in action I have a set of provisioning scripts
> that reprocuce the problem in an automated way...

> On a brand new Debian 8.1 linode, if you run my script it will prompt
> you for a mysql password-- the thing is I tried to pre-set the mysql
> password with debconf.

> git clone https://github.com/bradchesney79/2015DebianJessieWebserverProject.git
> pushd 2015DebianJessieWebserverProject-master/
> git checkout ef2dd6e396c0b88652c47c39f2cf692d562d9d23
> popd
> mkdir -p /root/bin
> cp -R /root/2015DebianJessieWebserverProject-master/* /root/bin/
> ./root/bin/build-script.sh

> The system will begin to build.

> <CTRL> + <Z> the password prompt to get back to the command line.

> I try to run the debconf command after the fact:

> root@server/root/# echo "mysql-server mysql-server/root_password select
> passw0rd" | debconf-set-selections

Ok, well, this is user error. The database *is* locked. The reason this
bug is open is because it's assumed that somehow, two packages are trying to
use the debconf database in parallel; if you're trying to access it yourself
while the debconf frontend is running, that's not a bug.

xebege (carlotrip) on 2016-05-16
Changed in debconf (Ubuntu):
assignee: nobody → xebege (carlotrip)
status: Triaged → Confirmed
Steve Langasek (vorlon) on 2016-05-16
Changed in debconf (Ubuntu):
assignee: xebege (carlotrip) → nobody
status: Confirmed → Triaged
Greg Rickson (greg-rickson) wrote :

I assumed it was because I had both synaptic and Ubuntu Software center open At the same time ??

Steve Langasek (vorlon) wrote :

On Tue, May 24, 2016 at 08:27:41AM -0000, Greg Rickson wrote:
> I assumed it was because I had both synaptic and Ubuntu Software center
> open At the same time ??

That is certainly the sort of thing that could lead to this locking problem,
yes.

Biatu (megagamernet) wrote :

it looks like if the Software Center is running, this will happen. After closing it, everything worked fine.

Displaying first 40 and last 40 comments. View all 125 comments or add a comment.
This report contains Public information  Edit
Everyone can see this information.

Duplicates of this bug

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.