Skip to content

[Switch] Duplicate entries in "history" playlist generating on latest nightly, "retroarch-salamander.cfg" most likely issue #19220

Description

@Megyomo

Is there an existing issue for this?

  • This is a bug in RetroArch frontend
  • I have searched the existing issues

Description

When I pick "load content" and asks me to pick a core it gets saved in "retroarch-salamander.cfg" as usual. The problem is it then never updates, assigning that same core to any other game I play, creating the duplicate entries. The duplicate entry ALSO gets the play time logged to it instead of my real game. If I pick games from any playlist, whether console playlists, "favorites" or "history" "retroarch-salamander.cfg" doesn't generate and I don't get duplicate entries so I believe "retroarch-salamander.cfg" is bugged on the latests Nintendo Switch nightly. "retroarch-salamander.cfg" can sometimes point to "Retroarch_Switch.nro" instead of the latest used core. Same issues apply

Expected behavior

When you start any game, whether from a playlist or from "load content", it should show you the correct core upon game startup. It should also leave only one entry on the "history" playlist with the play time correctly logged onto that entry.

Steps to reproduce the bug

  1. Delete "retroarch-salamander.cfg"
  2. Start Retroarch via title override (NOT a forwarder)
  3. Choose "Load Content" and load any game. It will ask you to load a core too. This will create the new "retroarch-salamander.cfg"
  4. Exit the game and load any game from another system.
  5. Exit that game and look into the "History" playlist; the duplicate entry with the wrongfully assigned core and play time will be there.

Version/Commit

1.22.2 2026/07/16 nightly

Bisect Results

Everything worked perfectly on the latest 1.22.2 stable. The latest stable can't be used on 21.x+ firmware, though.

Present in the nightly version

Yes, this is reproduced in the nightly build

Platform & operating system

Nintendo Switch 22.1.0 / AMS 1.11.1

Affected Cores

All of them

Environment information

No response

Relevant log output

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Fields

    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions