Package Details: proton-ge-custom-bin 1:GE_Proton9_20-1

Git Clone URL: https://aur.archlinux.org/proton-ge-custom-bin.git (read-only, click to copy)
Package Base: proton-ge-custom-bin
Description: A fancy custom distribution of Valves Proton with various patches
Upstream URL: https://github.com/GloriousEggroll/proton-ge-custom
Keywords: d9vk DXVK Faudio GloriousEggroll MediaFoundation Proton protonfixes Steam System-wide Valve vkd3d Wine
Licenses: custom, BSD, MPL, LGPL, MIT, zlib
Conflicts: proton-ge-custom
Provides: proton, proton-ge-custom
Submitter: RogueGirl
Maintainer: Jaja (floriplum, chaotic-aur, PedroHLC)
Last Packager: chaotic-aur
Votes: 215
Popularity: 7.38
First Submitted: 2020-02-21 11:06 (UTC)
Last Updated: 2024-11-11 11:31 (UTC)

Dependencies (28)

Required by (7)

Sources (4)

Pinned Comments

PedroHLC commented on 2021-07-27 19:39 (UTC)

The "chaotic-aur" co-maintainer is a bot that pulls any merged PR in https://github.com/chaotic-aur/pkgbuild-proton-ge-custom-bin back to this package. So if you guys have contributions or bump versions earlier than the maintainer, please share them as PRs. The commits will keep your authorship.

Happy gaming!

Latest Comments

« First ‹ Previous 1 2 3 4 5 6 7 8 .. 26 Next › Last »

KevinFumbles commented on 2023-04-09 03:29 (UTC) (edited on 2023-04-09 03:30 (UTC) by KevinFumbles)

@adambyte @Jaja it seems like if I go to the Preferences, go to the Third Party tab, and click "Clean" under the build directory, it updates this package correctly. Thanks for your comment, it's what made me to think of doing that.

It looks like Add/Remove Software's default build dir is under /tmp, so Manjaro users should be able to do fix this issue by pressing the Clean button in the GUI or by running rm -rf /tmp/pamac-build-%USER% in the terminal.

Gotta love the Linux community :D

Jaja commented on 2023-04-03 12:49 (UTC) (edited on 2023-04-03 12:53 (UTC) by Jaja)

@adambyte @KevinFumbles No, that is not how it works. The file "pleasenote.install" is to be found within the git repo itself that is hosted on the AUR along with the PKGBUILD file and other stuff. These are not files referenced by the source=() array, but used by makepkg command according to instructions stated by the PKGBUILD.

It seems to me like pamac has some issues to clone the repo correctly. Some suggestions:

  1. If you can find the folder that pamac uses to clone the repo, you could delete it and try again. I would look for it under ~/.cache, but I do not know how pamac works in detail.

  2. You could skip using the AUR for this package and use a pacman repo that has this package already pre-build for you. It is still the same package, though. You could use https://aur.chaotic.cx/ for this.

  3. You could build the package yourself without any AUR helper:

$ git clone https://aur.archlinux.org/proton-ge-custom-bin.git
$ cd proton-ge-custom-bin
$ makepkg
$ pacman -U *.zst

adambyte commented on 2023-03-23 17:15 (UTC)

@KevinFumbles @Jaja I'm getting the same problem. As a total AUR noob, I'm guessing that the problem is that the file pleasenote.install isn't listed under the package's "Sources," and so it doesn't get downloaded and added to the build environment, and then the build process gets aborted by a sanity check that is meant to confirm the existence of all required files.

KevinFumbles commented on 2022-11-12 03:41 (UTC)

@Jaja whoops, didn't see your reply until now. I'm using Add/Remove Software on Manjaro, which is pamac under the hood. If I run "pamac update" manually, I actually get a more helpful error message:

Preparing... Synchronizing package databases... Cloning proton-ge-custom-bin build files... Generating proton-ge-custom-bin information... ==> ERROR: install file (pleasenote.install) does not exist or is not a regular file. Error: Failed to prepare transaction: Failed to generate proton-ge-custom-bin information

I see the pleasenote.install file under the makepkg "install" option from the PKGBUILD. Not exactly sure what this is though, and why it's not there for me. Is this something that's supposed to be in the release tar?

Gigas002 commented on 2022-11-11 01:39 (UTC) (edited on 2022-11-11 01:45 (UTC) by Gigas002)

Why does in-game dxvk hud always tells me I'm running with dxvk 1.10.1-async, though package seems to contain dxvk builds from git (2.0)? I tried manually replacing libraries in game's pfx, tried changing version in proton-ge's dxvk dirs in /usr/share/steam/compatibilitytools.d/proton-ge-custom/files/, but nothing helps at all. I tried doing the same thing with proton-ge-custom package, thinking it was this package's prebuilt error, but no. That's been bugging me for several months and I still can't find an answer

Jaja commented on 2022-10-29 09:44 (UTC)

@KevinFumbles which program gives you this error message?

KevinFumbles commented on 2022-10-29 05:02 (UTC)

I'm getting this error: Failed to generate proton-ge-custom-bin information

Can anyone help me figure out what I'm doing wrong? I am just using Add/Remove Software, and I've already tried refreshing the mirrorlist, as well as restarting.

Jaja commented on 2022-09-24 09:24 (UTC)

@kreimben try to delete the files prior to building the packet. Your aur helper is not clever enough to download the files again if checksum failed - so you most likely still have the older versions on your drive.

kreimben commented on 2022-09-24 02:21 (UTC)

==> Validating source files with sha512sums...
    GE-Proton7-35_1.tar.gz ... Passed
    user_settings.py ... FAILED
    launcher.sh ... FAILED
    pam_limits.conf ... Passed
==> ERROR: One or more files did not pass the validity check!
 -> error making: proton-ge-custom-bin

user_settings.py failed!

Jaja commented on 2022-09-20 07:40 (UTC)

@quenyen if you refer to small changes like the latest in the launcher script, settings file and dependencies, I usually do not bump the package release. Doing so would force an update for everybody with little to no benefit for most users. The package gets updated upstream often enough to have those changes deployed soon enough. In case of fixing wrong checksums, incrementing the release number does not make sense at all.