Zoom Launch Fails On Raspberry Pi 4

[KitchM]

Confirmations

• [x] I searched for similar bug reports in https://github.com/Botspot/pi-apps/issues and found none were relevant.
• [x] I tried updating Pi-Apps and the issue is still not fixed. How to update Pi-Apps?
• [x] IMPORTANT: I promise to respond to comments on this issue and write a good bug report https://www.softwaretestinghelp.com/how-to-write-good-bug-report/

What happened?

The Zoom install routine does not get zoom working.

Description

:/opt/zoom $ ./ZoomLauncher [BOX64] Dynarec for ARM64, with extension: ASIMD CRC32 [BOX64] Running on Cortex-A72 with 4 cores, pagesize: 4096 [BOX64] Will use hardware counter measured at 54.0 MHz emulating 3.4 GHz [BOX64] Box64 with Dynarec v0.3.3 6f8f37e8 built on Jan 25 2025 06:31:02 [BOX64] Didn't detect 48bits of address space, considering it's 39bits [BOX64] Counted 56 Env var [BOX64] BOX64 LIB PATH: [BOX64] BOX64 BIN PATH: ./:bin/:/usr/local/sbin/:/usr/local/bin/:/usr/sbin/:/usr/bin/:/sbin/:/bin/:/usr/local/games/:/usr/games/ [BOX64] Looking for ./ZoomLauncher [BOX64] Rename process to "ZoomLauncher" [BOX64] Using native(wrapped) libpthread.so.0 [BOX64] Using native(wrapped) libglib-2.0.so.0 [BOX64] Using emulated /usr/lib/box64-x86_64-linux-gnu/libstdc++.so.6 [BOX64] Using emulated /usr/lib/box64-x86_64-linux-gnu/libgcc_s.so.1 [BOX64] Using native(wrapped) libc.so.6 [BOX64] Using native(wrapped) ld-linux-x86-64.so.2 [BOX64] Using native(wrapped) libdl.so.2 [BOX64] Using native(wrapped) libutil.so.1 [BOX64] Using native(wrapped) librt.so.1 [BOX64] Using native(wrapped) libbsd.so.0 [BOX64] Using native(wrapped) libm.so.6

What are your system specs (run the following command in your terminal)?

This is a Raspberry Pi 4 with the latest RPi Bookworm OS.  Your command does nothing on that system.

(Recommended) Error log? Terminal output? Debug messages?

[github-actions[bot]]

Hello there 👋 Thanks for submitting your first issue to the Pi-Apps project! We'll try to get back to you as soon as possible. In the meantime, we encourage you join our Discord server, where you can ask any questions you might have.

Please respond as soon as possible if a Pi-Apps maintainer requests more information from you. Stale issues will be closed after a lengthy period of time with no response.

[Botspot]

This returns nothing on your system?? ~/pi-apps/api get_device_info

[Botspot]

It works for me. I just tried it. You appear to be running Zoom correctly. Does the command ever return you to the :/opt/zoom $ prompt, or does the process seem to stay running forever? Does your CPU usage increase at all when running Zoom?

Try deleting any configuration and running it again:

rm -rf ~/.config/zoom.conf ~/.config/zoomus.conf 

[KitchM]

I got the command to work after the rm one above. The output was: OS: Debian GNU/Linux 12 (bookworm) OS architecture: 64-bit Last updated Pi-Apps on: 01/25/2025 Latest Pi-Apps version: 01/26/2025 Kernel: aarch64 6.6.62+rpt-rpi-v8 Device model: Raspberry Pi 4 Model B Rev 1.5 SOC identifier: bcm2711 Machine-id (hashed): 14a7ee2997b131649d22bd186e62b718618da5c8 Serial-number (hashed): 05e6190cc250b23c7ef1a64b10efde51d06c83cc Cpu name: Cortex-A72 Ram size: 7.80 GB Raspberry Pi OS image version: 2024-11-19 Language: en_US.UTF-8

[KitchM]

The commands always return to the place they were run from. The task manager shows it attempting at least four separate instances and then just one, which soon goes away. There is nothing left running after 20-30 seconds or so.

Also, there is never much CPU usage.

[Botspot]

@ptitseb do you see anything unusual about this user's setup? I'm not sure what else to suggest to them.

[KitchM]

If you think it is important, I could certainly start from scratch and reinstall a fresh copy of Raspberry Pi OS (Bookworm).

[Botspot]

If you think it is important, I could certainly start from scratch and reinstall a fresh copy of Raspberry Pi OS (Bookworm).

If you urgently need the issue fixed, that might fix it. Otherwise, please keep this SD card and don't clear it out, because if something is broken on your system and we can fix it, then that solution could help save others some trouble in the future.

[pikardbell]

Hi, I also have the same issue after receiving Pi Apps updates today.

Raspberry Pi 400 output from ~/pi-apps/api get_device_info below:

OS: Debian GNU/Linux 12 (bookworm) OS architecture: 64-bit Last updated Pi-Apps on: 02/08/2025 Latest Pi-Apps version: 02/08/2025 Kernel: aarch64 6.6.74+rpt-rpi-v8 Device model: Raspberry Pi 400 Rev 1.1 SOC identifier: bcm2711 Machine-id (hashed): 4062dccc0fa9623e634643616a9a986911b15736 Serial-number (hashed): f7de494b3b301a8e01cd304b7f4a82c9e2d6fb06 Cpu name: Cortex-A72 Ram size: 3.79 GB Raspberry Pi OS image version: 2024-03-15 Language: en_US.UTF-8

I have also run the rm -rf ~/.config/zoom.conf ~/.config/zoomus.conf command and the same issue remains.

[KitchM]

@Botspot Is there any further news on this issue? Do you need any other information from us?

[Botspot]

I was able to reproduce the launch failure. Opened an issue on the box64 repo: https://github.com/ptitSeb/box64/issues/2351

[KitchM]

Thanks, Botspot. Good job! It is nice to be able to have multiple versions of that computer upon which to test.

I still say it might be an install problem, since your implication is that the install procedure may not have a missing file. But I get your meaning. Good call.

Let's hope the other team can figure out what they missed in their software/platform testing.

Thanks again.