© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
1b1ed1a
(Get the code!)
Hi,
I also ran into this also on xenial. For me also taking the files under xenial-updates instead of xenial (as far as possible) fixed this for me. Thanks to buntix for the hint.
But as the message "for unknown reasons" said, this can happen for different reasons. In my case the libc6-udeb was probably simply newer and incompatible to the initrd and/or installer binaries. And this was fixed by taking the other path with the compatible binaries.
But this message might also have other reasons. The occurence is syncronized because on this date probably the newer version of libc6-udeb for xenial came out.
So I won't mark Bug#1816876 or this one as duplicate, as far as not all people having this two are coming to the same results.
Kind regards,
Lars