I am not sure where to get this question answered. Due to a number of Zoom bombers, when we begin a Zoom session we turn off the chat feature and we advise participants if they have a question to raise their hand. At this .1 of the co-host response back via chat to that individual and asked them how can we help? Since Chat is turned off, as a co-host will be see my message and will they be able to respond back to me while chat is off or do I have to enable chat for the host and co-host in order to communicate.

Hi,

I'm using Zoom 5.17.5 (2543) on Linux kernel 6.5.0-17 (distro: Kubuntu 23.10). The problem occurs in both X11 and Wayland.  After starting Zoom, if I share the screen and then subsequently view another shared screen, I can zoom in and out, but can't pan (move around the zoomed-in shared screen). There is no response when trying to do this. This problem has been present for years as far as I know.

If I try panning a shared zoomed-in screen before sharing my own screen, everything works fine.

After the problem occurs, I can't get this function back until I shut down Zoom and start it again. From then on, I have this function back until I share my own screen again and then the same problem reoccurs.

The problem doesn't occur in Windows.

Regards.

Hello,

We are an online school and online classes are done via zoom meetings. All the meetings are automatically recorded and saved in the zoom cloud. We have had some issues with some kids misbehaving by direct messaging each other.

In a meeting, a participant can DM to others. However, it looks like a supervisor can not see the chat log from a recorded video/data unless it is a general conversation.

Is there a way we can check direct messages between participants?

Thank you.

This problem started for me on Dec. 31, 2022, it had never occurred before.

I uninstalled and reinstalled the app.

I've updated to most recent Zoom Version: 5.13.5 (14826)

I've updated to OS Ventura 13.1

I should note that the flickering problem only happens when I hit "play" to get the full presentation. The screen shares my view just fine.

I have a newly built PC and Zoom has microphone issues with it. Randomly during a call I will get a message from Zoom that my microphone is no longer working. This can happen between 5 and 20 minutes into a call, and can happen several times during a call.

However, the microphone is working fine. I have other apps which us the microphone for hours without issue (e.g., TeamSpeak, Discord, Steam, etc.). Even in Zoom, when this problem occurs, I can switch the audio to the microphone in question and Zoom sees the microphone as working again. I end up switching the microphone from "Same as System" to "Logitech StreamCam" (which is what the system is using), back and forth, which re-enables the microphone in Zoom.

It is not the microphone that is not working - Zoom for some reason seems to think it is not working. The microphone is part of my Logitech StreamCam - my video never goes out, the camera and microphone are still in Device Manager, the system still sees everything fine, it is just Zoom that has the issue.

I am not using Logitech G Hub to manage the StreamCam - rather, I use Windows itself. Windows has minimal settings (format of 2 channels, 16bit, 48000Hz). I have tried configuring the microphone Advanced properties to no longer allow applications to take exclusive control of the device, but this setting does not seem to matter.

My system is running Windows 11 23H2 patched to current levels and Zoom (currently 5.16.6 24712) is also running the current version. My system has an AMD Ryzen 9 7950X3D CPU with 64GB of RAM. I have researched this issue online and found no fix - several others who experienced the issue also have AMD-based processors.

Again, the microphone works perfectly fine on the system. Every other application is able to use the microphone for hours. The mic is built-in to my StreamCam, and I do not lose video when this occurs, only the mic.

Additionally, this same exact webcam worked perfectly on my old Windows 10 system. The issue seems to be with Zoom and the new system.