Package Details: jitsi-meet-desktop 2.9.0-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://jitsi.org/jitsi-meet/
Keywords: chat IM video
Licenses: Apache
Conflicts: jitsi-meet-electron, jitsi-meet-electron-bin
Replaces: jitsi-meet-electron
Submitter: SamWhited
Maintainer: lsf
Last Packager: lsf
Votes: 24
Popularity: 1.23
First Submitted: 2020-04-10 13:16
Last Updated: 2021-09-29 08:55

Latest Comments

1 2 3 4 5 6 Next › Last »

je-vv commented on 2021-09-05 22:11

I rebuilt with 14, and it's working back. Not sure if it was a temporal out of service somewhere. Thanks a lot !

lsf commented on 2021-09-05 10:41

@je-vv

That's… odd (because I only ever had that "hanging, issue before when running nvm install (or use) during package building when already in a directory with an .nvmrc and running the nvm sourcing there, but hadn't had it for ages).

With your modifications, I'd assume it will fall back to npm 12 (as specified in the .nvmrc – which shouldn't hurt, so if it works, that's fine.

Alternatively, it might be worth trying to do the cd jitsi-meet-electron-${pkgver} only after the nvm commands (and _ensure_local_nvm are run) as a workaround.

I'll see if I can find out the root cause, though, as that's probably better than trying to find workarounds ;)

nvm install or use with a major version only shouldn't cause the issue, but admittedly I cannot recall why I went and set it to 14 in the first place instead of using the "predetermined" one in the .nvmrc (12). There probably was some reason ;)

je-vv commented on 2021-09-05 09:46

BTW, by changing:

nvm install 14

To:

nvm install

And, by removing:

nvm use 14

The build process doesn't hang any more. Not sure if the right thing to do, but it works, :) I guess the "nvm use 14" had to be removed, since "nvm install 14" doesn't really works out. Besides, the "nvm use" is not documented on:

https://wiki.archlinux.org/title/Node.js_package_guidelines#Using_nvm

Even though a full version is exemplified there...

je-vv commented on 2021-09-05 09:31

@lsf, prepare is hanging while executing:

nvm use 14

I realized it's while executing that by modifying the PKGBUILD:

prepare() {
  cd jitsi-meet-electron-${pkgver}
  export npm_config_cache="${srcdir}/npm_cache"
  _ensure_local_nvm
  echo "before nvm install"
  nvm install 14
  echo "after nvm install"

And the output I got:

before nvm install

Hanging in there, without getting to output "after ..." Not sure if the reference:

https://wiki.archlinux.org/title/Node.js_package_guidelines#Using_nvm

Would only work without specifying any version, or specifying major + minor + patch release version. Not sure if the problem is around that, specifying only the major release version, and perhaps not specifying any version would be best?

lsf commented on 2021-08-09 09:16

Thanks, seems to work fine! :)

je-vv commented on 2021-08-07 01:00

NP @lsf. BTW, I'm not sure which release brought it, but currently you can successfully build jitst-meet-desktop without python2. Can you please try it, and if confirming it, could you remove python2 from build dependencies?

I guess they bumped up the requirement for node-gyp on jitsi-meet-electron-utils, since at least master requires v. 6.1.0 now:

https://github.com/jitsi/jitsi-meet-electron-utils/blob/master/package-lock.json#L2444

So it seems safe to remove python2 from make depends...

Thanks !

lsf commented on 2021-08-04 21:42

Thanks for making me aware of that! :)

je-vv commented on 2021-08-04 20:14

@lsf, just in case you were not aware, the latest release, 2.8.9, uses electron13, so moving to 2.8.9 has that extra benefit, getting rid of electron12, :)

https://github.com/jitsi/jitsi-meet-electron/releases/tag/v2.8.9

lsf commented on 2021-07-14 09:25

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 ^^

Zappo-II commented on 2021-07-14 09:20

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...