Package Details: proton 5.13.5-1

Git Clone URL: (read-only, click to copy)
Package Base: proton
Description: Compatibility tool for Steam Play based on Wine and additional components
Upstream URL:
Licenses: BSD
Submitter: Forty-Bot
Maintainer: heavysink (lilac)
Last Packager: heavysink
Votes: 76
Popularity: 0.94
First Submitted: 2018-08-22 01:23
Last Updated: 2021-01-30 14:03

Pinned Comments

heavysink commented on 2020-07-31 01:35

I haven't found a solution to this for now... I cannot compile it due to 'wine_dlsym' I think it is from upstream after updating wine-valve.

EDIT: proton-git still have this problem... I submitted an issue on Github:

MagicAndWires commented on 2019-11-01 16:06

To the people getting the wine/wined3d-interop.h: No such file or directory the 4.17 proton requires a wine-valve version >=4.16, install wine-valve-git instead.

After some consideration, because new versions of proton require code that has not been released as a stable version yet any kind of "stable" package for wine-valve is going to be hell to maintain and always lagging slightly behind.

If anyone wants to continue a stable package despite this, I've disowned the package so you're welcome to give it a shot, but I'd advise users to just install wine-valve-git instead.

(No changes to the proton PKGBUILD necessary).

Forty-Bot commented on 2018-08-22 01:24

This is in an early state right now. vrclient_x64 needs the custom bundled version of wine, which I plan to make another package for. For now all that's packaged is lsteamclient.

Latest Comments

1 2 3 4 5 6 ... Next › Last »

EgidioCaprino commented on 2020-12-11 21:07

I'm getting this error when installing. Can you please help me?

heavysink commented on 2020-12-10 19:20

@ynikitenko update is on the way. I think you just ask each game to use custom proton and point it to the installed proton.

ynikitenko commented on 2020-12-10 18:21

Could you please update the package? The most recent version is proton-5.13-4, and it is the only one that supports Cyberpunk 2077 (which was released today). Do I understand right that there is no "proton" executable, and just several libraries and I have to use steam to run a game?

EgidioCaprino commented on 2020-12-05 17:57

==> ERROR: Could not resolve all dependencies.
error making: vkd3d-valve

heavysink commented on 2020-10-23 18:58

Sorry everyone, I forgot to change the version number to trigger rebuild at lilac. The lilac build bot will automatically update the version number tonight.

sperg512 commented on 2020-10-22 12:57

Exactly. I think I know how to fix the problem and I'm gonna test it, it's just an undefined reference error.

Edit: yep, as I suspected, the patch should be removed to let it build properly. I'm 99% that having dlopen instead of wine_dlopen, etc is completely unnecessary. I'll do some testing

Edit2: yeah there's no reason for the patch. dlopen, dlsym aren't deprecated in Wine anymore iirc? but it does work sooo

thaewrapt commented on 2020-10-20 09:30

Yeah, it makes no sense to build (and ship) 5.0.9 if PKGBUILD states 5.1.13b as the version, so it's not only out-of-date but the package itself is broken. Either make pkgver 5.0.9 or provide a new version.

loathingkernel commented on 2020-10-20 08:03

@xiretza the issue is in the PKGBUILD itself. It sources $_pkgver to download the source, which is still set to 5.0-9. .SRCINFO is autogenerated. Unless you have modified the PKGBUILD yourself, what you are building fine in a clean chroot is in fact the sources for 5.0-9

xiretza commented on 2020-10-19 11:46

Package builds fine in a clean chroot here, maintainer simply forgot to update the source = in .SRCINFO, which causes the aurweb interface to show the old URL under "Sources".

loathingkernel commented on 2020-10-19 07:57

@sperg512 Then what is the reasoning behind updating the version number?