mirror of
https://github.com/shadps4-emu/shadPS4.git
synced 2026-04-27 08:46:03 +03:00
[GH-ISSUE #3193] [APP BUG]: Crash immediately if geometry_* settings are omitted from config.toml #987
Labels
No labels
Bloodborne
bug
contributor wanted
documentation
enhancement
frontend
good first issue
help wanted
linux
pull-request
question
release
verification progress
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/shadPS4#987
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @tomalexander on GitHub (Jul 5, 2025).
Original GitHub issue: https://github.com/shadps4-emu/shadPS4/issues/3193
Checklist
Describe the Bug
I am attempting to use a minimal
config.tomlthat only contains the settings that I need changed from the defaults, rather than the entire auto-generated config. When I do this, shadps4 crashes immediately upon launch. I have narrowed it down to the geometry_* settings.Reproduction Steps
config.tomlto populateconfig.tomlwith the auto-generated defaults. Then close shadps4.~/.local/share/shadPS4/config.toml. Under the[GUI]section, delete the lines forgeometry_(h|w|x|y).You will get:
floating point exception (core dumped) shadps4and shadps4 fails to launch.Expected Behavior
When settings are omitted from
config.toml, shadps4 should use the same default values that would be written to the auto-generatedconfig.toml. This way, when we encode our configs into our gitops setups (ansible, nix, or just committing your configs to a git repo), we can write only the settings that we've changed rather than including the full auto-generated config containing transient settings like window geometry.Specify OS Version
NixOS
CPU
AMD Ryzen 7 7840U
GPU
Radeon 780M
Amount of RAM in GB
96
@StevenMiller123 commented on GitHub (Jul 25, 2025):
The crash should be fixed now, since missing config.toml settings are regenerated on emulator startup.
Please let me know if this crash still occurs, and I will reopen the issue.