Unfortunately those traces don't say much without the debugging symbols. If it happens also with the mainline kernel we should see similar bugs reported upstream, that's why I'm not very convinced about this being a kernel issue. More likely a library issue, considering that it happens with different applications (or interactions between kernel and a particular library).
You mention that the last kernel that was working was like a 6.5? There's a huge delta between 6.5 and 6.8. Maybe we could try to restrict this range a bit more... At https://kernel.ubuntu.com/mainline/ you can find the debs of pretty much all the mainline kernel versions, maybe you could also test some kernels between 6.5 and 6.8 (assuming you can easily reproduce the problem), in order to restrict the range of changes and have a better idea where to look. Thanks! -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2058191 Title: Getting SIGSEGV and SIGILL in many programs To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/2058191/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs