Paul Seelig wrote: > The screenshot provided is from a bookworm system with the > backported GNUstep packages from trixie.
Oh, I missed this. A "backport" means to rebuild the package for an older distro release using the toolchain of the older release, and older versions of the build-dependencies, if that is possible. If the dependency information in your initial report is correct, that is not the case -- glibc in bookworm is 2.36-9+deb12u9 and not 2.40-3, GCC is 12.2.0-14 and not 14.2.0-8. And of course the kernel in bookworm is 6.1.115 and not 6.10.12. If the bug cannot be reproduced on bookworm (aka stable), trixie (aka testing) or unstable (aka sid) with the stock Debian package, then I'm afraid it's invalid (still, I'd like to know about it, what's causing it and to get it fixed). How did you make these backports, exactly? Is this a bookworm machine dist-upgraded to trixie/sid? In that case you can just install the stock Debian packages for everything; there's no need for backports.