On Tue, Jul 03, 2012 at 03:21:33PM +0200, Harald Dunkel wrote: > The postinst script gets stuck on builing grub.cfg: > > : > Selecting previously unselected package memtest86+. > (Reading database ... 29792 files and directories currently installed.) > Unpacking memtest86+ (from .../memtest86+_4.20-1.1_amd64.deb) ... > Setting up memtest86+ (4.20-1.1) ... > Generating grub.cfg ... > Found linux image: /boot/vmlinuz-3.2.0-3-amd64 > Found initrd image: /boot/initrd.img-3.2.0-3-amd64 > Found linux image: /boot/vmlinuz-3.2.0-0.bpo.2-amd64 > Found initrd image: /boot/initrd.img-3.2.0-0.bpo.2-amd64 > Found linux image: /boot/vmlinuz-2.6.32-5-amd64 > Found initrd image: /boot/initrd.img-2.6.32-5-amd64 > Found memtest86+ image: /memtest86+.bin > Found memtest86+ multiboot image: /memtest86+_multiboot.bin > File descriptor 3 (pipe:[7342]) leaked on lvs invocation. Parent PID 2698: > /bin/sh > grub-probe: error: no such disk. > done > > > "done" is the last line. > > ps -ef shows: ... > root 2206 2202 0 14:58 pts/0 00:00:02 | \_ aptitude > root 2252 2206 0 14:59 pts/1 00:00:00 | \_ /usr/bin/dpkg > --status-fd 23 --configure memtest86+:amd64 > root 2253 2252 0 14:59 pts/1 00:00:00 | \_ > /usr/bin/perl -w /usr/share/debconf/frontend > /var/lib/dpkg/info/memtest86+.postinst configure > root 2259 2253 0 14:59 pts/1 00:00:00 | \_ > [memtest86+.post] <defunct>
This seems to show the debconf "frontend" script not dealing handling the termination of the memtest86+.postinst script. If any, it seems more plausible that the bug would be in debconf. Which debconf version is this ? Are you running squeeze or sid ? If I run "dpkg-reconfigure memtest86+" here (wheezy/amd64), however, things go perfectly fine: | Generating grub.cfg ... | Found background image: /usr/share/images/desktop-base/desktop-grub.png | Found linux image: /boot/vmlinuz-3.2.0-2-amd64 | Found initrd image: /boot/initrd.img-3.2.0-2-amd64 [...] | Found memtest86 image: /memtest86.bin | Found memtest86+ image: /memtest86+.bin | Found memtest86+ multiboot image: /memtest86+_multiboot.bin | done | root# It would be interesting to know what the frontend process is doing when that happens. Can you retry, and show 1. the output of "ps l <pid>" 2. the output of "strace -p <pid>" -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
