Relative paths not working in a playlist on linux

Description

Relative paths not working in a playlist on linux, only absolute paths.

Expected behavior

Launch a game from a playlist with relative path.

Actual behavior

The game is not launched.

Steps to reproduce the bug

1. Edit a playlist created previously with RetroArch interface than works well.
2. Replace absolute path like "/home/karl/.config/retroarch/roms/fbneo/1941.zip" with relative path like ":/roms/fbneo/1941.zip".
3. When try to launch the game from playlist, it not load

Bisect Results

I detected this when I was trying to prepare some playlist for my SteamDeck from my desktop installation.
I tried other relative path options like ":/cores/../roms/fbneo/1941.zip", "roms/fbneo/1941.zip" or "~/.config/retroarch/roms/fbneo/1941.zip", but no one work.

Relative paths works perfect for core line: "core_path": ":/cores/fbneo_libretro.so".

Version/Commit

1.19.1

Environment information

• OS: ArchLinux
• Compiler: Using official version in Arch Extra repository

Reproduce the issue on Linux using a playlist entry with the relative ROM paths shown in the report, comparing it with the working relative core path. Trace the playlist launch and path-resolution entry points to determine why the ROM path is not resolved; done means the listed relative ROM forms launch successfully without breaking absolute paths.