Conversation
Steam can mark a compatibility tool or runtime (Proton, Steam Linux Runtime) as fully installed (StateFlags bit 4) while its buildid stays 0, which means the download pipeline reported success without ever writing usable files to disk. Games depending on it then hang or fail silently, and every standard recovery step (verify integrity, delete manifest, steamcmd validate) is a no-op because Steam still believes the install is complete. SteamCompatibilityToolDiscovery already treats these as unusable, but silently drops them, leaving no signal in the UI about why a tool disappeared. Detection is generalized across every known Steam-library appid (all Proton versions and Steam Linux Runtime variants), not hardcoded to one, and a banner + guide dialog now explain the corruption and the manual recovery steps live in Steam's own console. This is diagnostic-only by design: ProtonPlus does not download depots or write Steam's appmanifest itself, since that would cross the project's existing boundary of never entering the installation workflow for externally-managed Steam library tools. Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_018UAYMTgUiHfHVpp9wEGco5
Word wrapping broke unbroken path/command tokens across many lines character-by-character. Give the dialog more room and let the monospace block scroll horizontally instead, since prose lines already carry their own manual line breaks. Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_018UAYMTgUiHfHVpp9wEGco5
Still too cramped for the command block even after the earlier width bump. Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_018UAYMTgUiHfHVpp9wEGco5
Adw.AlertDialog is a compact message-box widget that ignores content_width/content_height by design, which is why the dialog stayed small no matter how large those were set. Rebuilt it as a plain Adw.Dialog with a header bar and toolbar view, matching the pattern this codebase already uses for ReleaseChangelogDialog whenever a dialog needs real room for its content. Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_018UAYMTgUiHfHVpp9wEGco5
Owner
|
I am away for work till end of September/Early October. |
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
2 participants
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.
Thank you for contributing to ProtonPlus! Please complete the relevant sections below.
Category
Overview
Steam can mark a compatibility tool or runtime (Proton, Steam Linux Runtime) as fully installed (StateFlags bit 4) while its buildid stays 0, meaning the download pipeline reported success without ever writing usable files to disk. Games depending on it then hang or fail silently, and every standard recovery step (verify integrity, delete manifest, steamcmd validate) is a no-op because Steam still believes the install is complete.
SteamCompatibilityToolDiscovery already treated these as unusable but silently dropped them, leaving no signal in the UI about why a tool disappeared. This PR:
Issue Number
Related issue: #1232
New Variables or Dependencies
None. No new build scripts, environment variables, configuration options, or dependencies.
How to Test
Screenshots (if applicable)
If you've introduced any significant UI changes, please include a screenshot or a GIF.
Checklist
./scripts/build.sh translations(if applicable).Notes
Implemented with Claude Code, addressing #1232. Diagnostic-only as described above happy to adjust scope if maintainers want a different approach.