Package Details: threema-desktop-beta 2.0_beta56-2

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.54
First Submitted: 2025-04-23 21:13 (UTC)
Last Updated: 2025-10-12 18:34 (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 »

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.

bitsfritz commented on 2025-09-18 19:56 (UTC) (edited on 2025-09-18 19:58 (UTC) by bitsfritz)

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

tobias-haenel commented on 2025-09-11 10:01 (UTC) (edited on 2025-09-11 10:03 (UTC) by tobias-haenel)

Could you please add the following to the start of the build() section:

export CARGO_TARGET_DIR=target

This will ensure that the rust part of the build procedure also works without a chroot, when the cargo build.target-dir config option (https://doc.rust-lang.org/cargo/reference/config.html#buildtarget-dir) has been changed by a user in ~/.config/cargo.toml

See https://wiki.archlinux.org/title/Rust_package_guidelines#Build for more details.

dbrgn commented on 2025-07-08 23:06 (UTC) (edited on 2025-07-08 23:06 (UTC) by dbrgn)

@thomasgassmann: Thanks for the comment, which leads to a little rabbithole.

When starting Threema under Xorg (by directly launching /opt/threema-desktop-beta/ThreemaDesktopLauncher), the WM_CLASS of the window is set to the app name, which is "Threema Beta". In this case, the desktop file is correct.

But when starting Threema under Wayland (i.e. you're using the wrapper script at /usr/bin/threema-beta and have Wayland set up), there is no WM_CLASS because that's an Xorg thing. Instead, there's the app_id, and that is currently set to just Threema. That is also the case for Threema Work, meaning that under Wayland you cannot differentiate between the two windows, and the dock icons may misbehave.

I'll have to investigate how the Wayland app_id can be set from Electron. It seems that it is set here:

https://github.com/electron/electron/blob/712262597dd621285bad2bc98fc9bfe105cf15f8/shell/browser/native_window_views.cc#L293

Which uses this function:

https://github.com/electron/electron/blob/712262597dd621285bad2bc98fc9bfe105cf15f8/shell/common/platform_util_linux.cc#L431

...which looks like it should just use the base name of the .desktop file... However, that would be "ch.threema.threema-desktop", so I'm not sure where things go wrong.

Pointers welcome.

1 2 3 Next › Last »