Wayland general feedback/suggestions

TeamSpeak 6 Client Suggestions and Feedback
1

The teamspeak6 client lacks some functionality under Wayland compositors on Linux. Here’s the pain points in roughly descending order, from my perspective as a niche user (as I use niri, and not KDE or Gnome)

  • no screensharing currently
    • video devices work wonderfully for testing the server though!
    • use of xdg-desktop-portal w/ pipewire should work fine; if I have to use qpwgraph to mess with the capture plumbing myself that’s fine
  • no keybinds when window unfocused
    • the wayland global-shortcuts stuff is half baked and only really well supported on gnome/kde
    • an alternative would be IPC/cli endpoints (e.g. teamspeak6 --toggle-mute to IPC to the running client), as this would be more easily user-invokable & bindable to arbitrary keybinds outside the application
  • window buttons in top-right are nonfunctional, which makes most of the top-bar functionally extra padding
    • this is maybe fixable via user theming?
2

oh - also, the client appears to be unable to use v4l2 devices as sources - I’m unable to use obs virtual cam (or wf-recorder muxing straight to /dev/video2) as video sources. Rather unexpected lack of support there, since I thought v4l2 devices should work more or less ootb?

3

Well, myself and a few other Linux users have reported the same problems back in Feb. when they’ve launched the beta. There were zero improvements since then, so you might need to wait another year or two.

1 Like
4

same problem here…

5

I’m generally aware. I’ve been holding off on evaluating anything until the self-hostable binaries were available, and I wanted to make the feedback coming from the self-hosters paying for licenses is clear: we want better wayland support