Arch Linux User Repository

I think it's prudent to only update this package for final releases and not for pre-releases. When flagging it as out of date, please make sure it's a superseding release and not a pre-release.

gpg --keyserver hkp://keyserver.ubuntu.com --recv-keys E21B6950A2ECB65C

@Strykar To avoid this you need to build the package in an empty directory.

Package should not be asking the user anything:

Would you like to replace the existing file:
  Path:     ./LICENSE.electron.txt
  Size:     1096 bytes (2 KiB)
  Modified: 2025-06-23 15:42:13
with the file from archive:
  Path:     LICENSE.electron.txt
  Size:     1096 bytes (2 KiB)
  Modified: 2025-06-23 15:42:13
? (Y)es / (N)o / (A)lways / (S)kip all / A(u)to rename all / (Q)uit? 

@TheWicked Thanks for your effort. Current version of pacman seems to be ignoring the !strip option. ( https://gitlab.archlinux.org/pacman/pacman/-/issues/107 ) suggested temporary workaround is to add

OPTIONS=('!strip' '!debug')

Finally I am able to install the package again. After quite some "try and error" I found that it does not work with the current /etc/makepkg.conf provided by pacman. To get it working I had to disable the debug option:

OPTIONS=(strip docs !libtool !staticlibs emptydirs zipman purge !debug lto)

At first I thought it was some recent pacman change, but for a reason I do not remember I had manually disabled the debug flag in the past, so it was always working, but since there was a conflict in a recent update, I accidentally reverted my manual change and it stopped working.

It is highly advised to build in a clean chroot https://wiki.archlinux.org/title/DeveloperWiki:Building_in_a_clean_chroot

OK, I did some more digging. Basically running line 30 of the PKGBUILD from the yay cache directory makes it work again:

cd ~/.cache/yay/trezor-suite-appimage
sudo install -Dm755 "Trezor-Suite-24.3.3-linux-x86_64.AppImage" "/opt/trezor-suite/trezor-suite.AppImage"

Of course this is no practical solution. I assume the issue is somehow related to yay.

Hello, since 24.3.2 I get the exact same error like @mrpelotazo:

$ trezor-suite
This doesn't look like a squashfs image.

Cannot mount AppImage, please check your FUSE setup.
...

However, for me the permissions of /opt/trezor-suite/trezor-suite.AppImage are fine.

What I noticed during the update was my AUR helper showing that the disk space used with the new trezor-suite-appimage version is >100 MB less. The file size of /opt/trezor-suite/trezor-suite.AppImage is only about 188 KB, which does not seem to be right. I would expect at at least 100 MB, so I guess something is going wrong when extracting/installing it.

Hello, I'm getting the following error after last upgrade:

$ trezor-suite
This doesn't look like a squashfs image.

Cannot mount AppImage, please check your FUSE setup.
You might still be able to extract the contents of this AppImage 
if you run it with the --appimage-extract option. 
See https://github.com/AppImage/AppImageKit/wiki/FUSE 
for more information
open dir error: No such file or directory

Running the downloaded appimage directly (after giving it exec permissions) works fine though.

Hello, the signing key used is from SatoshiLabs. It may also be downloaded directly from the Trezor site (currently it's "Signing Key 2021", provided at https://trezor.io/trezor-suite):

wget https://trezor.io/security/satoshilabs-2021-signing-key.asc
gpg --import satoshilabs-2021-signing-key.asc
gpg --edit-key 'SatoshiLabs 2021'
trust
4 (full)
quit

@runaz
https://github.com/trezor/trezor-suite/issues/9224