Christian, again this bug report is about an already-resolved bug in
grub. Please open a new bug report for your unrelated issue.
--
dpkg fails with debconf locked
https://bugs.launchpad.net/bugs/189005
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscrib
Can confirm this bug on hardy. Also happens with other packages.
for example: sudo dpkg-reconfigure -p low gnome-applets
so it must be related to dpkg-packages somehow, I guess
--
dpkg fails with debconf locked
https://bugs.launchpad.net/bugs/189005
You received this bug notification because you
Sridhar,
The bug you've followed up to is a bug in the grub package that has been
resolved. If you're having debconf locking errors installing other
packages in the LiveCD, that is an entirely separate error which should
be filed in a new bug report.
--
dpkg fails with debconf locked
https://bu
Here is a work around: mv /var/cache/debconf/* /tmp/backup-debconf/
--
dpkg fails with debconf locked
https://bugs.launchpad.net/bugs/189005
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.u
Well, this is bug is still happening with the *released* 8.04 Live CD.
What gives?
[EMAIL PROTECTED]:~$ sudo apt-get install flashplugin-nonfree
Reading package lists... Done
Building dependency tree
Reading state information... Done
flashplugin-nonfree is already the newest version.
0 upgr
@Steve Langasek , yor are correct, but I think that should be a dpkg or
debconf bug or both, because should finish the lock or maybe remove it ( I used
--force-all ). tomorow i will search better.
thanks for your attention.
[EMAIL PROTECTED]:/home/myloginz# fuser -v /var/cache/debconf/config.
berg,
The bug that you've followed up to *is* fixed. Whatever the problem is
that you're seeing, it's not this bug. Indeed, your log shows no
mention of grub or any kernel-related packages.
Please file a new bug report against glibc for the problem you're
seeing.
** Changed in: grub (Ubuntu Ha
this is my situation:
I installed fresh install of Edubuntu 6.06.1
Make all dist-upgrade, rebooted
run update-manger -d
( 900 MB after ... and 14 hours too :(
the system seems rebooted ( xterm used to run update-manager was closed) . I
know, there is not automatic reboot.
Or my system have eler
this problem is no fixed. the "lock" happens with differents packages.
** Changed in: grub (Ubuntu Hardy)
Status: Fix Released => Confirmed
--
dpkg fails with debconf locked
https://bugs.launchpad.net/bugs/189005
You received this bug notification because you are a member of Ubuntu
Bugs,
This bug was fixed in the package grub - 0.97-29ubuntu17
---
grub (0.97-29ubuntu17) hardy; urgency=low
* debian/update-grub: use db_x_loadtemplatefile instead of
debconf-loadtemplate, so that we can call update-grub from maintainer
scripts of packages that do their own debco
Thanks!
--
dpkg fails with debconf locked
https://bugs.launchpad.net/bugs/189005
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-b
Hardy fully upgraded
The bus is marked as "fix committed" but i still have on all 3 update pc
this issue ( 21 February 2008 )
Thank you
--
dpkg fails with debconf locked
https://bugs.launchpad.net/bugs/189005
You received this bug notification because you are a member of Ubuntu
Bugs, which
** Changed in: grub (Ubuntu Hardy)
Status: In Progress => Fix Committed
--
dpkg fails with debconf locked
https://bugs.launchpad.net/bugs/189005
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-bugs mailing list
ub
Confirmed, if called from a maintainer script that uses debconf, the
current update-grub in hardy will error out. This wasn't tested for
because the official Ubuntu kernel packages don't use debconf.
I'll work on rolling this into the next upload.
** Changed in: grub (Ubuntu)
Importance: Unde
** Changed in: dpkg (Ubuntu)
Status: Confirmed => Invalid
--
dpkg fails with debconf locked
https://bugs.launchpad.net/bugs/189005
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@list
I agree with supernaicol, I modified the file /etc/kernel-img.conf by
commenting the stanza
# postin_hook = update-grub
then modified by hand the grub.lst to enable booting into new kernel image.
--
dpkg fails with debconf locked
https://bugs.launchpad.net/bugs/189005
You received this bug noti
I can confirm the work around posted by supernaicol, after downgrading grub my
two waiting kernel updates finaly installed succesfully.
The bug seems to be with the update-grub script, or the calling of it from
dpkg. I don't know enough of the package managment to realy asses this.
--
dpkg fail
I've some news...
I resolved the issue downgrading grub to the gutsy version, 0.97-29ubuntu4.
So maybe this is a grub bug, not an initramfs-tool one.
Bye folks.
** Changed in: grub (Ubuntu)
Sourcepackagename: initramfs-tools => grub
--
dpkg fails with debconf locked
https://bugs.launchpad.net/bu
me too, I can confirm the bug... it's quite annoying not being able to
install any new kernel image... I would port this bug to Hardy too.
** Also affects: initramfs-tools (Ubuntu)
Importance: Undecided
Status: New
--
dpkg fails with debconf locked
https://bugs.launchpad.net/bugs/18900
i can confirm the bug.
the solution two posts above doesn't work for me either.
Richte linux-image-2.6.24-mactelmacbook ein (2.6.24-mactelmacbook-10.00.Custom)
...
Running depmod.
Finding valid ramdisk creators.
Using mkinitramfs-kpkg to build the ramdisk.
initrd.img(/boot/initrd.img-2.6.24-macte
stSabri
sudo chmod 777 /var/cache/debconf/config.dat
make the updates
...
and restoring original permissions
sudo chmod 644 /var/cache/debconf/config.dat
don't works for me...
--
dpkg fails with debconf locked
https://bugs.launchpad.net/bugs/189005
You received this bug notification b
I face the same problem, my solution : change the access mode to 777 the
file config.dat in /var/cache/debconf : # chmod 777
/var/cache/debconf/config.dat
--
dpkg fails with debconf locked
https://bugs.launchpad.net/bugs/189005
You received this bug notification because you are a member of Ubuntu
This is pretty serious. It's currently impossible to test kernel
patches on Hardy.
--
dpkg fails with debconf locked
https://bugs.launchpad.net/bugs/189005
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-bugs mailing li
Same problem here... installing custom kernel
Thank you
apt-get -f install
.
Configuro linux-image-2.6.24.2-custom (2.6.24.2-custom-10.00.Custom) ...
Running depmod.
Finding valid ramdisk creators.
Using mkinitramfs-kpkg to build the ramdisk.
find: /lib/firmware/2.6.24.2-custom: Nessun file
** Summary changed:
- dpkg fails with deconf locked
+ dpkg fails with debconf locked
** Description changed:
- when install a kernel dpkg fails and reports deconf locked
+ when install a kernel dpkg fails and reports debconf locked
[EMAIL PROTECTED]:/usr/src$ sudo dpkg -i
linux-image-2.6.2
25 matches
Mail list logo
