Comment 6 for bug 2062176

I initially reassigned this from lxd to glibc on the basis that glibc is responsible for deciding whether to use the 64-bit vs 32-bit time_t variants for all the syscalls it wraps, and give preference to the 64-bit variants; HOWEVER,

       Note: glibc provides no wrapper for futex(), necessitating the use of
       syscall(2).

futex(2).

Confirmed that there are no 'futex' symbols in glibc.

So this is not a bug in glibc, and there is insufficient information here or in the linked github issue to say where the problem lies. The test case given in the github issue is invalid, because it builds without the default noble compiler flags of -D_FILE_OFFSET_BITS=64 -D_TIME_BITS=64 so tells us nothing about what code is actually being run as part of noble that depends on the old syscall.

Someone will need to strace this to find the guilty binary.