Keyboard input not accepted - Mac OS Sequoia

[zippythecat]

The issue

I can't get Mumble 1.5.735 to accept keyboard input at all. Have checked the Accessibility and Security settings, have deleted and installed the client, nothing is working. Using a Logitech MX Keys bluetooth keyboard that is otherwise working correctly in all respects with other programs.

It would bloody well help if keyboard shortcuts carried over from one update to the next, but they don't and never have. So every time I update I have to re-create my shortcuts and without a fix for the above that's impossible.

Mumble version

1.5735

Mumble component

Client

OS

macOS

Additional information

No response

[Krzmbrzl]

Have you explicitly removed accessibility access for Mumble and re-granted it afterwards?

[github-actions]

As there has been no activity on this issue for a couple of days, we assume that your issue has been fixed in the meantime.
Should this not be the case, please let us know.

If no further activity happens, this issue will be closed within 3 days.

[Oclair]

Please fix this bug, its horrible, I hate it, Mumble is not signed, just bad bad bad

It's been quite a long standing bug, it is not a support request

[davidebeatrici]

Who said Mumble is not signed? We are signing releases with our own GPG key.

On Windows we are additionally signing binaries through SignPath, there is no equivalent service for macOS as far as we know.

[Oclair]

Who said Mumble is not signed? We are signing releases with our own GPG key.

Mac OS
https://www.youtube.com/watch?v=zZEBE4b_xiQ

On Windows we are additionally signing binaries through SignPath, there is no equivalent service for macOS as far as we know.

Huh?
https://developer.apple.com/developer-id/

[Krzmbrzl]

Huh?
https://developer.apple.com/developer-id/

They don't provide any service. They sell you a 100$ per year subscription with which you are still on your own when it comes to figuring out how to get signing done. We tried that for quite some time but couldn't get it to work. And since nobody in the core team uses (or owns, for that matter) a Mac, we gave up on it.
Anyway, this is off-topic for the present issue. Have a look at #4263 and #5815

[Oclair]

You just figured this out now?

Before you wrote that how Windows signs apps and there is nothing available for mac os...

Push to Talk is Broken on Mac OS

This is a Bug report not a support request.
Have a nice day!

[davidebeatrici]

They sell you a 100$ per month subscription

It's per year, but still a scam.

You just figured this out now?

No, we figured it out as soon as notarization became mandatory and running unsigned apps became a several steps workflow.

Before you wrote that how Windows signs apps and there is nothing available for mac os...

SignPath signs our binaries and it's a third-party service. On macOS you're on your own, along with expenses.

But this is not about just signing anymore. Notarization means sending binaries to Apple who replies with a confirmation that is then attached to the files.

This makes a release workflow unnecessarily more complex and also inefficient.

Push to Talk is Broken on Mac OS

This is a Bug report not a support request.

You're the one who brought up signing in the first place. Do you perhaps mean there is a correlation between accessibility permissions not working and the unsigned binary?

[Oclair]

If it were any other type of innocuious app I would be completely sympathetic, but Mumble takes over core system automations deep into the system and every user including mac ones deserves no less but full verification and competent assurance this app is safe and runs correctly. At the moment the core developers have "given up on that".

And Voilla, I come here NOT because the app is not signed, but because They gave up and continue to release broken mac support.

[Krzmbrzl]

Simple solution then: stop using Mumble. Clearly, it only makes you miserable so please switch to using something else that works to your satisfaction.

Anyway: this has completely derailed the current issue. Any further comments towards that direction that aren't closely linked to the original topic of this issue will be deleted. If you want to continue the discussion, go ahead and create a separate issue or use GitHub's discussion feature.

[bikefish2]

Hello,

I'm having the same issue. After updating to 1.5.857, attempting to add or modify any entries under the Shortcuts tab of configuration no inputs of any type are detected. Existing shortcuts do not work. This has continued through multiple attempts at disabling and reenabling the options Mumble requests under Privacy & Security in macOS settings.

For the first time opening Mumble Configuration after launching Mumble, I am prompted to enable the Screen & System Audio Recording settings toggle. This happens whether or not the toggle is enabled or disabled prior to starting Mumble. I have not been prompted to reenable the toggle under Accessibility.

Mumble version
1.5.857

Mumble component
Client

OS
macOS Tahoe 26.0.1 (26.0.0 as well)

Additional information
None

[Krzmbrzl]

This has continued through multiple attempts at disabling and reenabling the options Mumble requests under Privacy & Security in macOS settings.

Does this include accessibility permissions?