protonscr

Broken Wine submodule reference in Proton repository

protonopen
ValveSoftware/Proton#8570 · opened 2025-03-28 by damnkrat · updated 2025-11-14 · 2 comments · github
1 matching comments, n / p to jump
Ddamnkrat 2025-03-28 github

I am currently investigating a broken Cyrillic input issue on Proton. However, I can't properly continue my investigation due to a broken submodule (Wine) reference. I'm trying to compile a range of Proton commits individually to troubleshoot a specific commit.

For a quick check, see wine folder at this commit:
https://github.com/ValveSoftware/Proton/tree/b5080e902c21d19e98eb9fd08d5670ed96acbe2c

It returns 404:
https://github.com/ValveSoftware/wine/tree/c244422700694cb551c8927d49ea241043d1a353

It seems that the referenced Wine commit is either missing, deleted, or moved from Valve's Wine repository. Because of that, performing a standard recursive git submodule update --init --recursive fails with:

❯ LC_ALL=C git submodule update --init --recursive
/usr/lib/git-core/git-remote-https: /usr/lib/steam/libcurl.so.4: no version information available (required by /usr/lib/git-core/git-remote-https)
/usr/lib/git-core/git-remote-https: /usr/lib/steam/libcurl.so.4: no version information available (required by /usr/lib/git-core/git-remote-https)
fatal: remote error: upload-pack: not our ref c244422700694cb551c8927d49ea241043d1a353
fatal: Fetched in submodule path 'wine', but it did not contain c244422700694cb551c8927d49ea241043d1a353. Direct fetching of that commit failed.

Could you please look into this?

PPierceLBrooks 2025-11-06 github

I have also encountered this issue on the experimental_10.0 branch, specifically with the experimental-10.0-20251023 tag.

CChiitoo 2025-11-14 github

Not sure what the situation was in March, but right now

https://github.com/ValveSoftware/Proton/tree/b5080e902c21d19e98eb9fd08d5670ed96acbe2c

wine seems to point to:

https://github.com/ValveSoftware/wine/tree/836060ee8b216b290e192f771d4f6e330e5e2420

Looking at 10.0-20251023 right now seems similar to me as well.

Testing b5080e902c2 locally also seems to do the right thing for me, so not sure if the problem is something local, or some kind of a temporary issue perhaps?

Proton versions