On Wed, Nov 22, 2017 at 07:34:15PM +0100, Marius Bakke wrote:
> This is a known problem in glibc that has recently been fixed AFAICT.
> 
> https://sourceware.org/bugzilla/show_bug.cgi?id=21041
> 
> It was also "backported" to the 2.26 release branch:
> 
> https://sourceware.org/git/?p=glibc.git;a=commit;h=88758c4ad3f046d050bc2c3ae0f172b6524ca6c2
> 
> We currently have 2.26 in 'core-updates' which hasn't started building
> yet.  Perhaps we should include this fix, thoughts?

Now we are using 2.28 and I can't reproduce the problem, so I'm closing
the bug.