Package Details: threema-desktop-beta 2.0_beta60-1

Git Clone URL: https://aur.archlinux.org/threema-desktop-beta.git (read-only, click to copy)
Package Base: threema-desktop-beta
Description: Threema Desktop 2.0 Beta.
Upstream URL: https://github.com/threema-ch/threema-desktop
Licenses: AGPL-3.0-only
Submitter: dbrgn
Maintainer: dbrgn
Last Packager: dbrgn
Votes: 5
Popularity: 0.006760
First Submitted: 2025-04-23 21:13 (UTC)
Last Updated: 2026-03-01 18:17 (UTC)

Pinned Comments

dbrgn commented on 2025-05-13 14:58 (UTC) (edited on 2025-07-08 08:01 (UTC) by dbrgn)

[Pinned comment]

  • Known issue: Saving the password does not work when launching from a window manager like Sway. If you use gnome-keyring but not GNOME, set XDG_CURRENT_DESKTOP=GNOME env variable (potentially by copying the .desktop file to ~/.local/share/applications/ and adjusting it).

Latest Comments

1 2 3 Next › Last »

tenninjas commented on 2026-04-21 05:22 (UTC) (edited on 2026-04-27 02:44 (UTC) by tenninjas)

I found the 'fix' of updating Cargo.toml to use the current wasm-bindgen was breaking things rather than fixing them at this point. I was able to resolve this by manually adding the correct source (currently 0.2.101) and locking to Threema's chosen versions. If anyone else is encountering the __wbindgen_externref_table_dealloc error, this is my temporary PKGBUILD diff which should fix it:

48,51c48,49
> source=("https://releases.threema.ch/desktop/${_pkgver}/threema-desktop-v${_pkgver}-source.7z"
>         "https://github.com/wasm-bindgen/wasm-bindgen/releases/download/0.2.101/wasm-bindgen-0.2.101-x86_64-unknown-linux-musl.tar.gz")
> b2sums=('e1a050d99f361b81601bbadf89a2a7f98f077cf2eb044bbc2c43d498621d974df203efcfc89c23fcd598a5effe9c811dcdfb40f55eab3d540d918b0c234429cf'
>         '94fd8bf565157f1ad057d39aed323d11be45a83a24e397992bc0a3f38eef766ee882e5bc39d00dc50d41454f3a51a4fcd72708a715e9aa1cd2b73242645cfe18') # Use get-checksum.sh to update
---
< source=("https://releases.threema.ch/desktop/${_pkgver}/threema-desktop-v${_pkgver}-source.7z")
< b2sums=('e1a050d99f361b81601bbadf89a2a7f98f077cf2eb044bbc2c43d498621d974df203efcfc89c23fcd598a5effe9c811dcdfb40f55eab3d540d918b0c234429cf') # Use get-checksum.sh to update
86,87c84,85
>   #sed -i '/^wasm-bindgen[ =]/s/version = "=.*"/version = "='$BINDGEN_VERSION'"/' Cargo.toml
>   cargo fetch --locked
---
<   sed -i '/^wasm-bindgen[ =]/s/version = "=.*"/version = "='$BINDGEN_VERSION'"/' Cargo.toml
<   cargo fetch
111d108
>   export PATH="${srcdir}/wasm-bindgen-0.2.101-x86_64-unknown-linux-musl:$PATH"

hias commented on 2026-03-29 20:17 (UTC)

Hi, I ran into this error while building: Error: Custom { kind: Other, error: "protoc failed: protoc: error while loading shared libraries: libabsl_log_initialize.so.2601.0.0: cannot open shared object file: No such file or directory\n" } After installing abseil-cpp, it builds fine. I hope this was helpful. And thanks for maintaining it.

dbrgn commented on 2025-10-31 15:27 (UTC)

@btl: It builds in a clean chroot (using the extra-x86_64-build command) on Arch Linux, so it must be on your side.

Note: You can also install Threema Desktop via Flatpak: https://three.ma/md I would usually suggest using the Flatpak over this AUR package, since it's sandboxed.

btl commented on 2025-10-30 21:25 (UTC)

Thanks for providing this. I was very happy with the AUR using CachyOS. But since Version Beta5.5 I can't do any updates via paru. As any other AUR I handle via paru does fine, it might be something in the threema-desktop-beta 2.0_beta57-1 AUR.pkg?

The installation aborts with:

error: failed to find the __wbindgen_externref_table_dealloc function ==> ERROR: A failure occurred in build(). Aborting... error: failed to build 'threema-desktop-beta-2.0_beta57-1': error: packages failed to build: threema-desktop-beta-2.0_beta57-1 PAKtC

Any chance I can get help with this issue?

dbrgn commented on 2025-10-15 07:55 (UTC)

wechsler: The package builds in a clean chroot. See comments below about your error - please upgrade your system.

wechsler commented on 2025-10-14 20:18 (UTC)

Thanks for providing the update to 2.0_beta56-2. Unfortunately while updating 2.0_beta54_1 --> 2.0_beta56-2 I received this error:

thread 'main' panicked at /build/.cargo/registry/src/index.crates.io-1949cf8c6b5b557f/clap_builder-4.5.47/src/parser/error.rs:32:9: Mismatch between definition and access of encode_into. Could not downcast to TypeId(0xf1420307fc22ca5c6c2812c04faba6a5), need to downcast to TypeId(0x306baddb6cd61f94b965c8cafbbb98f7)

note: run with RUST_BACKTRACE=1 environment variable to display a backtrace ==> ERROR: A failure occurred in build(). Aborting...

dbrgn commented on 2025-10-12 18:35 (UTC)

Updated to Beta 56. Package now includes a fix / workaround for the wasm-bindgen compatibility issues.

baby-void commented on 2025-10-10 15:25 (UTC)

https://threema.com/en/changelog/desktop-md

beta 56 has fixed saving passwords on KDE.

Fixes:

Prevent forwarding messages to blocked contacts

Display “archived” label for private chats

For some emoji reactions, there was no tooltip

On Windows, the app window could open outside of the screen in certain situations

Fix password saving in KDE (Linux)

…and various under-the-hood changes and improvements

bitsfritz commented on 2025-09-30 20:52 (UTC) (edited on 2025-09-30 20:54 (UTC) by bitsfritz)

got it done by downgrading both:

wasm-bindgen-0.2.101-1-x86_64

and

rustup-1.27.1-1-x86_64

didn't do the trick:

wasm-bindgen-0.2.104-1-x86_64

dbrgn commented on 2025-09-18 21:49 (UTC)

bitsfritz: Can confirm the error. The reason seems to be a recent update in wasm-bindgen: It builds successfully with 0.2.101-1 but not with 0.2.103-1.

The root problem has nothing to do with Threema and was reported here already: https://github.com/wasm-bindgen/wasm-bindgen/issues/4662 It is fixed on the main branch, but there is no release yet.

For now, until a fixed release >0.2.103 is released, you should downgrade wasm-bindgen to an earlier version.

1 2 3 Next › Last »