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

Bug #349469 reported by chocka
This bug affects 642 people
Affects Status Importance Assigned to Milestone
Aptdaemon
Fix Released
Undecided
Unassigned
Debconf
New
Unknown
aptdaemon (Ubuntu)
Invalid
Medium
Unassigned
debconf (Ubuntu)
Fix Released
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

Revision history for this message
chocka (chocka) wrote :
Revision history for this message
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
Revision history for this message
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)
Revision history for this message
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)
affects: update-manager (Ubuntu) → apt (Ubuntu)
Changed in apt (Ubuntu):
importance: Undecided → Medium
status: New → Triaged
Revision history for this message
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.

Revision history for this message
Kevin S (kevin-simpson) wrote : Re: [Bug 349469] Re: debconf: DbDriver "config": /var/cache/debconf/config.dat is locked by another process: Resource temporarily unavailable

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.
>
>

Revision history for this message
Garebear (garyrk) wrote : Re: [Bug 349469] Re: debconf: DbDriver "config": /var/cache/debconf/config.dat is locked by another process: Resource temporarily unavailable

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)
Revision history for this message
Thomas Zahreddin (thomas-zahreddin) wrote :

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

Revision history for this message
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...

Revision history for this message
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)
Revision history for this message
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.

Revision history for this message
kate dyson (kmdyson) wrote : Re: [Bug 349469] Re: debconf: DbDriver "config": /var/cache/debconf/config.dat is locked by another process: Resource temporarily unavailable

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

Revision history for this message
GIANLUCA (saragianlu777) wrote : Re: [Bug 349469] Re: debconf: DbDriver "config": /var/cache/debconf/config.dat is locked by another process: Resource temporarily unavailable

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
Revision history for this message
Mia (komorochema-gmail) wrote : Re: [Bug 349469] Re: debconf: DbDriver "config": /var/cache/debconf/config.dat is locked by another process: Resource temporarily unavailable

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

Revision history for this message
dan hawk (yellowbronco) wrote :

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

Revision history for this message
Leonardo Santagada @ Proge.com.br (santagada-proge) 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. I closed it and removed/installed the package again and it worked.

Revision history for this message
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.

Revision history for this message
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>

Revision history for this message
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
Revision history for this message
Walter Garcia-Fontes (walter-garcia) wrote :

I got this in an update with Oneiric Beta today.

Revision history for this message
ajaxStardust (novicenotes-net) wrote :

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)
tags: added: rls-p-tracking
Steve Langasek (vorlon)
description: updated
Revision history for this message
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
>

Revision history for this message
Joel Wirāmu Pauling (aenertia) (aenertia) wrote :

Wow...

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

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

Revision history for this message
Satyapriyananda (satyapriyananda) wrote :

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.

Revision history for this message
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>

Revision history for this message
hayig2000 (hayig2000) wrote :

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

Revision history for this message
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.

Revision history for this message
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...

Revision history for this message
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?

Revision history for this message
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?

Revision history for this message
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.

Revision history for this message
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.

Revision history for this message
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.

Revision history for this message
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?

Revision history for this message
Pierre Greiner (mailpiegr) wrote :

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

Revision history for this message
Thomas Hood (jdthood) wrote :

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

Revision history for this message
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

Revision history for this message
Emile Wintraeken (wintraek) wrote : Re: [Bug 349469] Re: debconf: DbDriver "config": /var/cache/debconf/config.dat is locked by another process: Resource temporarily unavailable

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

Revision history for this message
Marcelo (maniat1k-deactivatedaccount) wrote : Re: [Bug 349469] Re: debconf: DbDriver "config": /var/cache/debconf/config.dat is locked by another process: Resource temporarily unavailable

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...

Revision history for this message
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)
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)
Changed in aptdaemon (Ubuntu):
assignee: abdelilah (abdelilah51992) → nobody
description: updated
Ibra_dee (deemas-666)
Changed in aptdaemon (Ubuntu):
assignee: nobody → Ibra_dee (deemas-666)
Jennifer (heck-jennifer)
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)
Changed in aptdaemon (Ubuntu):
assignee: Jennifer (heck-jennifer) → nobody
Steve Langasek (vorlon)
Changed in aptdaemon (Ubuntu):
status: Fix Released → Confirmed
denise (denise-gies)
Changed in aptdaemon (Ubuntu):
assignee: nobody → denise (denise-gies)
Changed in aptdaemon (Ubuntu):
status: Confirmed → Triaged
Changed in debconf (Ubuntu):
assignee: nobody → erick samonte (erick-samonte4)
swaroop (sschakri123928)
Changed in aptdaemon (Ubuntu):
status: Triaged → Confirmed
assignee: denise (denise-gies) → nobody
Changed in debconf (Ubuntu):
assignee: erick samonte (erick-samonte4) → nobody
tags: added: vivid
Changed in debconf (Ubuntu):
assignee: nobody → Julio Alexander Sieg (julio-sieg)
Changed in debconf (Ubuntu):
status: Triaged → Invalid
status: Invalid → Confirmed
Steve Langasek (vorlon)
Changed in debconf (Ubuntu):
status: Confirmed → Triaged
assignee: Julio Alexander Sieg (julio-sieg) → nobody
79 comments hidden view all 159 comments
Revision history for this message
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.

Revision history for this message
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)
Changed in debconf (Ubuntu):
assignee: nobody → xebege (carlotrip)
status: Triaged → Confirmed
Steve Langasek (vorlon)
Changed in debconf (Ubuntu):
assignee: xebege (carlotrip) → nobody
status: Confirmed → Triaged
Revision history for this message
Greg Rickson (greg-rickson) wrote :

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

Revision history for this message
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.

Revision history for this message
Biatu (megagamernet) wrote :

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

Tirigo (wahren-amine)
Changed in debconf (Ubuntu):
status: Triaged → Confirmed
Changed in aptdaemon (Ubuntu):
status: Confirmed → Fix Released
Changed in debconf (Ubuntu):
status: Confirmed → Fix Released
Steve Langasek (vorlon)
Changed in debconf (Ubuntu):
status: Fix Released → Triaged
Changed in aptdaemon (Ubuntu):
status: Fix Released → Triaged
栾骋 (luancheng888)
affects: debconf (Ubuntu) → live-debconfig (Ubuntu)
Colin Watson (cjwatson)
affects: live-debconfig (Ubuntu) → debconf (Ubuntu)
5 comments hidden view all 159 comments
Revision history for this message
hamdou (fallhamd) wrote :

hello

Changed in aptdaemon (Ubuntu):
assignee: nobody → hamdou (fallhamd)
status: Triaged → Incomplete
Colin Watson (cjwatson)
Changed in aptdaemon (Ubuntu):
status: Incomplete → Triaged
pjeeva (pjeeva11)
Changed in aptdaemon (Ubuntu):
assignee: hamdou (fallhamd) → pjeeva (pjeeva11)
dino99 (9d9)
Changed in aptdaemon (Ubuntu):
assignee: pjeeva (pjeeva11) → nobody
Al Amin (alamin.rohita)
Changed in debconf (Ubuntu):
assignee: nobody → Al Amin (alamin.rohita)
Steve Langasek (vorlon)
Changed in debconf (Ubuntu):
assignee: Al Amin (alamin.rohita) → nobody
7 comments hidden view all 159 comments
Revision history for this message
iGadget (igadget) wrote :

What's up with all the spamming on Launchpad lately? Please, ban these accounts.
Unsubscribing to all notificiatons on this bug (also since despite it's affecting over 650 people and has a heat value of over 4000, it's not even assigned to anyone...).

Changed in debconf (Ubuntu):
status: Triaged → Confirmed
Changed in aptdaemon (Ubuntu):
status: Triaged → Confirmed
Changed in aptdaemon:
status: New → Confirmed
Changed in ambasa:
assignee: nobody → maurizio gamberini (mauriziogamberini1)
Changed in aptdaemon:
assignee: nobody → maurizio gamberini (mauriziogamberini1)
Changed in debconf:
assignee: nobody → maurizio gamberini (mauriziogamberini1)
Changed in aptdaemon (Ubuntu):
assignee: nobody → maurizio gamberini (mauriziogamberini1)
Changed in debconf (Ubuntu):
assignee: nobody → maurizio gamberini (mauriziogamberini1)
Steve Langasek (vorlon)
affects: ambasa → null-and-void
Changed in null-and-void:
assignee: maurizio gamberini (mauriziogamberini1) → nobody
Changed in aptdaemon (Ubuntu):
status: Confirmed → Triaged
Changed in debconf (Ubuntu):
assignee: maurizio gamberini (mauriziogamberini1) → nobody
Changed in aptdaemon (Ubuntu):
assignee: maurizio gamberini (mauriziogamberini1) → nobody
Changed in debconf:
assignee: maurizio gamberini (mauriziogamberini1) → nobody
Changed in aptdaemon:
assignee: maurizio gamberini (mauriziogamberini1) → nobody
Changed in debconf (Ubuntu):
status: Confirmed → Triaged
2 comments hidden view all 159 comments
Revision history for this message
Launchpad Janitor (janitor) wrote :

Status changed to 'Confirmed' because the bug affects multiple users.

Steve Langasek (vorlon)
affects: null-and-void → upstart (Ubuntu)
Changed in upstart (Ubuntu):
status: New → Confirmed
Steve Langasek (vorlon)
no longer affects: upstart (Ubuntu)
aden iwa rante (radeniw)
Changed in aptdaemon:
assignee: nobody → aden iwa rante (radeniw)
Changed in debconf (Ubuntu):
status: Triaged → New
Changed in aptdaemon (Ubuntu):
status: Triaged → New
Steve Langasek (vorlon)
Changed in aptdaemon:
assignee: aden iwa rante (radeniw) → nobody
Changed in aptdaemon (Ubuntu):
status: New → Triaged
Changed in debconf (Ubuntu):
status: New → Triaged
Changed in debconf (Ubuntu):
status: Triaged → Incomplete
status: Incomplete → Opinion
Steve Langasek (vorlon)
Changed in debconf (Ubuntu):
status: Opinion → Invalid
status: Invalid → Triaged
RATAN (rk191.-)
Changed in debconf (Ubuntu):
status: Triaged → Incomplete
Steve Langasek (vorlon)
Changed in debconf (Ubuntu):
status: Incomplete → Triaged
Revision history for this message
Yuniarti (arzn) wrote :

debconf: DbDriver "config": /var/cache/debconf/config.dat is locked by another process: Resource temporarily unavailable
dpkg: error processing package shim-signed (--configure):
 subprocess installed post-installation script returned error exit status 1
No apport report written because MaxReports is reached already
                                                              Errors were encountered while processing:
 libssl1.0.0:amd64
 libssl1.0.0:i386
 php7.1-cli
 php7.1-fpm
 php7.1-dev
 libphp7.1-embed
 php7.0-cli
 php7.0-dev
 php7.0-fpm
 shim-signed
E: Sub-process /usr/bin/dpkg returned an error code (1)

Manoj Singh (manojs1969)
Changed in debconf (Ubuntu):
status: Triaged → New
Steve Langasek (vorlon)
Changed in debconf (Ubuntu):
status: New → Triaged
Revision history for this message
John Howard (orthopteroid) wrote :
Download full text (4.3 KiB)

The below command (installing some dotnet framework dependencies) kicked up this error (and "1 not fully installed or removed.").

Just prior to running this command the visual-studio-code editor had unsuccessfully tried to download and install mono-related packages.

-----

# sudo apt-get install dotnet-dev-1.0.4
Reading package lists... Done
Building dependency tree
Reading state information... Done
The following packages were automatically installed and are no longer required:
  guile-2.0-libs libv8-3.14.5 linux-image-4.4.0-83-generic weechat-core
Use 'sudo apt autoremove' to remove them.
The following additional packages will be installed:
  dotnet-hostfxr-1.0.1 dotnet-hostfxr-1.1.0 dotnet-sharedframework-microsoft.netcore.app-1.0.5
  dotnet-sharedframework-microsoft.netcore.app-1.1.2 linux-image-4.4.0-83-generic
Suggested packages:
  fdutils linux-doc-4.4.0 | linux-source-4.4.0 linux-headers-4.4.0-83-generic
The following NEW packages will be installed:
  dotnet-dev-1.0.4 dotnet-hostfxr-1.0.1 dotnet-hostfxr-1.1.0 dotnet-sharedframework-microsoft.netcore.app-1.0.5
  dotnet-sharedframework-microsoft.netcore.app-1.1.2
The following packages will be upgraded:
  linux-image-4.4.0-83-generic
1 upgraded, 5 newly installed, 0 to remove and 6 not upgraded.
1 not fully installed or removed.
Need to get 97.3 MB/119 MB of archives.
After this operation, 347 MB of additional disk space will be used.
Do you want to continue? [Y/n]
Get:1 https://apt-mo.trafficmanager.net/repos/dotnet-release xenial/main amd64 dotnet-hostfxr-1.1.0 amd64 1.1.0-1 [124 kB]
Get:2 https://apt-mo.trafficmanager.net/repos/dotnet-release xenial/main amd64 dotnet-sharedframework-microsoft.netcore.app-1.1.2 amd64 1.1.2-1 [22.9 MB]
Get:3 https://apt-mo.trafficmanager.net/repos/dotnet-release xenial/main amd64 dotnet-hostfxr-1.0.1 amd64 1.0.1-1 [123 kB]
Get:4 https://apt-mo.trafficmanager.net/repos/dotnet-release xenial/main amd64 dotnet-sharedframework-microsoft.netcore.app-1.0.5 amd64 1.0.5-1 [22.6 MB]
Get:5 https://apt-mo.trafficmanager.net/repos/dotnet-release xenial/main amd64 dotnet-dev-1.0.4 amd64 1.0.4-1 [51.5 MB]
Fetched 97.3 MB in 27s (3,486 kB/s)
debconf: DbDriver "config": /var/cache/debconf/config.dat is locked by another process: Resource temporarily unavailable
(Reading database ... 210651 files and directories currently installed.)
Preparing to unpack .../linux-image-4.4.0-83-generic_4.4.0-83.106_amd64.deb ...
debconf: DbDriver "config": /var/cache/debconf/config.dat is locked by another process: Resource temporarily unavailable
dpkg: error processing archive /var/cache/apt/archives/linux-image-4.4.0-83-generic_4.4.0-83.106_amd64.deb (--unpack):
 subprocess new pre-installation script returned error exit status 1
Examining /etc/kernel/postrm.d .
run-parts: executing /etc/kernel/postrm.d/initramfs-tools 4.4.0-83-generic /boot/vmlinuz-4.4.0-83-generic
run-parts: executing /etc/kernel/postrm.d/zz-update-grub 4.4.0-83-generic /boot/vmlinuz-4.4.0-83-generic
Selecting previously unselected package dotnet-hostfxr-1.1....

Read more...

Changed in debconf (Ubuntu):
assignee: nobody → MAYANK SHUKLA (mayankgonda)
Steve Langasek (vorlon)
Changed in debconf (Ubuntu):
assignee: MAYANK SHUKLA (mayankgonda) → nobody
Revision history for this message
Eddie Losper (losper-eddie) wrote : Re: [Bug 349469] Re: debconf: DbDriver "config": /var/cache/debconf/config.dat is locked by another process: Resource temporarily unavailable

DEAR STEVE,

I DON'T KNO'W WHY THIS IS STIL ON MY COMPUTER, BECAUSE I DON'T USE UBUNTU ANYMORE.
I AM USING VODAFONE.

THIS CAN BE DELETED FROM MY COMPUTER PLEASE.

REGARDS,

EDDIE LOSPER

From: Steve Langasek
Date: 2017-07-07 15:18
To: losper.eddie
Subject: [Bug 349469] Re: debconf: DbDriver "config": /var/cache/debconf/config.dat is locked by another process: Resource temporarily unavailable
** Changed in: debconf (Ubuntu)
     Assignee: MAYANK SHUKLA (mayankgonda) => (unassigned)

--
You received this bug notification because you are subscribed to
Aptdaemon.
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 Aptdaemon:
  Confirmed
Status in Debconf:
  New
Status in aptdaemon package in Ubuntu:
  Triaged
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/aptdaemon/+bug/349469/+subscriptions

Revision history for this message
Adriano Batista Prieto (prietoab) wrote :

Complementing #8 and #11:

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

So, I made a backup of the files contained in /var/cache/debconf/ and have deleted all the original files in the same directory. After that, I've "restored" the backup and the upgrade worked fine.

lolo (loloadam373)
Changed in aptdaemon (Ubuntu):
status: Triaged → Incomplete
Changed in debconf (Ubuntu):
status: Triaged → Confirmed
Steve Langasek (vorlon)
Changed in debconf (Ubuntu):
status: Confirmed → Triaged
kirill (kirill-yalta)
Changed in aptdaemon (Ubuntu):
assignee: nobody → kirill (kirill-yalta)
Changed in debconf:
importance: Undecided → Unknown
status: New → Unknown
Steve Langasek (vorlon)
Changed in aptdaemon (Ubuntu):
assignee: kirill (kirill-yalta) → nobody
Changed in debconf:
status: Unknown → New
mahdi (mnusrat)
Changed in aptdaemon (Ubuntu):
assignee: nobody → mahdi (mnusrat)
status: Incomplete → Fix Committed
Changed in aptdaemon:
status: Confirmed → Fix Released
Changed in aptdaemon (Ubuntu):
status: Fix Committed → Fix Released
Changed in debconf (Ubuntu):
status: Triaged → Fix Released
Steve Langasek (vorlon)
Changed in aptdaemon (Ubuntu):
status: Fix Released → Incomplete
Changed in debconf (Ubuntu):
status: Fix Released → Triaged
Colin Watson (cjwatson)
Changed in aptdaemon (Ubuntu):
assignee: mahdi (mnusrat) → nobody
j.fred muggs (fredmuggs)
Changed in aptdaemon:
assignee: nobody → j.fred muggs (fredmuggs)
dino99 (9d9)
Changed in aptdaemon:
assignee: j.fred muggs (fredmuggs) → nobody
Changed in aptdaemon (Ubuntu):
status: Incomplete → Invalid
4 comments hidden view all 159 comments
Revision history for this message
dino99 (9d9) wrote :

Colin, Steve

please do something about the message output that newbies does not understand.

"locked by another process" that says it all; its enough for experienced users, but let think the others there is a bug. This is not a bug indeed, but a lack of user's knowledge.

"Resource temporarily unavailable" might not be scary for the crowd, but some should possibly prefer something more informative, like "please close first the other package manager, then you will be able to continue"

Facundo (fakku)
Changed in debconf (Ubuntu):
status: Triaged → Fix Released
Steve Langasek (vorlon)
Changed in debconf (Ubuntu):
status: Fix Released → Triaged
2 comments hidden view all 159 comments
Revision history for this message
tritonus (prestosfz) wrote :

windows 10 lost ! Ubuntu begun with problems to install ! Ubuntu hav e problems to boot at the beginning! CIAO hans

Changed in debconf (Ubuntu):
assignee: nobody → tritonus (prestosfz)
dino99 (9d9)
Changed in debconf (Ubuntu):
assignee: tritonus (prestosfz) → nobody
Changed in aptdaemon (Ubuntu):
status: Invalid → Fix Released
Changed in debconf (Ubuntu):
status: Triaged → Fix Released
Steve Langasek (vorlon)
Changed in aptdaemon (Ubuntu):
status: Fix Released → Invalid
Changed in debconf (Ubuntu):
status: Fix Released → Triaged
Changed in aptdaemon:
assignee: nobody → Nguyen Hoang Thuy Trang (trangnht)
Steve Langasek (vorlon)
Changed in aptdaemon:
assignee: Nguyen Hoang Thuy Trang (trangnht) → nobody
Changed in debconf (Ubuntu):
status: Triaged → New
Steve Langasek (vorlon)
Changed in debconf (Ubuntu):
status: New → Triaged
affects: aptdaemon → xorg-lts-transitional (Ubuntu)
Changed in debconf (Ubuntu):
status: Triaged → Incomplete
status: Incomplete → Confirmed
status: Confirmed → Fix Released
Changed in aptdaemon (Ubuntu):
status: Invalid → Fix Released
Steve Langasek (vorlon)
Changed in debconf (Ubuntu):
status: Fix Released → Triaged
affects: xorg-lts-transitional (Ubuntu) → aptdaemon
Changed in aptdaemon (Ubuntu):
status: Fix Released → Invalid
Morais (morais28)
Changed in aptdaemon:
assignee: nobody → Ismael Morais (morais28)
Steve Langasek (vorlon)
Changed in aptdaemon:
assignee: Morais (morais28) → nobody
2 comments hidden view all 159 comments
Revision history for this message
Ramshad Abdulraheem (datablackpanther) wrote :

Simply Reload the system will work

Revision history for this message
Rayden Joshua Britto (rayden-britto05) wrote :

ibpam0g

Changed in debconf (Ubuntu):
status: Triaged → Confirmed
Changed in aptdaemon (Ubuntu):
status: Invalid → Confirmed
Steve Langasek (vorlon)
Changed in debconf (Ubuntu):
status: Confirmed → Triaged
Changed in aptdaemon (Ubuntu):
status: Confirmed → Invalid
Changed in aptdaemon:
assignee: nobody → Ahmed Mohamed Tayel (atayel18)
Changed in debconf (Ubuntu):
assignee: nobody → Ahmed Mohamed Tayel (atayel18)
Changed in aptdaemon (Ubuntu):
assignee: nobody → Ahmed Mohamed Tayel (atayel18)
Changed in debconf (Ubuntu):
status: Triaged → New
status: New → Fix Released
Steve Langasek (vorlon)
Changed in debconf (Ubuntu):
assignee: Ahmed Mohamed Tayel (atayel18) → nobody
Changed in aptdaemon (Ubuntu):
assignee: Ahmed Mohamed Tayel (atayel18) → nobody
Changed in aptdaemon:
assignee: Ahmed Mohamed Tayel (atayel18) → nobody
Changed in debconf (Ubuntu):
assignee: nobody → SACHIN SALEEM (sachinrog)
assignee: SACHIN SALEEM (sachinrog) → nobody
Changed in debconf (Ubuntu):
assignee: nobody → Aayush Nepal (darkwebster82)
Steve Langasek (vorlon)
Changed in debconf (Ubuntu):
assignee: Aayush Nepal (darkwebster82) → nobody
1 comments hidden view all 159 comments
Revision history for this message
RICARDO ALEXIS RESTREPO RENGIFO (richard618921) wrote :

Hello I am richard618921. I need to solve the error message debconf: DbDriver "config": /var/cache/debconf/config.dat is locked by another process: Resource temporarily unavailable. What can I do ???

Changed in aptdaemon:
assignee: nobody → RICARDO ALEXIS RESTREPO RENGIFO (richard618921)
Steve Langasek (vorlon)
Changed in aptdaemon:
assignee: RICARDO ALEXIS RESTREPO RENGIFO (richard618921) → nobody
Changed in debconf (Ubuntu):
assignee: nobody → Yam budhathoki (yam-8138)
Changed in aptdaemon (Ubuntu):
assignee: nobody → Yam budhathoki (yam-8138)
Changed in aptdaemon:
assignee: nobody → Yam budhathoki (yam-8138)
Steve Langasek (vorlon)
Changed in aptdaemon:
assignee: Yam budhathoki (yam-8138) → nobody
Changed in aptdaemon (Ubuntu):
assignee: Yam budhathoki (yam-8138) → nobody
Changed in debconf (Ubuntu):
assignee: Yam budhathoki (yam-8138) → nobody
Displaying first 40 and last 40 comments. View all 159 comments or add a comment.
This report contains Public information  
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.