| Git Clone URL: | https://aur.archlinux.org/zoom.git (read-only, click to copy) |
|---|---|
| Package Base: | zoom |
| Description: | Video Conferencing and Web Conferencing Service |
| Upstream URL: | https://zoom.us/ |
| Keywords: | call conference meeting video |
| Licenses: | LicenseRef-zoom |
| Submitter: | edh |
| Maintainer: | edh |
| Last Packager: | edh |
| Votes: | 661 |
| Popularity: | 8.25 |
| First Submitted: | 2015-08-15 13:18 (UTC) |
| Last Updated: | 2024-09-15 14:44 (UTC) |
@thuchuc, if you are a gnome user, then the problem is likely that zoom abuses the screensharing mechanism under wayland, and by default, gnome will not allow the security violation. The workaround is to use lookingglass (ALT-F2 --> lg) and set this variable to true in the console:
global.context.unsafe_mode = true
It works, but you have to do it every login.
Hello everyone. It seems that I've lost the ability of sharing the screen in zoom. From what I'm reading it may be a problem of Gnome but I wanted to at least point this out here. Is anyone experiencing this issue?
@tsujigiri_nin Thanks for reporting this to Zoom. Zoom is definitely the problem. I have tried using the Zoom Test meeting on two different Debian based systems. The test meeting crashed on both devices.
@lifestronaut, @RFSharpe - glad it's not just me. Fwiw I submitted a zoom bug report after trying another clean build and getting the same issue. Hopefully it might get fixed...
@tsujigir_nin I had the same continuously scrolling "Zoom cannot detect your microphone" message today during a Zoom meeting. I am using EndeavourOS. My headphones are plugged in using the separate mini stereo jacks for speakers and microphone. Rebooting and rebooting with mic not plugged in did not remedy the situation for me. Output of "inxi -A"
Audio: Device-1: Intel 6 Series/C200 Series Family High Definition Audio driver: snd_hda_intel Device-2: AMD Cedar HDMI Audio [Radeon HD 5400/6300/7300 Series] driver: snd_hda_intel Sound Server-1: ALSA v: k5.16.2-arch1-1 running: yes Sound Server-2: PulseAudio v: 15.0 running: yes Sound Server-3: PipeWire v: 0.3.44 running: yes
After the meeting I went to the Zoom Test site. I could not do any further troubleshooting because the Zoom crashed after when I attempted start a test Zoom meeting. No error messages were displayed.
Hi there, does anybody know how to get Zoom's configuration files to be stored in ~/.config? I was hoping that the installation would respect XDG_CONFIG_HOME but it didn't.
@tsujigir_nin - I am experiencing the same issues. It doesn't appear to happen if I join with my mic plugged in, but it will happen if I disconnect my mic during the call or join without a mic. The only remedy I found is to reboot. Exiting zoom and restarting it yields the same unending cascade of notifications
Has anyone had issues with cascading/unstoppable 'Zoom cannot detect your [e.g.] microphone' messages on the 01/25 release? These cascading notifications prevented clicking any zoom buttons and continued after using keyboard shortcuts to exit the meeting. For me they occurred if I enter a meeting with the mic not set up (e.g. I forgot to plug it in). Zoom works as normal provided my mic is connected and configured in my system prior to joining a call. Weirdly, I don't get any notifications if I disconnect the mic during a zoom call.
Hi, does anyone know if Zoom unofficially supports any HID devices on Linux, for mute/unmute on a Jabra 410 speakerphone to mute/unmute in Zoom? Support says HID is only supported for macOS and Windows. I sent them a support request just now, asking here because not sure their support will actually know if there is anything under the hood.
Update: I opened a thread here too on this > https://community.zoom.com/t5/Meetings/HID-Support-for-Linux/td-p/32775
Pinned Comments
arash-m commented on 2024-09-15 15:56 (UTC)
Tested 6.2.0-1. Sharing works for me, but it still crashes after stopping. The workaround for me is still downgrading pipewire and libpipewire to 1.0.7 before meetings.
a172 commented on 2022-06-13 14:25 (UTC) (edited on 2022-06-13 14:25 (UTC) by a172)
@edh - That's not the answer I was hoping for (I was really hoping we could get it to launch without xwayland), but at least I know I'm not missing something.
Some
~/.config/zoomus.confupdates:qt5-webengineinstalled, and theebeddedBrowserForSSOLoginline doesn't exist in my configzoomus.conf. SSO login works just fine (issues with Firefox containers aside).pipewire-pulse.system.audio.typedefaulted toalsafor me (or I changed it without realizing it). I probably could have installedpipewire-alsaand fixed my issues, but I setsystem.autio.type=pulse(a lucky guess) and this worked. This should work for anyone using straight PulseAudio as well.If anyone finds documentation on
~/.config/zoomus.conf, please let us know.edh commented on 2016-08-26 11:03 (UTC) (edited on 2017-03-09 10:48 (UTC) by edh)