> My install image (with a modified boot meny, that loads the preseeding etc)
> is about a year old now, so not sure what the correct fix is. Updating our
> customised boot image would be a lot of work, so I’d prefer to have it
> fixed “correctly” (whatever it is).

I agree, and that was my initial reaction, but we were able to just drop
in the new kernel and initrd over top of the our previous ones and our
menu configs and preseeds came forward without any tweaks. Depends on if
you've built a custom initrd or modified the kernel, but might be worth
a try since I don't know if a backward compatible fix is on the way.
(linux and initrd.gz for netinstall available here:
http://archive.ubuntu.com/ubuntu/dists/xenial-updates/main/installer-
amd64/current/images/netboot/ubuntu-installer/amd64/)

> We haven’t used the image in several months, so didn’t notice until yesterday.
> Just bad timing. But if it started happing just a few days ago (and you’ve 
> been
> running it successfully on the new libc6 package), then I agree it can’t be 
> that..

Our netinstall image was about 6 months old, and we use it almost every
day. We know it was working as recently as 2019-02-19 and first saw
issues with it shortly before 22:00 UTC on 2019-02-20, around the time
this bug report was opened.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1816846

Title:
  segfault in libc-2.23.so netinstall installation pxe

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/glibc/+bug/1816846/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

Reply via email to