TeamSpeak crashing when trying to set a hotkey

If you install the new Teamspeak (I’m currently running version 5.0.0-beta66) on a Mac system (I’m using the new MacBook Pro 14" with M1 Pro on macOS Monterey version 12.0.1; without any external microphone or something else), add a whisper list and try to configure the hotkey, then the app crashes once you press any key.

Did I finally found a bug and became a worthy beta tester? :smiley:


We can reproduce this issue. This seems to happen with any hotkey (ptt or whisper etc).

Yes, sir, you have proven your worth!


moved by moderator

When I try to configure a keyboard shortcut for Whisper, the client closes.

  • macOS Monterey 12.0.1
  • MacBook Pro (13-inch, M1, 2020)
  • TeamSpeak version: 5.0.0-beta67
    Build Number:
    Build Date:
    12/1/2021, 2:58:21 PM
    Chromium Version:

Teampeak5 crashes when you want to select a button for Push to Talk.

1 Like


Please post a log and crashdump if available.

Do you have any other devices connected?


Thread 56:
0 ??? 0x7ff89292a940 ???
1 libsystem_kernel.dylib 0x7ff80246b506 __psynch_cvwait + 10
2 TeamSpeak 0x1049d65cc 0x104991000 + 284108
3 TeamSpeak 0x10525faca 0x104991000 + 9235146

Full Report

Ok that’s not what I asked for.

I mean a client log or crash dump. The error report is mostly not helpful.

Ps you can put massive text in a text document and attach it if needed.


sorry I have no other report

Maybe I can help :slight_smile:
I’ve got this error every time while trying to bind a key for toggle Microphone out other functions.

But I’m not able to upload a txt file or paste the whole crashlog (more than 128k chars).

You don’t have to.
We can reproduce this, but i forgot to merge this report to an existing thread.


moved by moderator

As the title says, Teamspeak crashes when trying to assign a hotkey for PTT. My specs are below, I also have a crash log if anyone needs that.

MacBook Pro 13-inch, M1, 2020
MacOS Ventura 13.0 Beta (22A5266r)
TeamSpeak 5 Beta

Teamspeak 5.0.0 beta 70 crashes while attempting to set PTT button on Mac

Macbook Pro 15-inch, Intel, 2016
MacOS Monterey 12.4

Build Number: 1654676785
Build Date: 6/8/2022, 10:26:25 AM
Chromium Version: 100.0.4896.127
ts5 beta 70 crash report

1 Like

Hi, I have the same problem. When I want to chose what key I want for push to talk the app closes. I’m currently running version 5.0.0-beta70.
And my computer is a macOS Monterey version 12.5.

How do I fix this?

Bump, still getting this crash when attempting to set a hotkey. This has been going on for as long as I can remember, would be nice to get this resolved in one of the next releases.

> * macOS Monterey 12.5.1
> * Version: 5.0.0-beta70
> * Build Number: 1654676785
> * Build Date: 6/8/2022, 4:26:25 AM
> * Chromium Version: 100.0.4896.127

1 Like

Also see a crash when setting a PTT key in Teamspeak Version: 5.0.0-beta70 running on MacOS Ventura 13.0. The crash is 100% reproducible. Crash Report here. The crash occurs instantly when you press any key when the app tells you to “Press Key Combination” in the Key Bindings screen.

I have ensured Teamspeak is enabled in System Settings > Privacy & Security for Input Monitoring (I have disabled and re-enabled it with no effect.)

My usage (VoIP radio) requires PTT - is there any workaround for this?

@TS.ChrisR a year has passed since the problem was reported, but it is still relevant. When do you plan to fix it?

After all, in the app for Windows there is no such problem.


agreed, pretty annoying it’s been reported for this long, but still no fix.
I don’t normally use hotkeys on Windows, but for macOS I would (if I could)… due to the types of microphones I use while using teamspeak on macOS picking up everything because of the environment I’m in… television, etc…

please just fix this already guys!

12 nov 2023 (almost 2 years later)
macbook air m1
macos Sonoma 14.0 (earlier 13.x)
teamspeak 5.0.0-beta76 (earlier beta75)

still crashes when trying to assign a hotkey… same as sssoviet

if there are logs or reports that can help you? please tell me their location


Please fix this.