On Wed, Mar 24, 2004 at 10:07:37PM +0100, Denis Barbier wrote: > On Wed, Mar 24, 2004 at 09:14:39AM -0500, Greg Folkert wrote: > [...] > > > DEBCONF_DEBUG=developer dpkg --configure xserver-xfree86 > > > or temporarily adding "set -x" as 2nd line to > > > /var/lib/dpkg/info/xserver-xfree86.postinst and running > > > "dpkg --configure xserver-xfree86" might show useful information. > > > > Here is the output > > -- Debconf Developer Debug output > > > > Script started on Wed Mar 24 09:04:39 2004 > > duke:~# DEBCONF_DEBUG=developer dpkg --configure --debug=3773 xserver-xfree86 > [...] > > debconf (developer): <-- METAGET shared/default-x-server choices > > debconf (developer): --> 0 xserver-xfree86 > > dpkg: error processing xserver-xfree86 (--configure): > > subprocess post-installation script returned error exit status 139 > > Errors were encountered while processing: > > xserver-xfree86 > > This exit code is certainly due to a SIGSEGV in a subprocess. > In order to determine the culprit, please add 'set -x' at line 2 of > xserver-xfree86.config (as mentioned earlier by Andreas) and re-run > the command above. This should tell which command segfaults. It won't, because debconf re-executes the maintainer script, losing the -x flag. The bug submitter needs to do this instead: # /usr/share/debconf/frontend sh -x /var/lib/dpkg/info/xserver-xfree86.config configure -- G. Branden Robinson | You can have my PGP passphrase when Debian GNU/Linux | you pry it from my cold, dead branden@debian.org | brain. http://people.debian.org/~branden/ | -- Adam Thornton
Attachment:
signature.asc
Description: Digital signature