libretro / libretro/RetroArch

Core Updater: not showing cores

Open
#11,288 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

Description

Core Updater shows no cores. Setting core_updater_show_experimental_cores = "true" shows experimental cores with random names e.g. "3dengine_libretro.so.zip" instead of something like "NES / Famicom (Nestopia EU)"

Tried changing DNS and nothing. No firewall or VPN set on this network or machine. Had to change libretro_directory to home config coz Arch defaults to a system folder for pacman, but that only fixed downloading the experimental cores that I can see.

Expected behavior

I expected to see the cores with typical names like in most of the tutorials. I'm not seeing that.

Actual behavior

Cores aren't displaying. Experimental ones are displaying.

Steps to reproduce the bug
  1. Install on Arch Linux
  2. Enable Core Updater in config file
  3. Open Core Updater
Bisect Results

I'm new to this program, unfortunately I have no idea if this has started happening recently or when that might have been.

Version/Commit

-RetroArch: 1.9.0/5e551dd92b

Environment information
  • OS: ArchLinux kernel 5.4.62-1-lts
  • 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

Start by reproducing the Core Updater behavior on Arch Linux with the reported configuration, including libretro_directory and core_updater_show_experimental_cores. Trace the Core Updater entry point that builds the core list; done means standard cores appear with user-facing names such as "NES / Famicom (Nestopia EU)" rather than only experimental archive filenames.

Written by the indexing model from the issue text.

Assessment

Tech stack
arch-linux, c, linux
Domain
tooling
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.