Repository navigation
FEX build: start Wine Steam as Steam starts itself - #753
Merged
Merged
Conversation
added 2 commits
November 1, 2026 13:17
On MetalSharp Wine (the fex build) Steam's UI never loaded when MetalSharp started it: the webhelper stopped before its message loop. Started without the steamwebhelper wrapper, the CEF flags and the environment's DLL overrides, it loads. On the fex build only: - no webhelper wrapper: deploy_steamwebhelper_wrapper and ensure_steam_launch_ready put Steam's own webhelper back as steamwebhelper.exe (restore_steam_webhelpers) instead, so a wrapper deployed before (or by Fix Steam) is undone at the next launch; refresh_stale_steamwebhelpers has nothing to refresh, and steamwebhelper_wrappers_ready is true - the Steam client starts without -no-cef-sandbox, -cef-single-process, -noverifyfiles and -no-dwrite (other arguments, such as steam://open/library, are kept) and without WINEDLLOVERRIDES; the registry's per-program overrides stay - `metalsharp-wine steam` does the same (facade version 3, so installed facades are rewritten) steam_process_test.py's Wine stand-in took a cold Steam start to be one with -no-cef-sandbox; it now also takes Steam.exe alone, and the test passes on both builds.
GitHub retires its macOS 14 runner images on November 2, 2026, and the C/C++/Obj-C and Metal jobs failed before starting during a scheduled brownout. Those jobs, the main CI's and the MonoKickstart build move to macos-15; nothing in them depends on macOS 14.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
On the FEX build (MetalSharp Wine), a Steam started by MetalSharp never showed its UI. Its webhelper stopped before its message loop. The same Steam, same runtime and same prefix, started as plain
steam.exeloaded normally. This makes MetalSharp's FEX Steam launch match that. The other build is unchanged.What changes on the FEX build
deploy_steamwebhelper_wrapperandensure_steam_launch_readynow put Steam's own webhelper back assteamwebhelper.exe(restore_steam_webhelpers). A wrapper deployed earlier, or by Fix Steam, is undone at the next launch.refresh_stale_steamwebhelpershas nothing to refresh, andsteamwebhelper_wrappers_readyreports ready.-no-cef-sandbox,-cef-single-process,-noverifyfilesand-no-dwrite. Other arguments are kept; activating a running Steam withsteam://open/librarystill works.WINEDLLOVERRIDESfrom the environment. The per-program overrides in the prefix's registry stay as they are.metalsharp-wine steamstarts Steam the same way.FACADE_VERSIONis now 3, so installed facades are rewritten.Tests
make VARIANT=fex testpasses.steam_process_test.pymodelled a cold Steam start as one with-no-cef-sandbox. Its Wine stand-in now also acceptsSteam.exealone, and the test passes against both the new and the previous backend.