Sorry @ilikelinux, I meant to respond to you, too. This is a clean install, no upgrade from 33; although, I had installed the 34 beta. Do you think that could be the root of the issue?
2 Likes
Yes, so you have same situation as me, i had some issues with sound and could solve them this way. It is a incompatibility with the config files. Copy them away to have a backup if you had a special setting.
2 Likes
Still doesn’t work for me…
1 Like
PuluseAudio ? 
2 Likes
Right?
I’ve contacted Zoom support to see if they have any ideas because I’m out of them.
2 Likes
Okay, on a whim I removed the official Zoom package (from them) and installed the flatpak via Software. Upon initial launch it complained that “screen sharing” wasn’t enabled for Wayland, but after a quick app restart, boom, audio share works flawlessly.
This isn’t a fix, as the issue with the official package persists, though.
2 Likes
Yes odd… I’m using X rather than Wayland, so that may explain the different experience.
1 Like
One of my suspicions was it could be either Wayland or some selinux issue, since I had plenty of those with any openvpn setting not from cli.
1 Like
That’s very odd. I’m using the zoom rpm from upstream, on Wayland, on F34 without any issues 
The version you’re using is newer than mine, though. So perhaps the new version includes a regression? What version is the FlatPak?
1 Like
Right?
The flatpak version is the same as the official client from Zoom themselves.
2 Likes
That’s even weirder 
I’ll test out the new version later and see what I get. May not be before the weekend though, since I don’t want to risk breaking zoom. Lots of meetings this week! 
1 Like
I’m successfully using the latest zoom
$ rpm -q zoom
zoom-5.6.16888.0424-1.x86_64
(with X)
$ inxi -A
Audio: Device-1: Intel 100 Series/C230 Series Family HD Audio driver: snd_hda_intel
Device-2: NVIDIA GK107 HDMI Audio driver: snd_hda_intel
Sound Server-1: ALSA v: k5.12.2-300.fc34.x86_64 running: yes
Sound Server-2: PipeWire v: 0.3.27 running: yes
2 Likes
Thank you both for your perseverance…
2 Likes
I’m encountering similar problems, and am hoping for help isolating the issue.
After updating from Fedora 32 to Fedora 34, Zoom crashes when trying to connect to audio when joining an external meeting.
The crash occurs when attempting to connect to audio for an external meeting. The window where the connection is made and confirmed grays out, and then the program crashes. If I join with “do not connect to audio” checked, or if I start a local meeting, things are fine, but it will then crash if I try to try to connect to audio while in the meeting.
A crash does NOT occur if I first run killall pulseaudio (which I was using as a quick fix for audio issues in Fedora 32), but the problem persists on reboot.
killall pulseaudio returns a toast message with an audio icon, and the text: “Raven/Raven2/Fenghuant HDMI/DP Audio Controller Digital Stereo (HDMI)”
I have uninstalled and reinstalling zoom from their site, and reinstalled pipewire per the link above.
Any advice on preventing pulseaudio from crashing Zoom (if that’s what’s happening) permanently is appreciated. Thanks!
Welcome to the ask Fedora community @lawsonkight.
Please give us the following infos:
uname -a
rpm -q zoom
inxi -A
I also use Zoom and I do not have this crash.
Have to mention that my DE is Mate, so i don’t have Wayland running.
Thanks for taking a look.
$ uname -a
Linux localhost.localdomain 5.12.9-300.fc34.x86_64 #1 SMP Thu Jun 3 13:51:40 UTC 2021 x86_64 x86_64 x86_64 GNU/Linux
$ rpm -q zoom
zoom-5.6.22045.0607-1.x86_64
$ inxi -A
Audio:
Device-1: AMD Raven/Raven2/Fenghuang HDMI/DP Audio driver: snd_hda_intel
Device-2: AMD Family 17h HD Audio driver: snd_hda_intel
Device-3: Logitech Webcam C270 type: USB driver: snd-usb-audio,uvcvideo
Sound Server-1: ALSA v: k5.12.9-300.fc34.x86_64 running: yes
Sound Server-2: PulseAudio v: 14.2-rebootstrapped running: yes
Sound Server-3: PipeWire v: 0.3.30 running: yes
EDIT:
My computer received updates for ALSA and Pipewire this morning. The output for inxi -A (below) has changed as a result, and Zoom is successfully connecting to audio, so I’ll consider this case resolved.
$ inxi -A
Audio:
Device-1: AMD Raven/Raven2/Fenghuang HDMI/DP Audio driver: snd_hda_intel
Device-2: AMD Family 17h HD Audio driver: snd_hda_intel
Device-3: Logitech Webcam C270 type: USB driver: snd-usb-audio,uvcvideo
Sound Server-1: ALSA v: k5.12.9-300.fc34.x86_64 running: yes
Sound Server-2: PulseAudio v: 14.2-rebootstrapped running: yes
Pipewire has a pulse_audio plugin, so sound Server PulseAudio is not needed anymore. Since Fedora 34 uses Pipewire as default Sound Server. I guess you are missing pipewire-pulsaudio ?!
Have a look here Changes/DefaultPipeWire - Fedora Project Wiki
2 Likes
According to the Zoom tech I corresponded with, Zoom only works with pulseaudio and not the pipewire-pulseaudio “adapter.”
Their engineers, apparently, are not “well-versed in Linux.”
Let me provide some additional context… I contacted Zoom support shortly after posting this and over the course of several weeks, their support technician with whom I was working confirmed from their “engineers” that because there are “too many Linux variants to account for” they really don’t support it. When I pointed out they offer both a .deb and an .rpm version, so they should at least support the distributions that use those kinds of packages, it was kind of dismissed.
As an interesting side-note, I did get it working by installing the flatpak, but I believe the current version installable by flatpak is broke because it keeps crashing on my system.
When I pointed out the tech that if the pipewire-pulseaudio “bridge” wouldn’t work, like the “engineer” said it wouldn’t, then the flatpak shouldn’t have worked either.
2 Likes
As others have noted, it works fine here with Wayland and pipewire on a Fedora 34 system when installed using the RPM. So we (and zoom devs) have not yet isolated the issue here from the looks of it. I’d go back to square 1 and start with logs etc. Maybe someone could try a F34 live image and see if it works there? There are updated Live images here:
1 Like
Interesting…
I installed the rpm directly from Zoom and an even more up-to-date one from the tech himself and neither worked.
The tech I corresponded with tried it on a live image and it wouldn’t work there either.
To be honest, their “customer service” was solid–i.e., incredibly willing to work on the problem and push it up the food chain–but tech support was incredibly dismissive.