Differences
This shows you the differences between two versions of the page.
| Both sides previous revision Previous revision Next revision | Previous revision | ||
|
stacker:docs:linux_installation_instructions [2020/03/04 23:00] rjlittlefield |
stacker:docs:linux_installation_instructions [2025/10/01 16:50] (current) rjlittlefield /tmp limits versus new projects location |
||
|---|---|---|---|
| Line 28: | Line 28: | ||
| chmod +x ZereneStacker/jre/lib/jspawnhelper | chmod +x ZereneStacker/jre/lib/jspawnhelper | ||
| </code> | </code> | ||
| + | * Be sure that you have downloaded the version of Zerene Stacker that matches your version of Linux. Attempting to run the 32-bit version of Zerene Stacker on a 64-bit Linux, or vice versa, may produce some confusing diagnostic like "cannot execute: required file not found", even though the ZereneStacker executable program is clearly present. \\ \\ | ||
| + | * On some Linux installations, there are stringent limits on the amount of data that can be written into /tmp . This can cause Zerene Stacker to be aborted with a **java.io.IOException: Disk quota exceeded**. The best and simplest solution to this problem is to make Zerene Stacker create new projects in some folder in your account's main file space. The location for new projects is specified at Options > Preferences > Project Settings. Select "In specified directory" and either use the Choose button or just type in a path to an ordinary folder in your account's file space. Whatever you set will be remembered across launches of Zerene Stacker, so you need to do this only once. \\ \\ If you plan to save projects, and the device for that saving is reasonably fast, then the most efficient approach is to create new projects on the same device where they'll be saved. That way the Save Project function only has to move/rename the project folder instead of copying it. | ||
| + | |||