Package Details: proton-native 4.11.9-1

Git Clone URL: (read-only)
Package Base: proton-native
Description: Compatibility tool for Steam Play based on Wine and additional components. Monolithic distribution
Upstream URL:
Licenses: GPL
Conflicts: proton-native
Provides: proton-native
Submitter: loathingkernel
Maintainer: loathingkernel
Last Packager: loathingkernel
Votes: 3
Popularity: 1.78
First Submitted: 2019-11-12 13:24
Last Updated: 2019-11-29 17:05

Dependencies (169)

Required by (0)

Sources (8)

Latest Comments

loathingkernel commented on 2019-11-13 19:57

It happens too me too, but not every time consistently. It is not going to forget it every time, but if it forgets it once, then it won't remember it at the next start.

My workaround has been to have a valve proton distribution selected in the global options and then select proton-native on a per game basis.

I don't know why it might be happening, it could be because it doesn't find the dist.lock file? But even if it was there, it should be user-writable, which defeats the whole system-wide installation.

If this happens for a title that has a native port, it will trigger a redownload, which in my case at least, is going to fail eventually to merge the newly downloaded files with the existing installation. In that case, the workaround I use, is to stop the download, select a Valve proton and restart a client.

This has happened to me no matter the way I have used to make steam aware of proton-native, either by placing it in /usr/share/steam/compatibilitytools.d or by the older way I used, by providing a compatibilitytools.vdf with a path to the install location (it used to be in /opt/proton-native)

yochananmarqos commented on 2019-11-13 15:54

If I choose to run other titles with proton-native and restart Steam, the Enable Steam Play for all other titles checkbox is unchecked. Checking it and restarting results in it being unchecked again.

loathingkernel commented on 2019-11-12 23:16

You make some good points. Thanks for testing it. Anyways, enjoy it and when you find any issues please report them!

yochananmarqos commented on 2019-11-12 22:50

I created my wine-mono-bin PKGBUILD right before I flagged your package out of date. I never noticed you updated it, heh.

You might be right about the versioning of python-ufoprocessor, that is odd they went from 1.0.6 > 1.7. If the next version is 1.0.8, then I'll have to add an epoch: 1:1.0.8.

I was going to add the python- prefix for psautohint, but it's more than just a Python library. Just like afdko, there are binaries. Just about every other distro that has that package calls it psautohint. See on Repology.

Now to try it out and play some games. Thanks for creating this!

loathingkernel commented on 2019-11-12 22:03

wine-mono-bin is one of my packages, I pushed the new version after the out-of-date flag.

nasm is a dependency of ffmpeg, added.

afdko is not my package, I just updated it and wrote PKGBUILDs for the missing components locally.

python-ufoprocessor is probably version 1.0.7 and not 1.7. In the git tags it is tagged as 1.07, probably they forgot a dot there as the previous one was 1.0.6. There isn't something you can do about it, but it will cause issues with the next version number if they go to 1.0.8.

I think psautohint should be named python-psautohint, at least that is what I named it in my case. Still, it is up to the maintainer of afdko to update it.

One last thing, it doesn't work with winelib versions of d9vk and dxvk. I can make it depend on some arbitrary name provided by the -mingw and -bin packages, but I only maintain d9vk.

Any other issues you can find, please report them.

yochananmarqos commented on 2019-11-12 21:18

In order for the font stuff to build, I had to update / fix a few things and wrote my own PKGBUILDs for required dependencies:

python-brotli & python-zopfli are required which are optional dependencies of python-fonttools.

nasm is needed:

nasm/yasm not found or too old. Use --disable-x86asm for a crippled build.

The only thing I was missing from the dependencies you added were opencl-headers and vulkan-headers, FYI.

I just started a clean build and it's looking good so far. Looks like it'll take awhile. I'l let you know if there are any more issues.

loathingkernel commented on 2019-11-12 19:38

I updated with the dependencies from arch wine. For afdko you can use this

yochananmarqos commented on 2019-11-12 16:44

fontforge is missing from makedepends():

fontforge -quiet -script ../proton/fonts/scripts/ obj-fonts/LiberationSans-Regular.sfd "Arial" "Arial" "Arial"
/bin/bash: fontforge: command not found

It still won't build as afdko is missing the ufoProcessor Python library. I'll work on that and update this comment as I go.

Traceback (most recent call last):
  File "/usr/sbin/makeotf", line 6, in <module>
    from pkg_resources import load_entry_point
  File "/usr/lib/python3.7/site-packages/pkg_resources/", line 3250, in <module>
  File "/usr/lib/python3.7/site-packages/pkg_resources/", line 3234, in _call_aside
    f(*args, **kwargs)
  File "/usr/lib/python3.7/site-packages/pkg_resources/", line 3263, in _initialize_master_working_set
    working_set = WorkingSet._build_master()
  File "/usr/lib/python3.7/site-packages/pkg_resources/", line 583, in _build_master
  File "/usr/lib/python3.7/site-packages/pkg_resources/", line 900, in require
    needed = self.resolve(parse_requirements(requirements))
  File "/usr/lib/python3.7/site-packages/pkg_resources/", line 786, in resolve
    raise DistributionNotFound(req, requirers)
pkg_resources.DistributionNotFound: The 'ufoProcessor==1.0.6' distribution was not found and is required by afdko
make[1]: *** [../proton/build/makefile_base.mak:1524: obj-fonts/SourceHanSansSCRegular.otf] Error 1
make[1]: Leaving directory '/home/yochanan/Documents/pkgbuilds/proton-native/src/build'
make: *** [../proton/build/makefile_base.mak:17: nested_make] Error 2