Package Details: jitsi-meet-desktop 2025.1.1-1

Git Clone URL: https://aur.archlinux.org/jitsi-meet-desktop.git (read-only, click to copy)
Package Base: jitsi-meet-desktop
Description: Jitsi Meet desktop application
Upstream URL: https://github.com/jitsi/jitsi-meet-electron
Licenses: Apache-2.0
Submitter: SamWhited
Maintainer: xiota
Last Packager: xiota
Votes: 30
Popularity: 0.076825
First Submitted: 2020-04-10 13:16 (UTC)
Last Updated: 2025-01-20 03:51 (UTC)

Dependencies (2)

Required by (0)

Sources (2)

Latest Comments

« First ‹ Previous 1 2 3 4 5 6 7 8 9 Next › Last »

lsf commented on 2021-04-03 11:41 (UTC)

Normally it should be enough to just rebuild the package – it probably happened because nodejs got updated in the meantime.

I'll push a new version of jitsi-meet-desktop in a few minutes anyway, so things should work again after you've installed that one :)

@je-vv: np.

where does the .npmrc get generated?

nirnakinho commented on 2021-04-03 11:29 (UTC) (edited on 2021-04-03 11:30 (UTC) by nirnakinho)

Hello,

for a few days, jitsi-meet-desktop fails to start, it gives me the following error message:

App threw an error during load
Error: The module '/tmp/.org.chromium.Chromium.9WLDXQ'
was compiled against a different Node.js version using
NODE_MODULE_VERSION 85. This version of Node.js requires
NODE_MODULE_VERSION 87. 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:12684)
    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)
A JavaScript error occurred in the main process
Uncaught Exception:
Error: The module '/tmp/.org.chromium.Chromium.9WLDXQ'
was compiled against a different Node.js version using
NODE_MODULE_VERSION 85. This version of Node.js requires
NODE_MODULE_VERSION 87. 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:12684)
    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)

I am at loss why there is a conflict between those nodejs module versions, any help is appreciated. Thanks.

Regards,

je-vv commented on 2021-03-31 00:17 (UTC)

@lsf, the export of npm_config_cache, does work, sorry about that. I just noticed the file

% cat .npmrc                                                                                                                                                                                                                       
prefix=/usr

still gets generated though. Which is a minor thing compared to the cache though... Thanks !

DAMO238 commented on 2021-03-29 14:19 (UTC)

@gok's advice worked, even though it didn't install with pacman due to error: target not found: jitsi-meet-desktop, which was solved by manually telling pacman to install the compiled package with sudo pacman -U /path/to/package.

lsf commented on 2021-03-28 23:24 (UTC)

@je-vv the line with export npm_config_cache="$srcdir/npm_cache" should be equivalent to this – doesn't it work as I thought it did?

je-vv commented on 2021-03-28 23:02 (UTC)

@lsf or @SamWhited, could you please add --cache "${srcdir}/npm-cache" or something similar so that npm and npx don't pollute the FS with bloated stuff? Thanks !

lsf commented on 2021-03-28 10:50 (UTC)

@gok: That's quite strange indeed – no idea why this could be. But still, great to hear that you could get it to build now! :)

gok commented on 2021-03-28 10:22 (UTC) (edited on 2021-03-28 10:52 (UTC) by gok)

When intially trying to build jitsi-meet-desktop 2.8.3-1 with plain makepkg on my system, it hung at building the robotjs dependency, like @milaq and @DAMO238 reported. Then I tried to build jitsi-meet-desktop 2.8.3-1 in a clean chroot (by running the following command, in a directory where I downloaded the jisti-meet-desktop PKGBUILD: extra-x86_64-build -- -I /path/to/nvm-0.37.2-1-any.pkg.tar.zst, where nvm 0.37.2-1 is the latest version currently in AUR), which worked.

The weird thing is that, after a 1st successful building of jitsi-meet-desktop 2.8.3-1 in a clean chroot, re-building it with plain makepkg now works, and I don't know why. I don't have time to dig into this at the moment. I will try to understand why this happens next time there is a jitsi-meet-desktop update.

lsf commented on 2021-03-27 19:54 (UTC)

Have you tried building it in a clean chroot to make sure it's not some enviroment / system specific issue? https://wiki.archlinux.org/index.php/DeveloperWiki:Building_in_a_clean_chroot

(I still can't reproduce it, neither in a clean chroot, docker or with plain makepkg).

DAMO238 commented on 2021-03-27 17:48 (UTC)

I also have the hang at robotjs. I have tried using both nvm and nvm-git from the aur, neither of which worked.

« First ‹ Previous 1 2 3 4 5 6 7 8 9 Next › Last »