Your Application is broken

Hey ​@Roland Detterbeck

Thank you for raising these concerns. Here's a breakdown of each issue you've mentioned:

Crashes and Freezes on Fedora

There have been recurring reports from Linux users, including Fedora users, of crashes and freezes across multiple Zoom releases. Some issues have been fixed in subsequent updates, while new regressions have also appeared.

To help narrow down the issue, it would be useful to know:

Your Fedora version (e.g., Fedora 42 or 43)

Whether you're using Wayland or X11

Whether you installed Zoom via RPM or Flatpak — packaging differences can affect stability on Linux systems

Stable Release Channel

Zoom does not currently offer a separate Long-Term Support (LTS) desktop client for general Linux users. If your goal is maximum stability, using a version known to work well on your Fedora release rather than always updating to the latest may help.

Application Bloat

Zoom Workplace has expanded beyond meetings to include Chat, Notes, AI Companion, Mail, Calendar, Whiteboard, and other collaboration features. The concern about feature bloat and requesting a more lightweight client is a reasonable product suggestion that can be submitted as a feature request.

Keystroke Interception in the Chat Window

To clarify this concern:

If keyboard shortcuts or typing behavior changes while the Zoom chat window has focus, this has been reported by some users in recent releases and may be a bug worth escalating.

The Zoom desktop client receives keyboard input only when its own window is in focus — there is no evidence of general system-wide keystroke interception.

Could you clarify which behavior you're experiencing — is it only affecting the chat window, or does it affect all typing while Zoom is running in the background? This will help us determine if it's a bug or an expected shortcut feature.

Thanks for the response.

I am using the current Fedora release with all available updates, KDE Plasma on Wayland, and the official Zoom RPM package.

The latest Zoom update has fortunately made the client largely stable again. However, one input-related issue remains: I cannot enter the # character normally in the Zoom chat field. The required key combination appears to be intercepted by the client instead of inserting the character into the message.

To be clear, I am not claiming that Zoom intercepts keyboard input system-wide. This happens inside the Zoom chat window while the message input field has focus. A chat editor should prioritize valid text input over application shortcuts.

This is particularly problematic with non-US keyboard layouts, where characters such as # require key combinations that applications may incorrectly interpret as shortcuts.

Asking for the exact Fedora version may be useful for reproducing a specific regression, but suggesting that users remain on an older “known good” version is not a reasonable long-term solution. Zoom provides an official Fedora RPM, so I expect the current, fully patched Fedora release and its standard Wayland environment to be properly tested and supported.

My original wording was frustrated, but that frustration comes from repeatedly encountering new regressions after updates in an application required for daily work.

We sincerely apologize for the inconvenience. To help our developers pinpoint the issue more accurately, we would like to clarify two points:
- Is the chat window the one within the meeting or a non-meeting chat window?
- Can you successfully type the `#` character into the input field of the search window?
Thank you.

I have also encountered another serious issue with the current client:

Whenever I start a Zoom Phone call, the desktop client crashes completely. The call itself remains active in the background. After restarting the client, I can rejoin the ongoing call.

So the call connection is apparently not terminated, but the entire user interface crashes immediately when the call is started. This happens reproducibly and makes Zoom Phone effectively unusable.