libretro / libretro/RetroArch

Can't generate new cfg file properly on Windows 10, but works fine on linux with WINE.

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

as I mentioned in #11028 ,when I restart retroarch ,the program just won't show up.
If I delete the retroarch.cfg and restart, the program still can't start.

Expected behavior

retroarch should restart and reset config to default

Actual behavior

the newly generated cfg file contains only one line:

config_save_on_exit = "true"

Retroarch process just dies then.
Even a newly downloaded retroarch program cannot work properly.

Steps to reproduce the bug
  1. delete retroarch.cfg
  2. restart program
  3. the problem happens
Bisect Results
  • I haven't encountered this until recently, I'm using 1.8.9.
Version/Commit

You can find this information under Information/System Information

-RetroArch: RetroArch 1.8.9 (Git 4c6b139)

Environment information
  • OS: Windows 10 build 2004 x86_64 ,the system language is zh-cn
  • Compiler: [In case you are running local builds]

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 configuration-generation failure on Windows 10 build 2004 with RetroArch 1.8.9 and a deleted retroarch.cfg. Compare the generated file and restart behavior with Linux under WINE; done means a newly generated configuration contains the required settings and RetroArch restarts successfully instead of exiting.

Written by the indexing model from the issue text.

Assessment

Tech stack
c
Domain
operating-systems
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.