Zoom Support for Raspberry Pi 4 and Ubuntu Server 19.01 Desktop

[Botspot]

BTW I have submitted a request to Zoom for them to fix the Chrome app.

2020-04-09-125102_1280x1024_scrot.png (116.81 KiB) Viewed 1297 times

[zooropean]

BTW I have submitted a request to Zoom for them to fix the Chrome app.
2020-04-09-125102_1280x1024_scrot.png

Thank you very much.

I had thought about this but wasn't sure they would have it fixed by the time I need to return my RPI4 for a refund.

[hippy]

Don't know if this helps explain anything but it's what I see when the Zoom Chrome App is launched from the command line. Shows all this before offering the Join/Sign-in screen, nothing added when one clicks join and it gives the forever spinning "Connecting..."

Code: Select all

pi@Pi3B:~ $ /usr/bin/chromium-browser --profile-directory=Default --app-id=hmbjbjdpkobdjplfobhljndfdfdipjhg

 --disable-quic --enable-tcp-fast-open --ppapi-flash-path=/usr/lib/chromium-browser/libpepflashplayer.so --ppapi-flash-args=enable_stagevideo_auto=0 --ppapi-flash-version=
libEGL warning: DRI2: failed to authenticate
[5075:5215:0409/195742.646412:ERROR:object_proxy.cc(632)] Failed to call method: org.freedesktop.DBus.Properties.Get: object_path= /org/freedesktop/UPower: org.freedesktop.DBus.Error.ServiceUnknown: The name org.freedesktop.UPower was not provided by any .service files
[5075:5215:0409/195742.648050:ERROR:object_proxy.cc(632)] Failed to call method: org.freedesktop.UPower.GetDisplayDevice: object_path= /org/freedesktop/UPower: org.freedesktop.DBus.Error.ServiceUnknown: The name org.freedesktop.UPower was not provided by any .service files
[5075:5215:0409/195742.649680:ERROR:object_proxy.cc(632)] Failed to call method: org.freedesktop.UPower.EnumerateDevices: object_path= /org/freedesktop/UPower: org.freedesktop.DBus.Error.ServiceUnknown: The name org.freedesktop.UPower was not provided by any .service files
[5129:5129:0409/195743.537371:ERROR:sandbox_linux.cc(369)] InitializeSandbox() called with multiple threads in process gpu-process.

Anyone know how to run a Chrome App with 'sudo' ? Tried that on the off-chance but it complained about root and no '--no-sandbox'. Added that and it opened a normal browser page with a pop-up and "You are using an unsupported command line flag: --no-sandbox".

[Botspot]

Don't know if this helps explain anything but it's what I see when the Zoom Chrome App is launched from the command line. Shows all this before offering the Join/Sign-in screen, nothing added when one clicks join and it gives the forever spinning "Connecting..."

None of those errors look app-specific. If you ran plain chromium-browser in the terminal, you would still get those errors.

Anyone know how to run a Chrome App with 'sudo' ? Tried that on the off-chance but it complained about root and no '--no-sandbox'. Added that and it opened a normal browser page with a pop-up and "You are using an unsupported command line flag: --no-sandbox".

Keep in mind that a chrome app is just a html page with some added privileges.
Chromium is absolutely not intended to be run as root user for security reasons.

IMO, the chrome app is behaving as if it had no internet connection. Login times out. Connection waits forever.
It seems like it is failing to establish a connection or something.

I'm going to run the app under strace (a event-level I/O logger) and see if anything turns up.
Edit: strace didn't show anything interesting. Just many repeated calls to ioctl to detect how much time has passed.

[mshirvaikar]

BTW I have submitted a request to Zoom for them to fix the Chrome app.
2020-04-09-125102_1280x1024_scrot.png

Many thanks Botspot!

I filed a support request also but not as well written as yours.

[hippy]

Chromium is absolutely not intended to be run as root user for security reasons.

That's definitely so. I was just trying to move things forwards, temporarily altering the environment with any change in behaviour of the black box software helping to identify the underlying issue.

I was wondering if the problem may be down to the Zoom Chrome App calling or doing something which Linux or Raspbian blocks without root privileges. Running as root and it working would suggest that's the case, it not working would suggest something else is the issue.

Running the Arduino IDE as root got the Raspberry Pi PiDuino framework running That (1) got something which wouldn't otherwise run running, (2) identified the reason why it wouldn't otherwise run, (3) pointed to what needs to change to allow it to run without root privileges.

It seemed worthwhile trying the same for the Zoom Chrome App. Either way it would mean we'd know one more thing than we do now.

[Botspot]

IMO, the problem has something to do with the connection to the server. After all, everything works except login and connecting.
I tried running the app in FydeOS (Chromium OS for RPi), but it didn't work there either. Something must be common with both OSes for both to fail.

It could be the Raspberry Pi & its hardware. I think that's unlikely, since chrome apps are essentially html and javascript, but a possibility.
It can't be Raspbian-related. FydeOS (not raspbian) failed.
It could be the fact that both OS'es use Chromium instead of Chrome. I'm aware of several inconsistencies between the two, including Native Client (that's why the VNC Chrome app doesn't work).

[zooropean]

BTW I have submitted a request to Zoom for them to fix the Chrome app.
2020-04-09-125102_1280x1024_scrot.png

Did you get a response from Zoom yet?

I tried again this morning to use Zoom but this time had my daughter join her class meeting. 1 minute in I had her switch to tablet.

[Botspot]

Did you get a response from Zoom yet?

No, nothing.

[hippy]

It could be the Raspberry Pi & its hardware. I think that's unlikely, but a possibility.

If not an OS issue, then being ARM rather than X86 and/or being Chromium rather than Chrome, would seem to be the two most likely explanations to me.

Perhaps someone could try the Zoom Chrome App under Chromium on Windows. I tried on Windows 7 but get a "WebGL not supported" error when installing - it installed and runs well with Chrome.

Does anyone know where the Zoom Chrome App is stored on disk on a Pi ? I'll keep looking but haven't found it yet.

Code: Select all

pi@Pi3B:~ $ ls -l /home/pi/.config/chromium/Default/Extensions/hmbjbjdpkobdjplfobhljndfdfdipjhg/3.6.4098.303_0/
total 20
drwx------ 5 pi pi 4096 Apr  3 17:42 build
-rw------- 1 pi pi 1906 Apr  3 17:42 manifest.json
drwx------ 2 pi pi 4096 Apr  3 17:42 _metadata
drwx------ 3 pi pi 4096 Apr  3 17:42 _platform_specific
-rw------- 1 pi pi 2181 Apr  3 17:42 policy.json

Code: Select all

pi@Pi3B:~ $ ls -l /home/pi/.config/chromium/Default/Extensions/hmbjbjdpkobdjplfobhljndfdfdipjhg/3.6.4098.303_0/_platform_specific/arm
total 26052
-rw------- 1 pi pi 26674352 Apr  3 17:42 zoom_arm.nexe

[zooropean]

It could be the Raspberry Pi & its hardware. I think that's unlikely, but a possibility.

If not an OS issue, then being ARM rather than X86 and/or being Chromium rather than Chrome, would seem to be the two most likely explanations to me.

Perhaps someone could try the Zoom Chrome App under Chromium on Windows. I tried on Windows 7 but get a "WebGL not supported" error when installing - it installed and runs well with Chrome.

Does anyone know where the Zoom Chrome App is stored on disk on a Pi ? I'll keep looking but haven't found it yet.

Code: Select all

pi@Pi3B:~ $ ls -l /home/pi/.config/chromium/Default/Extensions/hmbjbjdpkobdjplfobhljndfdfdipjhg/3.6.4098.303_0/
total 20
drwx------ 5 pi pi 4096 Apr  3 17:42 build
-rw------- 1 pi pi 1906 Apr  3 17:42 manifest.json
drwx------ 2 pi pi 4096 Apr  3 17:42 _metadata
drwx------ 3 pi pi 4096 Apr  3 17:42 _platform_specific
-rw------- 1 pi pi 2181 Apr  3 17:42 policy.json

Good idea-like you I tried it on Chrome in Win10 and the Chrome app works fine.

[Botspot]

I may have just found something: in chrome://extensions, enable "Collect Errors" for Zoom.
Then attempt to login.
This appears:

2020-04-14-115351_1280x1024_scrot.png (20.35 KiB) Viewed 1060 times

[zooropean]

I may have just found something: in chrome://extensions, enable "Collect Errors" for Zoom.
Then attempt to login.
This appears:2020-04-14-115351_1280x1024_scrot.png

Do you think there's a workaround?

Thank you!

[zooropean]

It could be the Raspberry Pi & its hardware. I think that's unlikely, but a possibility.

If not an OS issue, then being ARM rather than X86 and/or being Chromium rather than Chrome, would seem to be the two most likely explanations to me.

Perhaps someone could try the Zoom Chrome App under Chromium on Windows. I tried on Windows 7 but get a "WebGL not supported" error when installing - it installed and runs well with Chrome.

Does anyone know where the Zoom Chrome App is stored on disk on a Pi ? I'll keep looking but haven't found it yet.

Code: Select all

pi@Pi3B:~ $ ls -l /home/pi/.config/chromium/Default/Extensions/hmbjbjdpkobdjplfobhljndfdfdipjhg/3.6.4098.303_0/
total 20
drwx------ 5 pi pi 4096 Apr  3 17:42 build
-rw------- 1 pi pi 1906 Apr  3 17:42 manifest.json
drwx------ 2 pi pi 4096 Apr  3 17:42 _metadata
drwx------ 3 pi pi 4096 Apr  3 17:42 _platform_specific
-rw------- 1 pi pi 2181 Apr  3 17:42 policy.json

Good idea-like you I tried it on Chrome in Win10 and the Chrome app works fine.

Ok I installed Chromium on my Win10 machine. Then added the Zoom Chrome App.

I am able able to join Zoom calls or start them with no issues.

[zooropean]

I may have just found something: in chrome://extensions, enable "Collect Errors" for Zoom.
Then attempt to login.
This appears:2020-04-14-115351_1280x1024_scrot.png

From Win10:

{
"app": {
"background": {
"scripts": [ "build/js/background.js" ]
}
},
"description": "Zoom Cloud Meetings for Chrome",
"externally_connectable": {
"matches": [ "*://*.zoom.us/*", "*://*.zoomgov.com/*", "*://*.zoomdev.us/*", "*://*.zoom.com/*" ]
},
"icons": {
"128": "build/static/images/zoom-logo-128.png"
},
"key": "MIIBIjANBgkqhkiG9w0BAQEFAAOCAQ8AMIIBCgKCAQEAjXFAHp3jJP5VXqg4Zcvhw20dD7vDIPB6HGUbrIpQB4sRHWB0PwVKqpllNVuwvd6gRNOeMvgdFt9VRYT8knUZ0gR1pRaaOw+gQ5iPh4f2kdwJ83+nHIdvBSs4oNDm3rZvjZrR9603sNgCQGOZUtMnJAe1qCZY0SFBL7H9nQR6G6VFcpdYEs9ybyqnZ8M/RRkCxen3fwODmN1nGvas9AeyFS5+6M+LDteDt+LGjoSR7l6L60UIxgoExnJ4/urlqZHgM3JzZWAy/ZWi15ew/D6YOklgbB6VDkr1uNAGvlVVSaVKauGK6UZ6yaFzXtLKyyFxlIIKLpXonpM4bAIDoLwdBwIDAQAB",
"manifest_version": 2,
"minimum_chrome_version": "52.0.0.0",
"name": "Zoom",
"offline_enabled": false,
"permissions": [ {
"fileSystem": [ "write", "directory" ]
}, "storage", "alwaysOnTopWindows", "audioCapture", "desktopCapture", "videoCapture", "unlimitedStorage", "system.cpu", "system.memory", "system.display", "power", {
"socket": [ "tcp-connect", "resolve-host", "udp-bind::*", "udp-send-to:*:*", "resolve-proxy" ]
}, "*://*.zoom.us/*", "*://*.zoomgov.com/*", "*://*.zoomdev.us/*", "*://*.zoom.com/*", "webview", "idle" ],
"platforms": [ {
"nacl_arch": "x86-64",
"sub_package_path": "_platform_specific/x86-64/"
}, {
"nacl_arch": "x86-32",
"sub_package_path": "_platform_specific/x86-32/"
}, {
"nacl_arch": "arm",
"sub_package_path": "_platform_specific/arm/"
} ],
"requirements": {
"3D": {
"features": [ "webgl" ]
}
},
"storage": {
"managed_schema": "policy.json"
},
"update_url": "https://clients2.google.com/service/update2/crx",
"version": "3.6.4111.0413",
"version_name": "3.6.5 (4111.0413)"

[hippy]

Ok I installed Chromium on my Win10 machine. Then added the Zoom Chrome App.

I am able able to join Zoom calls or start them with no issues.

Thanks for the info. That would seem to narrow it down to the Chromium build for ARM or the Pi being ARM.

BTW : Your manifest.json appears to be the same on the Pi as Win 10 ( looked at, not binary compared ). My Pi auto-updated the Zoom app from 3.6.4098.303_0 to 3.6.4111.413_0 so earlier directory paths are fluid.

[Botspot]

What do you guys think, should we ask a mod to move this topic to General Discussion? I don't see anything Ubuntu related about it, and General Discussion is much more popular. Maybe we could get some more users on board trying to fix this!

[Botspot]

I think I've found the problem:
Those two java scripts causing the errors mention NaCl extensively. NaCl is an API that Raspbian's chromium does not support IIRC. Same reason why the VNC Viewer Chrome App doesn't work in Raspbian.

According to Wikipedia, NaCl is:

a sandboxing technology for running either a subset of Intel x86, ARM, or MIPS native code, or a portable executable, in a sandbox.

And it turns out there is ARM native code shipped with Zoom: _platform_specific/arm/zoom_arm.nexe.

I cracked it open using hexedit, and sure enough:

Screenshot from 2020-04-14 20-20-27.png (237.64 KiB) Viewed 961 times

So I think that pretty much settles it. As hippy said, "That would seem to narrow it down to the Chromium build for ARM or the Pi being ARM."

[hippy]

So I think that pretty much settles it.

Yup; I think we're at the end of the road with the Zoom Chrome App. We either need to provide NaCl for Chromium, build a Chrome for ARM, or find some other way to run Chrome on a Pi. Exagears apparently used to but that's gone. There may be some other means of emulation but I would expect any emulation to give poor performance. Otherwise it's in the hands of Zoom to produce a native ARM app.

Perhaps the Foundation could apply pressure on Zoom to get that done, maybe even partner with them to do it. Because, like it or not, the best recommendation for anyone wanting or having to use Zoom during this current crisis seems to be "use Windows".

[rpdom]

So I think that pretty much settles it.

Yup; I think we're at the end of the road with the Zoom Chrome App. We either need to provide NaCl for Chromium, build a Chrome for ARM, or find some other way to run Chrome on a Pi. Exagears apparently used to but that's gone. There may be some other means of emulation but I would expect any emulation to give poor performance. Otherwise it's in the hands of Zoom to produce a native ARM app.

Perhaps the Foundation could apply pressure on Zoom to get that done, maybe even partner with them to do it. Because, like it or not, the best recommendation for anyone wanting or having to use Zoom during this current crisis seems to be "use Windows".

I'm probably taking rubbish here (just ignore me if I am) as I don't run chromium browser on a Pi, but would the "libsodium23" package in Buster provide the needed NaCl api?

[Botspot]

would the "libsodium23" package in Buster provide the needed NaCl api?

I highly doubt it. On my raspbian, it's already installed by default.

[hippy]

Just a FYI; no joy for me with the Zoom Chrome App using "Debian Buster with Raspberry Pi Desktop: The Raspberry Pi Desktop OS for PC and Mac - based on Debian Buster" on my AMD64 PC. Reports "Not compatible" using Chromium, "WebGL not supported" when installing with Chrome.

[zooropean]

Sigh well thank you for all of the work everyone.

I guess the focus should be on trying to improve the video performance of Zoom in Chromium.

[Botspot]

In case anyone missed it in the other Zoom thread, it looks like procount got zoom working on RPi by using Android OS!

I have tried running zoom under Android on the RPi4 4GB.
I installed Konsta's LineageOS 16.0 for the RPi4. Then I installed GAPPS pico to get the Play Store, from where I installed Zoom.

I only had the RPF camera without a mic on my Pi, but I managed to setup a meeting with my laptop that had video and mic.
Initial impressions were quite good as I got video in both direction, and the audio from the laptop mic came through on the Pi's HDMI. Obviously I couldn't test the audio in the other direction.

The video and audio came through consistently from the laptop, but unfortunately, the video from the Pi occasionally froze on my first test. On my second meeting, the video worked throughout the meeting for over 10 mins, but then froze again when I started messing with the settings. so maybe if you just video and don't mess with the settings it will be fine

Screen sharing and whiteboard both seemed to work.

The video lag was under 1 second, and the audio was about half that, or less.

[stinky_feat]

Hi There,

I kind of have the same issue.
So i have a RPi 4 4GB, and i'm running Raspbian OS. I also have a USB cam with mic.
I have joined a lot of meetings in zoom using Chromium, and works nice, but a i always had the same problem. I can never send audio and video simultaneously.
When i tried, it always said that chromium is preventing access to the mic. (although i have it autorized.)

I also have the zoom for chromium app installed.