Arch Linux User Repository

No problem, things like that happen ;)

You can put flags for electron apps in ~/.config/electron-flags.conf (or ~/.config/electron12-flags.conf for apps using electron12; Arch has configured their electron packages in such a way as to pick those up.

Mine looks like

--enable-features=UseOzonePlatform
--ozone-platform=wayland
--enable-gpu

for WayLand, for example. But since GPU / HW / HW Video acceleration with chrome/electron/wayland/etc. is kind of a mess with different GPUs, that might not help you very much ^^

FacePalm, sorry mate, forgot that I had a .local/bin override launcher that fiddled the settings to get GPU acceleration working (which it didn't, by the way)... THX and again, sorry for bothering...

That should only happen if you try to launch it with electron(version 13 which is the current default in the Arch repos). The /usr/bin/jitsi-meet-desktop explicitely uses electron12, so I'm not sure what's going on here. Could you make sure you've made no changes to the PKGBUILD as provided by this AUR repo, or if your /usr/bin/jitsi-meet-desktop has electron12 in it?

(I can reproduce that error if I run NODE_ENV=production ELECTRON_IS_DEV=false electron /opt/jitsi-meet-desktop/app.asar instead of NODE_ENV=production ELECTRON_IS_DEV=false electron12 /opt/jitsi-meet-desktop/app.asar, like it's used in the /usr/bin/jitsi-meet-desktop. See https://github.com/nodejs/node/blob/master/doc/abi_version_registry.json for a list of NODE_MODULE_VERSION mappings, 89 would be electron 13.)

Even after rebuilding this package I continue to get this...

No idea how to fix it...

~ >>> jitsi-meet-desktop                                                       
App threw an error during load
Error: The module '/tmp/.org.chromium.Chromium.mSFmmz'
was compiled against a different Node.js version using
NODE_MODULE_VERSION 87. This version of Node.js requires
NODE_MODULE_VERSION 89. Please try re-compiling or re-installing
the module (for instance, using `npm rebuild` or `npm install`).
    at process.func [as dlopen] (electron/js2c/asar_bundle.js:5:1846)
    at Object.Module._extensions..node (internal/modules/cjs/loader.js:1138:18)
    at Object.func [as .node] (electron/js2c/asar_bundle.js:5:2073)
    at Module.load (internal/modules/cjs/loader.js:935:32)
    at Module._load (internal/modules/cjs/loader.js:776:14)
    at Function.f._load (electron/js2c/asar_bundle.js:5:12913)
    at Module.require (internal/modules/cjs/loader.js:959:19)
    at require (internal/modules/cjs/helpers.js:88:18)
    at Object.<anonymous> (/opt/jitsi-meet-desktop/app.asar/node_modules/robotjs/index.js:1:15)
    at Module._compile (internal/modules/cjs/loader.js:1078:30)

Thank you - you're a star!

I will try it today

Should be working again now. Might even cut the build time a bit on x86_64, as now everything that's not the desired (dir) build target just won't happen anymore.

I can reproduce this, I think (or at least something that looks like it ^^)

I'll see if I can get it fixed while muttering to myself about how much I hate how "oh, $application is so very cross platform and you can run (and build) it anywhere, because electron" it all is ;D

I am getting an error when building for aarch64. The extract from the log is

13 info lifecycle jitsi-meet-electron-utils@2.0.16~install: jitsi-meet-electron-utils@2.0.16
14 verbose lifecycle jitsi-meet-electron-utils@2.0.16~install: unsafe-perm in lifecycle true
15 verbose lifecycle jitsi-meet-electron-utils@2.0.16~install: PATH: /home/alarm/Downloads/jitsi-meet-desktop/src/.nvm/versions/node
/v14.17.1/lib/node_modules/npm/node_modules/npm-lifecycle/node-gyp-bin:/home/alarm/Downloads/jitsi-meet-desktop/src/jitsi-meet-elect
ron-2.8.7/node_modules/jitsi-meet-electron-utils/node_modules/.bin:/home/alarm/Downloads/jitsi-meet-desktop/src/jitsi-meet-electron-
2.8.7/node_modules/.bin:/home/alarm/Downloads/jitsi-meet-desktop/src/jitsi-meet-electron-2.8.7/node_modules/.bin:/home/alarm/Downloa
ds/jitsi-meet-desktop/src/.nvm/versions/node/v14.17.1/bin:/usr/local/sbin:/usr/local/bin:/usr/bin:/usr/bin/site_perl:/usr/bin/vendor
_perl:/usr/bin/core_perl
16 verbose lifecycle jitsi-meet-electron-utils@2.0.16~install: CWD: /home/alarm/Downloads/jitsi-meet-desktop/src/jitsi-meet-electron
-2.8.7/node_modules/jitsi-meet-electron-utils
17 silly lifecycle jitsi-meet-electron-utils@2.0.16~install: Args: [ '-c', 'prebuild-install || node-gyp rebuild' ]
18 silly lifecycle jitsi-meet-electron-utils@2.0.16~install: Returned: code: 1  signal: null
19 info lifecycle jitsi-meet-electron-utils@2.0.16~install: Failed to exec install script
20 verbose stack Error: jitsi-meet-electron-utils@2.0.16 install: `prebuild-install || node-gyp rebuild`
20 verbose stack Exit status 1

Any ideas?

A quick note on the most recent update:

I've reverted the patch (https://github.com/jitsi/jitsi-meet-electron/commit/0e0483cbc52a9cad1fef51ed5abb846bd6445b11) for pipewire screensharing support, as that change caused jitsi-meet-desktop to hang / not launch on swaywm with the following flags for native wayland support in my ~/.config/electron12-flags.conf:

--enable-features=UseOzonePlatform
--ozone-platform=wayland

The flag (--enable-features=WebRTCPipeWireCapturer) can be easily applied, if desired, by putting it in this very file (~/.config/electron12-flags.conf) individually, which I think is a saner approach to using it anyway.

It might work fine on other setups, but at least on my system (with sway-git and wlroots-git), it doesn't work.

@je-vv:

Those issues should be fixed now, hopefully (those of @jsamr as well, I think :).

oh well, with last change (2.8.6-2) building jitsi-meet-desktop leaves ~/.npm dirty... I guess the build stage is not doing anything to change the cache directory as it was done on on the prepare stage. Perhaps adding the env var setting:

export npm_config_cache="${srcdir}/npm_cache"

also to the build stage? Or perhaps it's being set too late on the prepare stage? I can't tell, but maybe using:

unset npm_config_prefix
export npm_config_cache="${srcdir}/npm_cache"

at the beginning of prepare() might solve things, and if not enough, then at the beginning of both, prepare() and build()