libretro / libretro/RetroArch

[SteamOS / Flatpak] Can't stack shader presets due to path mismatch

Open
#15,503 2 comments 3 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
C
Stars
14.1k
Forks
2.2k
Avg merge
7h 35m
Merged PRs (30d)
51

Description

Description

On Steam Deck Linux, using the Flatpak build of RetroArch 1.15.1, load any shader preset and then attempt to append or prepend any other preset. The operation will fail.

Actual behavior

The log reveals the problem:

[WARN] [Shaders]: Could not read root preset: "/app/share/libretro/shaders/retroarch.slangp".

There is no retroarch.slangp present in that location. The stock presets are stored there, but retroarch.slangp is actually located at /home/deck/.var/app/org.libretro.RetroArch/config/retroarch/config/retroarch.slangp. Symlinking the latter to the former has been tested and seems to rectify the problem.

Expected behavior

RetroArch should locate the file without me having to symlink it after every update.

Steps to reproduce the bug

See above.

Version/Commit
  • RetroArch: 1.15.1 (Installed from Flathub via the Steam OS Discover app)
Environment information
  • OS: Steam Deck OS 3.4.8

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by tracing shader preset append/prepend handling and how the Flatpak build resolves the root preset path. Reproduce on SteamOS with RetroArch 1.15.1, compare /app/share/libretro/shaders/retroarch.slangp with the config path under /home/deck/.var/app/org.libretro.RetroArch, and verify presets can be stacked without a symlink.

Written by the indexing model from the issue text.

Assessment

Tech stack
c
Domain
computer-graphics, operating-systems
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
38/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.