Topic: Trezor Suite 21.3.1 AppImage issues - Debian (Read 117 times)

I have spent quite a bit of time reading about this issue.  Not specific to Trezor Suite there are many "games/software" products that fire off chrome-sandbox flags of sorts.  Many sage users just send the error flags to the vendors/producers to fix rather than edit their OS for safety reasons.  After all Electrum has no issues with AppImage that I have ever experienced - just saying!

Anyway, every single time I mount Trezor Suite it creates a different temp file of course, since its not persistent.  I created a VM and did a snapshot so I could keep playing with edits having immunity by flashing back snapshots as needed.  I didn't mind running with --no-sandbox due to the locked down VM as an experiment.  Frankly, Trezor Suite is slowwwwww compared to Electrum or even regular Trezor io wallet.

Side note:  I am trying to plan for my heirs to have access to my coins IF/When I am gone.  Trezor Suite is easy for me but it would be confusing for non-Crypto heirs to figure out.  Trezor io wallet is easy BUT at this time they don't deal with bc1 addresses.  What the hell is up with that for a leading HW vendor?  I know you can send to bc1 addresses but its unimaginable to me that you can't setup a bc1 wallet on trezor io without being bound to Trezor Suite.  Frankly, its embarrassing for them.

I have laid out a plan for my heirs using Electrum and Trezor because bc1 is where you want to be, especially going forward.

Alright, so running as root without the --no-sandbox parameter is not permitted.



Did you check whether the file /tmp/.mount_Trezor7lPlMN/chrome-sandbox is indeed owned by root with mode 4755? (Note that the path might change slightly after each restart).
If not, enter the directory and do:

I went over to GitHub and grabbed a previous version of Trezor Suite (the previous version was GPG verified as GOOD too).  It fails to perform producing similar errors as the current 21.3.1.

Here are the errors reported below.  One instance was me as user trying to run AppImage in a user terminal.  Second was me elevating to sudo in a terminal.  There was a third instance where I actually went full root using a root terminal but it produced the same result as my user invoking sudo so I didn't paste it here.

Reminder: Right clicking the Desktop AppImage Icon and changing the properties dialogue to executable and then clicking on the Icon does nothing.

------------------------
user@debian:~$ cd Desktop
user@debian:~/Desktop$ ./Trezor-Suite-21.3.1-linux-x86_64.AppImage
[1980:0320/195209.105776:FATAL:setuid_sandbox_host.cc(158)] The SUID sandbox helper binary was found, but is not configured correctly. Rather than run without sandboxing I'm aborting now. You need to make sure that /tmp/.mount_Trezor7lPlMN/chrome-sandbox is owned by root and has mode 4755.
Trace/breakpoint trap

---------------------------

user@debian:~$ cd Desktop
user@debian:~/Desktop$ sudo ./Trezor-Suite-21.3.1-linux-x86_64.AppImage
[sudo] password for user:
[2082:0320/195504.314527:FATAL:electron_main_delegate.cc(253)] Running as root without --no-sandbox is not supported. See https://crbug.com/638180.
Trace/breakpoint trap
------------------------------

It appears that I will simply wait a month or so (to get out of beta) before getting involved with Trezor Suite.  A Virtual Machine running Debian Buster AppImage doesn't like it so far!  I don't want to run this on a bare metal machine so I don't know if the VM is introducing variables into the mix causing these errors.



ps - I am not involved in this project at GitHub.  If someone wants to copy and paste this to someone there feel free to do so.  I don't mind experimenting with things in my VM's if getting hands on would help them at all.

Guys thanks for the suggestions.  I am not home today but will give these a go tomorrow.  I will get back with the results.  Can't believe I never thought to attempt root/sudo in the terminal, LOL!  Yes there were error messages but I didn't record them to paste here.  This thread was started just to see if others are having issues.  I assume not too many are using Debian VM's to run Trezor Suite.  I am not in a super hurry to dive into Suite but I feel I should know my way around it since I am a long time crypto person.  Strangely, the Electrum AppImages run perfectly on these same systems giving me issues.

What output do you get?

Starting it via the command line should result in an log being forwarded to stdout.
Are there any error messages appearing? And Warning messages? Anything which could give a clue why it works with the --no-sandbox parameter?

Also, did you try it running as root (without the --no-sandbox) parameter? Does it work this way?

Trezor Suite is open source software and you can find all odler versions on their github page starting from v20.8.1.
You can download AppImage or try to compile yourself from source if you know what you are doing, but you will probably have some bugs in this beta software.
Best thing would be to report the issues you have in github and wait for them to get out of beta and that will happen next month I think.
https://github.com/trezor/trezor-suite/releases

BTW,

I forgot to mention that the AppImage will start if I invoke the no sandbox command.

./filename --no-sandbox

Not too keen on running in that mode, obviously!

Wasn't sure of the best forum for this.  Since its Trezor Suite I figured some here may know.  Decided to experiment with Trezor Suite 21.3.1 on Debian Desktop as AppImage.  Same result on two machines.  The AppImage won't open/mount.  I am running Electrum AppImage on both of these machines without any issues at all.  I GPG verified the downloads, which came back as GOOD!  AppImage is easy to use normally.  Just change permissions to be executable, click and go.  Not on 21.3.1.  BTW- I also tried ./ to run from a terminal and no go either.  Before I tear into this tomorrow I thought I would check to see if others here are running this latest version on a Debian machine?

Is there a location on trezor.io where I can download the previous version to examine that as well?  Maybe GitHub?  Starting here to see if I am the "lone ranger", which would be par for the course,LOL.