add finish-args-contains-both-x11-and-wayland for teamspeak

[SenseiHiraku]

See flathub/com.teamspeak.TeamSpeak#83 (comment)
Any other socket combination is causing a crash when using the newest version

[bbhtt]

what happens when only x11 is used?

[SenseiHiraku]

what happens when only x11 is used?

[2:2:1016/143732.018287:ERROR:../source/chromium/src/ui/ozone/platform/wayland/ozone_platform_wayland.cc:282] Failed to initialize Wayland platform
Crash on startup, this worked in older versions, but since wayland screenshare was added in the new version, this does not work anymore.

[bbhtt]

why is it trying to use wayland when it is not available?

[SenseiHiraku]

I'm not sure, but here is the changelog for the new update:
https://community.teamspeak.com/t/teamspeak-6-0-0-beta3-foundation-i-update/62417

[SenseiHiraku]

why is it trying to use wayland when it is not available?

This is in the changelog @bbhtt

"Added support for Pipewire Capturing under wayland

Wayland is needed in order to stream wayland applications, for which they've added support in the new version.
Teamspeak 6 is still in beta, so things might change in future, and then I'll let you know when the finish-args-contains-both-x11-and-wayland exception is not needed any more and things get more stable.

[bbhtt]

Yes but that should not be used when it has no access to the wayland socket.

You cannot use wayland specific features when the app itself has no access to the wayland socket.

[SenseiHiraku]

The app itself has wayland support and is using it. We're only resolving a crash issue by that exception, which occures when wayland socket is used with or without combination of fallback-x11 in the specific case of opening hotkey or audio settings.

[bbhtt]

Then you should use x11 only, if it crashes it doesn't support wayland properly and if -socket=x11 also causes a crash, clearly the app is broken.