libretro / libretro/RetroArch

Root folders missing from File Browser

Open
#10,580 5 comments 0 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

First and foremost consider this:

  • Only RetroArch bugs should be filed here. Not core bugs or game bugs
  • This is not a forum or a help section, this is strictly developer oriented

Description

On linux file browser doesn't recognise user created directories at /
For example /test/dir

Expected behavior

File browser lists all dir's in /
For example
/bin
/boot
/dev
/test

Actual behavior

Dir's in / are not shown in the file browser

Steps to reproduce the bug
  1. Install Retroarch via snap.
    sudo snap install retroarch
  2. Create a dir.
    sudo mkdir /test
  3. Launch retroarch
  4. Settings > Directories
  5. Edit directory and select /

Also tried

  • running retroarch as sudo.
  • checked chown on dir which is set to root:root
  • uninstall/reinstall
  • running as another user
  • scanned code base looking for anything obvious that would limit the display of dir's
  • searched past issues + forums
    all with no luck.
Bisect Results

Fresh install of Retroarch on Debian via SnapCraft.io.

Version/Commit
  • RetroArch: 1.8.6
Environment information
  • OS: Debian Buster
  • Compiler: N.A

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

Reproduce the issue using the documented Snap installation, create /test, and open Settings > Directories to select /. Start by tracing the root directory listing from that browser entry point. Done means user-created directories such as /test appear alongside /bin, /boot, and /dev on Debian when using the reported setup.

Written by the indexing model from the issue text.

Assessment

Tech stack
c, linux
Domain
frontend, 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.