errors using UMU/Proton

[leahanderson1]

any boots after building the SDK do not launch, giving exit code 5.
The log only contains one line:
state level=info t=8 ev=account stage=identity primary=0x9EAA300100100100 characters=3

game boots when using vanilla wine, though.

[lutralutraq77]

Hi @leahanderson1 — could you try the diagnostic build from [this successful Windows CI run](https://github.com/lutralutraq77/Sunrise-work/actions/runs/33990738907)? It adds startup/SDK logging to help locate the failure; it isn’t a confirmed fix.

Back up your existing DLL, settings and generated SDK, then follow the [UMU/Proton logging instructions](https://github.com/lutralutraq77/Sunrise-work/blob/4d2404de6d4cd41283b789c0465b549a0eb5f65c/docs/umu-sdk-startup-diagnostics.md), including debug logging and PROTON_LOG=1. Please reproduce once and attach:

• The full Sunrise/logs/sunrise.log, Proton log (including any exception/backtrace), and UMU/launcher terminal output from that run.
• Exact Sunrise build/commit, UMU and Proton versions, plus the vanilla Wine version that works.
• Your launch command/options and environment variables, including DLL overrides and prefix selection.
• Whether working vanilla Wine and failing UMU/Proton used the same Wine prefix, game files and generated SDK. If different, please describe the differences and include a working Wine log if possible.

Save logs before another launch overwrites them, and redact credentials/personal details; no game files or SDK dumps are needed. The account-identity line is normal, and exit code 5 alone doesn’t identify the underlying error. Thanks!

[leahanderson1]

Hi @leahanderson1 — could you try the diagnostic build from [this successful Windows CI run](https://github.com/lutralutraq77/Sunrise-work/actions/runs/33990738907)? It adds startup/SDK logging to help locate the failure; it isn’t a confirmed fix.

Back up your existing DLL, settings and generated SDK, then follow the [UMU/Proton logging instructions](https://github.com/lutralutraq77/Sunrise-work/blob/4d2404de6d4cd41283b789c0465b549a0eb5f65c/docs/umu-sdk-startup-diagnostics.md), including debug logging and PROTON_LOG=1. Please reproduce once and attach:

* The full `Sunrise/logs/sunrise.log`, Proton log (including any exception/backtrace), and UMU/launcher terminal output from that run.

* Exact Sunrise build/commit, UMU and Proton versions, plus the vanilla Wine version that works.

* Your launch command/options and environment variables, including DLL overrides and prefix selection.

* Whether working vanilla Wine and failing UMU/Proton used the same Wine prefix, game files and generated SDK. If different, please describe the differences and include a working Wine log if possible.

Save logs before another launch overwrites them, and redact credentials/personal details; no game files or SDK dumps are needed. The account-identity line is normal, and exit code 5 alone doesn’t identify the underlying error. Thanks!

before i go diving down the rabbit hole of what you want me to do, i want to clarify some things.

This issue does not show up on Sunrise 0.3.2.

The current latest commit was used, commit a57dc9a.

wine version that "worked" was wine-11.17

each instance used separate prefixes.

I also tried with GE-Proton 11-3, which worked without any issue.

[stanuwu]

I use windows so I'll leave this one open until someone on Linux can confirm the exact cause or PR a fix

[Nyxaraa]

Using UMU and Proton 11.0 I am unable to replicate this bug, this might unfortunately be an issue with your setup or your proton prefix. If GE worked for you I'd be hesitant to say this is a bug with the src.

[leahanderson1]

Using UMU and Proton 11.0 I am unable to replicate this bug, this might unfortunately be an issue with your setup or your proton prefix. If GE worked for you I'd be hesitant to say this is a bug with the src.

i was using umu-proton 10

[Nyxaraa]

Tested with a clean proton 10 prefix and umu enabled, unable to replicate the issue.

[stanuwu]

Waiting for 1 more to try and replicate

[itstxl]

I hit a similar Proton issue, although it differed from exit code 5: Sunrise reached orbit, but every activity loaded indefinitely.

The standard log only reported sdk_generation result=fail ... detail="invalid_input". I added temporary diagnostic statuses to activity_sdk_live_publication, rebuilt the DLL, and reproduced the failure. This narrowed it to canonical_directory returning noncanonical_parent.

Proton was launching the game through Z:\home\..., where Wine exposed my Btrfs home subvolume as an intermediate reparse point. Sunrise rejected that ancestry while publishing activity_sdk.pack, so the pack and catalog were never committed and mission seeds could not resolve.

I fixed it without changing Sunrise's path validation: an isolated Proton prefix maps the game directory directly to Wine drive D: and launches D:\destiny2.exe. SDK generation then completed successfully and activities loaded normally.

Working launcher and documentation: https://github.com/itstxl/Sunrise/tree/feature/linux-proton-launcher/scripts/linux

[slhad]

I can confirm the Z:\ problem on Btrfs home too, Sunrise worked with Proton Experimental 11.0-100 on Arch

[3r1]

adding a symlink and running with "D:\destiny2.exe" instead of destiny2.exe works (simplified solution inspired from itstxl's script)

symlink game directory to d (fix z: sadness):
ln -s <gamedir> <prefixdir>/dosdevices/d:

wine command:
cd <gamedir> && WINEPREFIX=<prefix_dir> wine "D:\\destiny2.exe"

tested working on 0.5.1 with proton cachyos 11.0.20260703-1, Sunrise/sdk properly populated and playable (ty to everyone working on this btw)