How to solve "execve: Exec format error" until proper package fix.
Just remove the empty spaces (4) at the first line in /usr/bin/ferdium
Its supposed to be like this
#!/bin/sh
ELECTRON_IS_DEV=0 exec /usr/bin/electron25 /opt/ferdium-bin/ "$@"
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.22 |
First Submitted: | 2022-04-22 10:05 (UTC) |
Last Updated: | 2024-11-11 09:07 (UTC) |
« First ‹ Previous 1 2 3
How to solve "execve: Exec format error" until proper package fix.
Just remove the empty spaces (4) at the first line in /usr/bin/ferdium
Its supposed to be like this
#!/bin/sh
ELECTRON_IS_DEV=0 exec /usr/bin/electron25 /opt/ferdium-bin/ "$@"
After install lastest build, i cannot start Ferdium from the menu, only from console. From the menu, i have this error: Launching Ferdium (Failed) execve: Exec format error
I have removed the tab in front of the shebang in the start script, the issue reported by @Sintan and @emceebois should be fixed now.
Can confirm the same issue that @Sintan references. I have not tested his fix since I got my system working again by removing the whitespace from the script manually, but it looks good to me.
The current packages fails to launch (at least on KDE). Changing lines 54-56 of PKGBUILD
to
cat > "$pkgdir/usr/bin/$_pkgname" <<EOF
#!/bin/sh
ELECTRON_IS_DEV=0 exec /usr/bin/$_electron /opt/$pkgname/ "\$@"
EOF
fixes it. It's just that the shebang was being printed to the script with a tab.
In the arch
array, arm64
is invalid. The name of 64-bit ARM is aarch64
.
Is it normal that the package conflicts with itself? I downloaded the PKGBUILD and removed the conflict with ferdium-bin and I could install it.
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.
@TechXero Yep, ferdium and ferdium-git are broken too:
https://github.com/ferdium/ferdium-app/issues/235
Latest is broken just purple screen ...
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.