Skip to content

Empty or unreadable Core directory hides Downloads directory #19405

Open

Description

@davidhedlund

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/cores or any writable folder) makes Downloads reappear.

Steps to reproduce the bug

  1. Launch RetroArch with:
    • No cores installed, or
    • Core directory set to an unreadable path.
  2. Go to Main Menu → Load Content.
  3. Observe that the Downloads directory is missing from the file browser.
  4. Go to Settings → Directory.
  5. Change Core Directory to a valid, readable path (e.g., /home/youruser/retroarch/cores).
  6. Return to Main Menu → Load Content.
  7. 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.cfg with 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.

Activity

  1. changed the title [-]AppImage: Default unreadable Core directory hides Downloads directory in Load Content[/-] [+]Unreadable Core directory hides Downloads directory[/+] on Aug 14, 2026
  2. changed the title [-]Unreadable Core directory hides Downloads directory[/-] [+]Empty Core directory hides Downloads directory[/+] on Aug 14, 2026
  3. changed the title [-]Empty Core directory hides Downloads directory[/-] [+]Empty or unreadable Core directory hides Downloads directory[/+] on Aug 14, 2026
  4. davidhedlund commented on Aug 21, 2026

    @davidhedlund
    ContributorAuthor

    @gouchi Good day. Do you know if this is intentional or not?

  5. gouchi commented on Aug 27, 2026

    @gouchi
    Member

    @davidhedlund If I understand correctly, it seems to be coming from this condition. You will need at least one pair of abc_libretro.so and abc_libretro.info to show Load Content > Downloads.

  6. davidhedlund commented on Sep 13, 2026

    @davidhedlund
    ContributorAuthor

    @gouchi Thank you very much for the review, and thank you @4RH1T3CT0R7 for fixing it!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions