| Git Clone URL: | https://aur.archlinux.org/ferdium-bin.git (read-only, click to copy) |
|---|---|
| Package Base: | ferdium-bin |
| Description: | A messaging browser that allows you to combine your favorite messaging services into one application (binary release). |
| Upstream URL: | https://ferdium.org |
| Licenses: | Apache |
| Conflicts: | ferdium, ferdium-beta, ferdium-beta-bin, ferdium-electron, ferdium-git, ferdium-nightly, ferdium-nightly-bin |
| Provides: | ferdium |
| Submitter: | cedricroijakkers |
| Maintainer: | cedricroijakkers |
| Last Packager: | cedricroijakkers |
| Votes: | 39 |
| Popularity: | 0.78 |
| First Submitted: | 2022-04-22 10:05 (UTC) |
| Last Updated: | 2025-11-03 14:34 (UTC) |
@cedricroijakkers, update the electron version to 37, upstream moved to it with 7.1.1.
To avoid this sort of mismatch, imo it would be better to link the dependency to just plain electron, instead of pinning it to a specific version, it is not as if electron has major breaking changes per every version, and I don't think that upstream has version specific code.
Hmmm, aparently needs to conflict with nodejs-lts-iron as example
Building ferdium-bin 7.1.0 leads to follow error:
CANNOT RUN WITH NODE 20.19.5 asar requires Node >=22.12.0.
Packages installed by this package are:
extra/asar 4.0.1-1 3,64 MiB 0,37 MiB extra/electron35 35.7.5-1 270,56 MiB 81,03 MiB
It looks like the issue is fixed in electron35. I just edited ferdium's starter script for now to use electron35. It will be overwritten on the next ferdium-bin update but I assume that this will change to electron35 anyway.
Thanks for your support!
I would have found it unlikely to be ferdium itself, since it's electron that is responsible for the screen rendering etc. If you submit the issue to electron upstream, you should be able to reproduce it by just running the electron executable itself also: /usr/bin/electron34
Damn, it's indeed electron34. Sorry for the confusion. I'll try to downgrade it as far as possible to find the exact minor version where the issue started appearing.
Technically that would be untested, but I honestly don't think you would run into a lot of issues, so if the combo 7.0.1 + electron33 works for you, I would use that for now.
I posted a report upstream: https://github.com/ferdium/ferdium-app/issues/2109
Is it possible to use version 7.0.0 with electron34 or version 7.0.1 with electron33 by editing the PKGBUILD correspondingly?
The easiest way would be to clone the PKGBUILD file and modify it yourself. To downgrade the Electron version, modify the variables _electron and _electronpackage and build it, to downgrade Ferdium itself, modify the variables pkgverorg and pkgver and build it. Be sure to run updpkgsums before building with makepkg -si.
If you find that the issue is with Electron itself, you can also see if you can reproduce it by just running the electron executable, make screenshots and post them as an issue in the electron github. If you find that the problem is with Ferdium, post them on the Ferdium github.
I downgraded to 7.0.0 and electron33, looks like the issue isn't there any more. Is there any way to find out, whether it's the electron33->electron34 upgrade or the ferdium 7.0.0->ferdium7.0.1 upgrade that introduced the issue?
Pinned Comments
cedricroijakkers commented on 2022-06-13 06:54 (UTC)
Note: This package follows the latest release package on the GitHub releases page of ferdium-app (https://github.com/ferdium/ferdium-app/releases). A tag in the git repo does not always mean a new binary release will be created. If you wish to follow the latest tag in git and build Ferdium yourself, use the AUR package
ferdiuminstead.