Zoom Workplace crashes when accessing Settings under Linux Mint Cinnamon

[Zapfenzieher]

I have 2 machines running Zoom Workplace (v6.6.10) under Linux Mint (v22.2) Cinnamon (v6.4.8) and a 3rd running Windows 10 (22H2 b19045). On the Windows machine, I can open the Settings window and access all of the dialogs (video, audio, etc.). Under Linux (both machine), trying the same thing causes Zoom Workplace to crash and require restarting, regardless of whether the Settings are invoked via the gear wheel icon or from the Settings entry in the User menu. All 3 machines are 64-bit laptops of varying vintage and manufacture.

One of the Linux machines  has an external monitor and webcam attached; the other does not. The first one has only a touchpad; the 2nd has both touchpad and (wireless) mouse. There's no difference in the behaviour I've noted above; both crash Zoom immediately on trying to access or change Settings. 

Zoom Workplace under Windows was installed a few years ago via the downloaded installer app. Under Linux (both installations), I used Mint's Software Manager to install Zoom from the repository with no changes to the default location or settings. One of these machines has had Zoom for a couple of years (running on an HDD); one was freshly installed last summer following a clean Linux installation (complete overwrite of the SSD).  

I can't seem to find anything online about this particular problem, but because it's affecting both of my Linux-based machines, it's either something I'm doing or something that affects a Linux Mint Cinnamon installation specifically. Anyone else with Linux Mint experience out there have any suggestions on where to look next?

Thanks!

[west_richmond]

We are having the same issue, on Linux Mint 22.2 Zara (base: Ubuntu 24.04 noble)

dmesg says:

zoom[8513] trap invalid opcode ip:62a3b18dc151 sp:7ffd989bd728 error:0 in zoom[a9b8151,62a3ad2fc000+c55e000]

This is on an older four-core AMD A6-3650 machine, but Zoom used to work fine on the same machine--with less RAM--under Fedora 43 and many earlier versions. Please advise if anyone has made it past this problem!