Installing and running Foundry VTT?

Hi, it's me again! I'm trying to figure out how to install/run Foundry VTT but the instructions in the foundry installation guide aren't getting me anywhere.

Running it with sudo apt got me this:

Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
E: Unable to locate package foundryvtt

Foundry vtt is a virtual tabletop for online tabletop gaming.

downloaded from https://foundryvtt.com as a .zip file.
Instructions say to run

unzip foundryvtt.zip -d $HOME/foundryvtt

and then run ./foundryvtt or rename the file with a .sh so it can be run with a double click. None of this seems to work. I extracted using Caja instead.

Trying to run it from pluma briefly opens a window which closes and does nothing. Trying to open the file in Pluma prompts me to select the Character Encoding type, which I don't know.

Am I missing something? Am I not going to be able to run a game for my pathfinder group?

When you run the program using the terminal, is there any output at all?

cd $HOME/foundryvtt
./foundryvtt

If the program fails to launch, usually they'd be a library error, then we know it's down to missing/incompatible dependencies.

Since we don't own this paid software, please let us know:

  1. What Ubuntu MATE version are you running?

  2. What is this file? I'm guessing a binary?

    file ./foundryvtt
    
  3. Are there other files in that package?

  4. What libraries does it need?

    ldd ./foundryvtt
    

Unless I didn't look deep enough, the details on their site are pretty light of what kind of program this is.

1 Like

Okay, let's see here. I'm running MATE 1.26.2. After extracting the zip file, it's a set of several libraries and the file I'm trying to run should be an executable. I have them all in a single folder with the zip file's native subfolders. I do have it checked to allow running as an executable. When I double click it or right click and select run as administrator, a white box briefly comes up and then disappears before I can even see what it's saying.

Please could you provide the output of this command? Using the :terminal: Terminal from the extracted folder (which should be in your home directory):

cd ~/foundryvtt
ldd ./foundryvtt

The ldd command should list what libraries it needs. You might need to tell us what's inside that folder, in case it's overriding with its own libraries.

ls

For the Ubuntu MATE version - it can be found from this command:

lsb_release -a

Not sure if the white box window is the terminal, or the application itself. If you start it from the terminal, if it throws an error, it should persist.

2 Likes

Okay so! I figured out how to open the terminal from the folder, which was new to me. Running ldd ./foundryvtt got me a whole lot of stuff, most of which appears to be located in my native filesystem. One is the name of another file present in the extracted folder, libffmpeg.so.

trying again to run it from this properly localized console now returns the following: 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 /home/user/FoundryVTT/chrome-sandbox is owned by root and has mode 4755.
Trace/breakpoint trap (core dumped)

Apologies, I should've given clearer instructions how to easily open the terminal.

The SUID sandbox helper binary was found, but is not configured correctly.

Thanks! This sounds familiar, it's an Electron application. Essentially a web application running on the local computer.

To fix, run these commands in the terminal:

sudo chown root /home/user/FoundryVTT/chrome-sandbox

and:

sudo chmod 4755 /home/user/FoundryVTT/chrome-sandbox

(The * won't appear when typing your user password for sudo)

Your program should then launch when you double click it and click "Run".

Apparently, this happens because the program is using an older way of handling this sandbox [1]. Those commands satisfy its requirements by saying "root owns this chrome-sandbox executable; and when executed, run as the owner (root user)". Another Electron app had the same problem, not sure if it's due to newer Ubuntu versions.

5 Likes

It worked! Thank you so much!

2 Likes