Hi,
Since the new update the client seems to be running wayland instead of xwayland which is great because it fixed the screensharing but it completely broke every keybinding for me.
My old bindings simply no longer register when I press them, even when hovering over TeamSpeak and it’s in focus.
If I try re-binding the button the input is not recognized at all. It simply says “Press key combination” and doesn’t see any input.
I am able to create a new profile and type to give it a new name, so the application seems to be recognizing some input.
In Hyprland I did try making some global binds like thier example for teamspeak 3 Binds – Hyprland Wiki
But this didn’t get me any further.
System:
- Version: 6.0.0-beta3.2
- WM: Hyprland 0.51.1
- OS: EndeavourOS
- Kernel: Linux 6.16.10-arch1-1
Thanks.
If you start the client with --ozone-platform=x11 it will revert to the old behavior. With the latest version the client starts as a native wayland window by default.
Support for the global shortcut portal is planned but has no ETA as of now.
3 Likes
Hi, this solution is very vague as a relatively casual linux user that came from windows only a couple years ago. I start the app by double-clicking it in my Dolphin file browser, but it is unclear how to run it in terminal let alone add this line to it somehow.
I am running X11 solely because of its hotkey friendliness, but hotkeys do not function on this client for me just like the OP’s didn’t.
I’ve tried adding --ozone-platform=x11 to all sorts of fields in the teamspeak-client.desktop properties as well but it either didn’t run or didn’t fix, so I assume im doing something wrong. Sorry for the noob question.
You need to add it to the exec line like this. It worked when you no longer see the warning banner in the Key Bindings settings.
[Desktop Entry]
Version=1.0
Type=Application
StartupNotify=false
-Exec=/path/to/TeamSpeak %u
+Exec=/path/to/TeamSpeak --ozone-platform=x11 %u
Name=TeamSpeak
...
4 Likes
Thank you for the reply!
I found the correct line and added it as you wrote, but it looks like the program still doesn’t respond to hotkey binding, so perhaps the cause for my issue is different from the OP’s.
My PTT and all other binds work fully in my TS3 client on the same system, no matter what other app is in focus.
With the TS6 client, certain keys will work within the program like ESC to cancel a binding, and some F keys, but nothing can be bound to a hotkey, as if it’s not listening. The myTeamSpeak account carries over my preferred hotkey from TS3 into TS6, which is Mouse5, but pressing it doesn’t do anything, even if it is bound.
It worked when you no longer see the warning banner in the Key Bindings settings.
This is not a warning I see in my Key Bindings settings on x11. I started the program on a Wayland session to see if anything changed. The warning now appears, but the fix still does not seem effective. I also tried the alternative --ozone-platform-hint=x11 variable/argument it suggests and again without any arguments at all, but no luck on changing the key binding functionality, but I can also see that the warning banner is not being removed, so perhaps the line is not applying. My desktop entry looks like this:
[Desktop Entry]
Categories=AudioVideo;Audio;Chat;Network;
Comment[en_GB]=TeamSpeak Voice Communication Client
Comment=TeamSpeak Voice Communication Client
Exec='/my/system/path/to/TeamSpeak' --ozone-platform=x11 %u
GenericName[en_GB]=
GenericName=
Icon=teamspeak-client
MimeType=
Name[en_GB]=TeamSpeak
Name=TeamSpeak
Path=
StartupNotify=false
StartupWMClass=TeamSpeak
Terminal=false
TerminalOptions=
Type=Application
Version=1.0
X-KDE-SubstituteUID=false
X-KDE-Username=
- Teamspeak Version: v6.0.0-beta8.
- Kernel: 6.1.161-1-MANJARO (64-bit)
- WM: x11 and wayland
- KDE Plasma: 6.5.5
