2x different costume core name in Load Core

Description and Steps to reproduce the bug

Sometimes I do build libretro-core from Official Git Emulator and Git-Libretro, also I do build different git-branch in repository and for this way i have to use my costume core name. I noticed this names double mirrored in Menu - Load Core , if used special sort... Example: yabause and his branches

$ ls -1 /usr/lib64/libretro/ | grep yabause
__lr.yabause-kronos.so
__lr.yabause-yabasanshiro.so
__lr.yabause.so
$ ls -1 /usr/lib64/libretro/info/ | grep yabause
__lr.yabause-kronos.info
__lr.yabause-yabasanshiro.info
__lr.yabause.info
$ cat /usr/lib64/libretro/info/__lr.yabause* | grep display_name
display_name = "__lr.yabause-kronos 200926"
display_name = "__lr.yabause-yabasanshiro 200908"
display_name = "__lr.yabause 200605"

I see in Load Core double yabause w/o different:

__lr.yabause
__lr.yabause
__lr.yabause-kronos

RetroArch-1.9.0:

I'm tried to remove info-files and tried xmb-theme too. From last screen you can see this show_bug in action for other cores. Example, _pcsx-rearmed, core.so from:

• https://github.com/libretro/pcsx_rearmed
• https://github.com/notaz/pcsx_rearmed

└─$  ls -1 /usr/lib64/libretro/ | grep _pcsx-rearmed
_pcsx-rearmed.so
_pcsx-rearmed_lr.so
└─$ cat /usr/lib64/libretro/info/_pcsx-rearmed* |grep display_name
display_name = "_pcsx-rearmed 200704"
display_name = "_pcsx-rearmed_lr 200910"

But for some cores i see correct (ex. _picodrive):

└─$ ls -1 /usr/lib64/libretro/ | grep _picodrive
_picodrive.so
_picodrive_lr.so
└─$ cat /usr/lib64/libretro/info/_picodrive* |grep display_name
display_name = "_picodrive 200314"
display_name = "_picodrive_lr 200816"

After my action, I tried to install RetroArch-1.8.2 and all is good then:

• Expected behavior: Different names, how in old version
• Actual behavior: 2x/mirrored different bin cores with and w/o info-files
• Bisect Results: RetroArch: 1.8.9 and 1.9.0 - this bug detected, maybe earlier
• Versions: RetroArch_1.9.0 / Slackware Linux 14.2 / GCC (5.5.0) 64-bit

upd.2022-03-07

Ok, what's going on. Trouble in non-standart name_core w/o _libretro.{so,info} at the end.

• Example: quicknes-20220228.516_e6f08c1

$ ls /usr/lib64/libretro/info/{.,..} |grep '.quicknes'
__lr.quicknes.info
__lr.quicknes_libretro.info
__lr.quicknes.so
__lr.quicknes_libretro.so
$ md5sum /usr/lib64/libretro/info/__lr.quicknes*
e54210cb7c90042bd60401b5766e42e3  /usr/lib64/libretro/info/__lr.quicknes.info
e54210cb7c90042bd60401b5766e42e3  /usr/lib64/libretro/info/__lr.quicknes_libretro.info

$ cat /usr/lib64/libretro/info/__lr.quicknes_libretro.info
# Software Information
display_name = "__lr.quicknes 220228"
authors = "blargg|kode54"
supported_extensions = "nes"
corename = "QuickNES"
license = "LGPLv2.1+"
permissions = ""
display_version = "Git | 516.20220228"
categories = "Emulator"

# Hardware Information
manufacturer = "Nintendo"
systemname = "Nintendo Entertainment System"
systemid = "nes"

# Libretro Features
supports_no_game = "false"
database = "Nintendo - Nintendo Entertainment System"
savestate = "true"
savestate_features = "deterministic"
cheats = "false"
input_descriptors = "true"
memory_descriptors = "true"
libretro_saves = "true"
core_options = "true"
load_subsystem = "false"
hw_render = "false"
needs_fullpath = "false"
disk_control = "false"
is_experimental = "false"

description = "QuickNES is the fastest NES emulator available via libretro, though this speed comes at the cost of some accuracy. This core should be used only when performance is of the utmost concern and even FCEUmm is too demanding."

Start by reproducing the issue in the Load Core menu with the listed yabause, pcsx-rearmed, picodrive, and quicknes .so/.info filename pairs, comparing the 1.9.0 behavior with 1.8.2. Trace how core filenames and their info files become menu names; done means differently named cores appear once each, including cores with non-standard names or missing suffixes.