The problem has fixed itself with today's updates. It can't have been the kernel or libc after all, neither was in this round of updates. Anyway, feel free to close, unless you still want to isolate the cause.