Package Details: ferdium-bin 7.0.0-1

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: 36
Popularity: 1.59
First Submitted: 2022-04-22 10:05 (UTC)
Last Updated: 2024-11-11 09:07 (UTC)

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

Latest Comments

« First ‹ Previous 1 2 3 Next › Last »

Fijxu commented on 2023-12-31 02:46 (UTC) (edited on 2023-12-31 02:47 (UTC) by Fijxu)

I can ask why this pacakge uses electron27-bin instead of the default electron on the official arch repositories? Electron 25 is just fine right or there is any problems with Ferdium being ran under Electron 25?

I don't want to have multiple electron versions on my PC.

cedricroijakkers commented on 2023-11-06 13:44 (UTC)

I have removed the conflict with the package itself, that should fix your issues.

The-Anathema commented on 2023-11-04 21:58 (UTC)

Ferdium-bin conflicting with Ferdium-bin causes unresolvable dependency conflict (pacaur, probably others), please correct this.

oldflag commented on 2023-10-28 09:11 (UTC)

After update to electron27, ferdium does not read config from ~/.config/electron<version>-flags.conf? Do you guys have this issue?

cedricroijakkers commented on 2023-09-04 07:03 (UTC)

Interesting. I also only have /usr/lib/libicui18n.so.73.2 on my system, but both building and running the package work fine for me.

Ferdium is being run by the electron executable in /usr/lib/electron25/electron. Mine has a dependency on /usr/lib/libicui18n.so.73, maybe check your and try reinstalling the electron25 package?

archee commented on 2023-09-02 14:06 (UTC)

I'm also getting the error about missing /usr/lib/libicui18n.72.so. My system has only /usr/lib/libicui18n.73.so.

ViCinS commented on 2023-08-30 07:06 (UTC) (edited on 2023-08-30 07:10 (UTC) by ViCinS)

Hello, I got this error upgrading:

==> Validazione di source_x86_64 file con sha512sums...

ferdium-bin-6.4.1-1-amd64.zip ... Verificato

==> Estrazione dei sorgenti in corso...

-> Estrazione di ferdium-bin-6.4.1-1-amd64.zip usando bsdtar in corso...

==> Avvio di prepare() in corso...

==> Entro nell'ambiente fakeroot...

==> Avvio di package() in corso...

node: error while loading shared libraries: libicui18n.so.72: cannot open shared object file: No such file or directory

I've newest version of libicu:

/usr/lib/libicui18n.so

/usr/lib/libicui18n.so.73

/usr/lib/libicui18n.so.73.2

Thank you!

vmfventura commented on 2023-08-29 22:44 (UTC)

Thank, working

cedricroijakkers commented on 2023-08-29 06:45 (UTC)

The issue with "Exec format error" in the start script has been solved, if you still have an old version of the package installed locally, force a clean build reinstall, and the problem should be gone.