[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#833599: marked as done (debian-installer: choose-mirror segfaults)

Your message dated Mon, 15 Aug 2016 06:41:17 +0200
with message-id <20160815044117.GF2696@mraw.org>
and subject line Re: Bug#833599: debian-installer: choose-mirror segfaults
has caused the Debian Bug report #833599,
regarding debian-installer: choose-mirror segfaults
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 owner@bugs.debian.org

833599: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=833599
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message ---
Package: debian-installer
Severity: grave
Tags: d-i
Justification: renders package unusable


When using todays (and few previous days) netboot/mini.iso amd64
snapshot, I am consistently getting segfault when executing "Choose
mirror to install from (menu item)" during expert install.

in the dmesg:

segfault at 0 ip 000000004017c0 sp 0000xxxx error 4 in choose-mirror[4000000+6000]

I do not think this is related to libc6 issues reported in

I had no issues with debian 8.5.0 netboot iso.


--- End Message ---
--- Begin Message ---
Hi again Witold,

Cyril Brulebois <kibi@debian.org> (2016-08-15):
> Witold Baryluk <witold.baryluk@gmail.com> (2016-08-09):
> > < Unpacking choose-mirror-bin (2.70) ...
> > < Unpacking choose-mirror (2.70) ...
> > ---
> > > Unpacking choose-mirror-bin (2.69) ...
> > > Unpacking choose-mirror (2.69) ...
> > 92c92
> > < Unpacking wpasupplicant-udeb (2.5-1) ...
> > ---
> > > Unpacking wpasupplicant-udeb (2.3-2.4) ...
> > 
> > 
> > Which is strange. As the 2.70 only contains translation fixes.
> > 
> > But it is possible that the compiler used or libc used was different than
> > previously, which somehow manifests here.
> A new glibc upstream version migrated to testing late July, which might
> have to do with the issues you're seeing. I'll be double checking this
> shortly.

I've tracked this down and documented the results in #834383, which I've
just uploaded a fix for. I'm closing this bug report accordingly; thanks
for your investigations and sorry for not getting back to you sooner.


Attachment: signature.asc
Description: Digital signature

--- End Message ---

Reply to: