Skip to content
X-Plane 5 min read

How do I fix X-Plane scenery permission denied on Linux?

Adam McEnroe
In short

Fix X-Plane Custom Scenery permission denied errors on Linux by correcting ownership, folder modes and read-only or external-drive mounts safely.

To fix an X-Plane Custom Scenery "Permission denied" error on Linux, make the active Custom Scenery folder writable by your normal user, correct any root-owned files, and confirm the drive is mounted read-write. Do not run X-Plane, its installer, or your file manager as root.

Why does X-Plane scenery show Permission denied on Linux?

The error means your user account cannot create, replace, remove or read something in the destination folder. A mistake we see constantly is installing X-Plane with sudo, which leaves the simulator or its scenery owned by root.

Other common causes include:

  • The scenery is being copied into a different X-Plane installation from the one you actually use.
  • An archive was extracted as root, so its files retained unsuitable ownership.
  • The simulator is on a drive mounted read-only.
  • An NTFS, exFAT, FAT or network mount assigns ownership through mount settings rather than normal Linux file permissions.
  • A parent directory lacks the execute permission required to enter it.

How do I repair Custom Scenery permissions?

Repair the smallest relevant directory and keep X-Plane under your normal user account.

  1. Find the active X-Plane folder. Locate the installation containing the executable and Log.txt, then confirm that its scenery path is exactly /path/to/X-Plane/Custom Scenery. Linux paths are case-sensitive.
  2. Inspect its ownership and permissions. Run stat -c '%U:%G %A %n' "/path/to/X-Plane/Custom Scenery". The owner should normally be your user, and the permission string must allow that user to write to and enter the directory.
  3. Correct root ownership. For a single-user installation on a native Linux filesystem, run sudo chown -R "$USER":"$(id -gn)" "/path/to/X-Plane/Custom Scenery". If the entire standalone X-Plane installation was created as root, it is usually better to move or reinstall it in a user-writable location; our Linux installation guidance explains the safe ownership model.
  4. Restore user access. Run chmod -R u+rwX "/path/to/X-Plane/Custom Scenery". The capital X adds directory traversal without making every ordinary data file executable.
  5. Copy the package as your normal user. A terminal example is cp -r --no-preserve=ownership "$HOME/Downloads/Airport Name" "/path/to/X-Plane/Custom Scenery/". Adjust both paths for the real package and installation.
  6. Start X-Plane without sudo. If it still reports an access failure, inspect Log.txt for the exact path it could not read. That path often exposes a second installation, inaccessible library or nested package folder.

If Custom Scenery does not exist and you cannot create it, inspect the X-Plane parent folder. Do not take ownership of protected system directories merely to force an installation to work.

What if X-Plane is installed on an external drive or NAS?

If X-Plane is on external or network storage, fix the mount configuration rather than repeatedly running chmod.

Check the filesystem and mount options with findmnt -T "/path/to/X-Plane/Custom Scenery" -o TARGET,SOURCE,FSTYPE,OPTIONS.

ResultMeaningCorrect action
ro in the optionsThe filesystem is read-only.Unmount it cleanly, investigate any filesystem error, and remount it read-write. Folder permissions cannot override a read-only mount.
Native Linux filesystemNormal owner and mode rules apply.Use chown and chmod u+rwX on the affected X-Plane folder.
NTFS, exFAT or FATOwnership commonly comes from mount options.Mount it with your user and group IDs plus an appropriate mask. Changing ownership after mounting may have no effect.
Network shareLocal permissions may be limited by the server or share credentials.Correct the account, export and mount permissions instead of forcing local modes.

For symlinks, external disks and network locations, follow our guide to placing X-Plane 12 Custom Scenery on another drive or NAS. A noexec mount does not normally prevent copying scenery data, but it can affect packages containing Linux plugins or helper programs.

Should I use sudo or chmod 777?

Do not run X-Plane, its installer, an archive manager or routine scenery copies with sudo, and do not use chmod -R 777.

Using sudo for a one-off ownership repair is reasonable, but using it for installation creates more root-owned files and repeats the problem at the next update. Mode 777 grants every local user write access and hides the ownership mistake instead of fixing it. On a deliberately shared installation, configure a shared group or access control list rather than assigning everything to one user.

Why does the scenery still not appear after permissions are fixed?

If the copy succeeds but the airport remains missing, the remaining problem is usually package structure, scenery order or a missing library rather than Linux permissions.

  • Open the installed package and check that its actual scenery contents are not buried inside an extra wrapper directory. Our X-Plane 12 scenery installation instructions show the expected folder structure.
  • Confirm that you repaired and populated the Custom Scenery directory belonging to the installation you launched.
  • Check scenery_packs.ini after starting and closing X-Plane. Airport, overlay and mesh ordering can determine what is visible; see our scenery order and overlay guidance.
  • Read Log.txt for missing resources, libraries, case-mismatched filenames or plugin errors. Those require fixing the named dependency or package, not broadening filesystem permissions.
AI Assistant New

Still stuck? Ask Fly Away

Ask Fly Away is our AI flight-sim assistant. Ask your exact question and get a direct, step-by-step answer in seconds — free to try.

Ask Fly Away Free preview · unlimited for PRO members