This has been reported 75 times in the last year according to errors.ubuntu.com.
Notably, almost all the CPUs do not have SSE2, and we build with SSE2. So that's (SSE2 instructions) probably where the SIGILL is coming from. The stack trace is in the static initialization phase right when mixxx starts up.
I don't know if we care, but it's worth noting that happens.
This has been reported 75 times in the last year according to errors.ubuntu.com.
Notably, almost all the CPUs do not have SSE2, and we build with SSE2. So that's (SSE2 instructions) probably where the SIGILL is coming from. The stack trace is in the static initialization phase right when mixxx starts up.
I don't know if we care, but it's worth noting that happens.