Package Details: ente-auth 4.4.25-3

Git Clone URL: https://aur.archlinux.org/ente-auth.git (read-only, click to copy)
Package Base: ente-auth
Description: Open source 2FA authenticator, with end-to-end encrypted backups
Upstream URL: https://ente.com/auth
Licenses: AGPL-3.0-or-later
Submitter: yochananmarqos
Maintainer: yochananmarqos
Last Packager: yochananmarqos
Votes: 3
Popularity: 0.004142
First Submitted: 2024-06-08 18:40 (UTC)
Last Updated: 2026-08-27 16:57 (UTC)

Dependencies (19)

Required by (1)

Sources (3)

Latest Comments

madhakker commented on 2026-08-27 11:28 (UTC)

Blank/black window on launch — packaging bug + fix

After building and installing via yay -S ente-auth, the app compiled fine but launching produced a blank window with the terminal showing:

[CryptoUtil][SEVERE] Failed to load sodium ⤷ error: Invalid argument(s): Failed to lookup symbol 'sodium_init': /opt/ente-auth/lib/libflutter_linux_gtk.so: undefined symbol: sodium_init

Root cause 1 — missing execute permission on plugin libraries

All the Flutter plugin .so files in /opt/ente-auth/lib/ were installed as -rw-r--r-- (no execute bit), except libflutter_linux_gtk.so itself. This looks like the install() step in the PKGBUILD isn't preserving/setting the execute bit when copying the built plugin libraries. Fix:

bash sudo chmod +x /opt/ente-auth/lib/*.so

Root cause 2 — libsodium never gets loaded into the process

Even after fixing permissions, the sodium_init lookup still failed. The Dart sodium_libs package uses DynamicLibrary.process() on Linux, which requires libsodium's symbols to already be loaded globally into the process — but nothing in the bundled app (/opt/ente-auth/) actually links or bundles libsodium.so, and libsodium_libs_plugin.so (the plugin responsible for loading it) doesn't appear to load it with global visibility as installed.

Workaround — force-preload the system libsodium before launch:

bash LD_PRELOAD=/usr/lib/libsodium.so enteauth

This launches the app successfully. For a permanent fix without editing the system desktop file, users can override the launcher in ~/.local/share/applications/enteauth.desktop with:

Exec=env LD_PRELOAD=/usr/lib/libsodium.so /opt/ente-auth/enteauth

Suggested PKGBUILD fixes:

In package(), ensure plugin .so files are installed with install -Dm755 (not -Dm644) so they retain the execute bit. Either statically link libsodium into the Linux build, or add a depends=('libsodium') and have the app properly dlopen() it with RTLD_GLOBAL at startup (may need investigating whether this is an upstream sodium_libs/ente-auth Linux bug rather than purely a PKGBUILD issue) — the LD_PRELOAD wrapper above is a working stopgap in the meantime.

(Separately, unrelated to this package: if your system locale isn't a generated UTF-8 locale, you may also see a "Locale not supported by C library" warning and libsecret/keyring errors on first launch — worth generating a proper UTF-8 locale via /etc/locale.gen if you hit that too.)

yochananmarqos commented on 2026-08-26 16:22 (UTC)

@pSYCHO: See the upstream issue.

pSYCHO commented on 2026-08-26 06:37 (UTC)

After installing this, all I see is a black screen, but ente-auth-bin works for me, although it is not updated regularly.

Proxy-A23 commented on 2024-06-25 05:40 (UTC) (edited on 2024-06-25 05:42 (UTC) by Proxy-A23)

@yochananmarqos The package ente-auth-bin does work; I know because it's the one I'm currently using, at least until this package allows logging in.

yochananmarqos commented on 2024-06-24 17:36 (UTC) (edited on 2024-06-24 17:36 (UTC) by yochananmarqos)

@Proxy-A23: I have the same issue with this package and have not figured out why yet. The ente-auth-bin package does not work at all as it can't find libsodium.so.23.

Proxy-A23 commented on 2024-06-24 05:59 (UTC) (edited on 2024-06-25 05:45 (UTC) by Proxy-A23)

I don't understand why, when using this package to log in, I get the message "Recreate password: The current device is not powerful enough to verify your password, but we can regenerate in a way that works with all devices. Please login using your recovery key and regenerate your password (you can use the same one again if you wish)."

I saw the following on Reddit:

"Hey, this means that the parameters that were used to derive your master-key on your original device, are incompatible with your current device (likely because it's less powerful).

If you recover your account via your current device and reset the password, it will re-generate a key that will be compatible on both devices."

I tried this, but every time I use my key, it says it's incorrect and I can't change the password.

However, if I install the other package ente-auth-bin I can log in without any issues.