Your message dated Sun, 20 Apr 2008 09:15:28 +0300
with message-id <[EMAIL PROTECTED]>
and subject line Re: Bug#114658: debconf seg fault
has caused the Debian Bug report #114658,
regarding debconf seg fault
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [EMAIL PROTECTED]
immediately.)


-- 
114658: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=114658
Debian Bug Tracking System
Contact [EMAIL PROTECTED] with problems
--- Begin Message ---
Package: debconf
Version: 1.0.10

Architecture: MIPS

Hi,

Setting up debconf (1.0.10) ...
dpkg: error processing debconf (--configure):
 subprocess post-installation script killed by signal (Segmentation fault)
Errors were encountered while processing:
 debconf
E: Sub-process /usr/bin/dpkg returned an error code (1)

This is repeatable.

(On an SG Indy)
Dave
 ---------------- Have a happy GNU millennium! ----------------------   
/ Dr. David Alan Gilbert    | Running GNU/Linux on Alpha,68K| Happy  \ 
\ gro.gilbert @ treblig.org | MIPS,x86,ARM, SPARC and HP-PA | In Hex /
 \ _________________________|_____ http://www.treblig.org   |_______/


--- End Message ---
--- Begin Message ---
On Mon, Oct 15, 2001 at 05:47:35PM +0200, Martin Michlmayr wrote:
> * Joey Hess <[EMAIL PROTECTED]> [20011013 21:32]:
> > Sounds like a general perl segfault problem on the MIPS then. debconf
> 
> FWIW, I've seen random seg faults with perl on mips and mipsel, too,
> and know of others who had the same experience.

I assume these have since been fixed. The best I could find are these:

 http://lists.debian.org/debian-mips/2002/08/msg00022.html

 http://web.archive.org/web/20020610073339/www.debian.org/ports/mips/

which suggest it was a kernel problem specific to R4600 processors. It
was on the MIPS ports 'known problems' list until 2005 or 2006.

There's no way to look into this anymore. Closing.

Cheers,
-- 
Niko Tyni   [EMAIL PROTECTED]


--- End Message ---

Reply via email to