The folder with Tropy-related files is actually all there is: the ‘installation’ is just to to move the folder to a convenient place and make Tropy known to your desktop environment so that you can start it by clicking on its icon. So this means that starting the ‘tropy’ file in that folder should actually just start Tropy. You mentioned that your attempt to open that file resulted in a pop-up – but how did you try to open it? I don’t know have a Chromebook myself, but I would guess that it might not be possible to launch binaries by clicking on them in the Files app. If that’s what you did, can you try to open the folder in the terminal and to start binary there?
If you’ve downloaded the tar.bz2 to your Downloads folder you could do this:
- Open the terminal
- Go to the Downloads folder:
cd ~/Downloads - Make a folder to unpack Tropy (we can move/install the folder later when we know that Tropy can be started):
mkdir tropy - Unpack the archive:
tar xjf tropy-1.9.0-x64.tar.bz2 -C ./tropy - Go to the folder
cd tropy - And try to launch tropy with
./tropy
If Tropy starts, we’re good. In this case we should move the folder to more permanent location and I register the application so that you get a launcher icon and don’t have to use the terminal to start Tropy – these are the instructions in the INSTALL file, but I need to do some research to check if those steps apply on Chrome OS too.
If Tropy does not start, please post the corresponding error message. If it is something security/sandbox related, you might try the following steps right away (still in the new Tropy folder):
./tropy --no-sandbox
Or, if this doesn’t work then:
sudo chown root chrome-sandbox
Followed by
sudo chmod 4755 chrome-sandbox
And then try again to launch Tropy with ./tropy