| 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.076133 |
| First Submitted: | 2025-04-23 21:13 (UTC) |
| Last Updated: | 2025-12-09 08:42 (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.
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_deallocfunction ==> 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?
wechsler: The package builds in a clean chroot. See comments below about your error - please upgrade your system.
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...
Updated to Beta 56. Package now includes a fix / workaround for the wasm-bindgen compatibility issues.
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
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
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.
get error
Finished `release` profile [optimized] target(s) in 1m 21s
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)
fresh build, wiped threema-desktop-beta folder's content before building
Pinned Comments
dbrgn commented on 2025-05-13 14:58 (UTC) (edited on 2025-07-08 08:01 (UTC) by dbrgn)
[Pinned comment]
XDG_CURRENT_DESKTOP=GNOMEenv variable (potentially by copying the .desktop file to~/.local/share/applications/and adjusting it).