Empty or unreadable Core directory hides Downloads directory
Nobody has claimed this yet.
- Dominant language
- C
- Stars
- 14.1k
- Forks
- 2.2k
- Avg merge
- 7h 35m
- Merged PRs (30d)
- 51
Description
Is there an existing issue for this?
- I have searched the existing issues
- This is a bug in the RetroArch frontend
Description
When the Core directory is empty (e.g., no cores installed) or points to an unreadable path, the Downloads directory (~/.config/retroarch/downloads) disappears from the Load Content file browser.
This makes it impossible to browse or verify downloaded content via the GUI, even though the files exist on disk. The Downloads folder should remain visible for overview purposes, even if no cores are available to load the content.
Expected behavior
Maintaining consistency with the general file browser that can access all directory contents:
- The Downloads directory should be visible in Main Menu → Load Content regardless of:
- Whether the Core directory path is readable.
- Whether any cores are installed.
- Users should be able to browse the contents of Downloads even if no core can currently load those files.
Actual behavior
- If the Core directory is empty or unreadable:
- The Downloads directory does not appear in the Load Content file browser.
- Changing the Core directory to a valid, readable path (e.g.,
/home/youruser/retroarch/coresor any writable folder) makes Downloads reappear.
Steps to reproduce the bug
- Launch RetroArch with:
- No cores installed, or
- Core directory set to an unreadable path.
- Go to Main Menu → Load Content.
- Observe that the Downloads directory is missing from the file browser.
- Go to Settings → Directory.
- Change Core Directory to a valid, readable path (e.g.,
/home/youruser/retroarch/cores). - Return to Main Menu → Load Content.
- Observe that the Downloads directory is now visible.
Version/Commit
- 1.22.2 (Git 433f9bf)
- Also reproduced in current nightly builds.
Platform & operating system
- GNU/Linux
Affected Cores
- N/A (frontend behavior)
Environment information
- RetroArch releases
- AppImage
- Flatpak
- Default
retroarch.cfgwith Core directory set to/usr/lib/x86_64-linux-gnu/libretro/(or any unreadable/empty Core path)
Relevant log output
(Attach RetroArch log if available; otherwise leave blank)
Additional notes
- This is primarily a UX issue: users should be able to inspect the Downloads folder even if no cores are installed yet.
- Fix suggestion: decouple the visibility of the Downloads directory in the file browser from the validity/readability of the Core directory.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start in the Main Menu → Load Content file-browser handling and trace how Core Directory readability affects the Downloads directory entry. Reproduce with an empty or unreadable Core Directory, then verify that Downloads remains visible and browsable regardless of whether cores are installed.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- c
- Domain
- frontend
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Active
- Clarity
- Mostly clear
- Newbie friendliness
- 64/100