Package Details: threema-desktop-beta 2.0_beta51-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: 4
Popularity: 2.99
First Submitted: 2025-04-23 21:13 (UTC)
Last Updated: 2025-05-09 08:12 (UTC)

Pinned Comments

dbrgn commented on 2025-05-13 14:58 (UTC)

[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).
  • Known issue: App restarts (e.g. when enabling or disabling logging) don't work when started through an app launcher like dmenu. They work when starting "ThreemaDesktopLauncher" from the command line though. See https://aur.archlinux.org/packages/threema-desktop-beta?O=10#comment-1020954 for more details.

Latest Comments

« First ‹ Previous 1 2

dbrgn commented on 2025-04-24 16:52 (UTC)

@nasko: Thanks for the report. This is an issue with the upstream package, because the font "Lab Grotesque" is not bundled for licensing reasons. This issue will be fixed with the next release, but for now I patched it in this package.

nasko commented on 2025-04-24 00:53 (UTC) (edited on 2025-04-24 01:07 (UTC) by nasko)

I can't see any digits in the desktop app - neither in the chat window, nor in the prompt where I'm typing. Spaces are shown in place of the digits.

DE: KDE Plasma 6.3.4 WM: KWin (Wayland) Kernel: Linux 6.14.2-arch1-1 VGA: Intel Corporation Alder Lake-UP3 GT2 [Iris Xe Graphics] (rev 0c) Kernel driver in use: i915

Screenshot: https://gist.github.com/nasko/7a7da247725a51079c906529164281ce

dbrgn commented on 2025-04-23 21:18 (UTC)

Known issue: App restarts (e.g. when enabling or disabling logging) don't work when started through an app launcher like dmenu. They work when starting "ThreemaDesktopLauncher" from the command line though.

Calling strace on the launcher shows:

wait4(60452, [{WIFEXITED(s) && WEXITSTATUS(s) == 8}], 0, NULL) = 60452
--- SIGCHLD {si_signo=SIGCHLD, si_code=CLD_EXITED, si_pid=60452, si_uid=1000, si_status=8, si_utime=82 /* 0.82 s */, si_stime=25 /* 0.25 s */} ---
ioctl(2, TCGETS, {c_iflag=BRKINT|ICRNL|IMAXBEL|IUTF8, c_oflag=NL0|CR0|TAB0|BS0|VT0|FF0|OPOST|ONLCR, c_cflag=B38400|CS8|CREAD|HUPCL, c_lflag=ISIG|ICANON|ECHO|ECHOE|ECHOK|IEXTEN|ECHOCTL|ECHOKE, ...}) = 0
write(1, "Target binary exited with status"..., 48) = -1 EPIPE (Broken pipe)
--- SIGPIPE {si_signo=SIGPIPE, si_code=SI_USER, si_pid=60423, si_uid=1000} ---
write(2, "\nthread 'main' panicked at libra"..., 116) = 116
write(2, "note: run with `RUST_BACKTRACE=1"..., 78) = 78

This should in theory be resolved by the IsTerminal checks (https://github.com/threema-ch/threema-desktop/blob/stable/src/rust/launcher/src/util/logging.rs) but that doesn't seem to help. Pointers welcome.

« First ‹ Previous 1 2