I’ve downloaded the TS6 beta on Nobara 42 (based on Fedora 42) and the app seg faults when it tried to launch. Some deeper digging shows an AVX2 error, which makes zero sense as I’m on a modern Ryzen CPU that has AVX2 (Ryzen 9 5900X) with an AMD RX 7700XT GPU.
I can’t figure out why the app refuses to run.
No real help here from me, I fear, just for the process of elimination.
I use TS6 on Nobara, too, but my CPU is way older (Intel Skylake). Graphics card is comparable though (RX 7600).
I’ve done as much debugging as I can (I can’t see what is causing the issue because TS isn’t open source so all the code is blocked from the debugging tools)
There is something with Teamspeak itself that is asking some something my PC doesn’t have, but it can’t tell me what it is because the code is locked down. Whatever it is, it’s only missing on my Desktop and nothing else as every other Linux machine I’ve used can run it with no issues at all.
If TS was open source I’m sure this could be figured out and solved, but as of right now I’m at a wall with no way past because I’m not allowed to see what is causing the problem…
I HAVE FIGURED IT OUT
If you use pipewire (which most if not all modern Linux desktops do, especially ones that ship Wayland by default), you can make custom sinks (basically virtual audio input/output devices). HOWEVER if you do not add the “device.properties” section in pipewire.conf when making them, TeamSpeak crashes as it always assumes this will be there. However nothing else I have ever used has required this as I’ve had these sinks set up the same way for years without any issues.
If someone on the dev team can see this, please change how TS6 reads pipewire sinks to ignore if devices.properties is not there and pull the name from factory.name in its place
The solution was in this thread fro TS5 at the very bottom: (Solved) TeamSpeak 5 client refusing to start: SIGSEGV - #19 by Profpyrus
I’ll forward that to the devs to evaluate.
