Package Details: proton-ge-custom-bin 1:GE_Proton9_19-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: 214
Popularity: 7.73
First Submitted: 2020-02-21 11:06 (UTC)
Last Updated: 2024-11-10 11:13 (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 .. 8 9 10 11 12 13 14 15 16 17 18 .. 26 Next › Last »

superboringdev commented on 2021-04-22 19:03 (UTC)

I'm hoping that this will be fixed in 6.6. There already is a tag for 6.6-GE-1.

Unfortunately, I haven't been able to build proton-ge-custom, so I'm not able to test that. Do you have it built on your end?

Thanks

floriplum commented on 2021-04-22 18:23 (UTC)

Unless it is something we can fix by changing the included script to start proton we need to wait for an upstream fix(since we use the pre-compiled binary).

We should try to run a program with the default proton tarball(maybe i can try that later), if it doesnt work someone could report it to GloriousEggroll.
But since you need to contact him through discord, that is something i cant do since i dont have a discord account.

Greetings
Flori.

superboringdev commented on 2021-04-22 18:07 (UTC) (edited on 2021-04-22 18:07 (UTC) by superboringdev)

Been having the same issue:

Application could not be started, or no application associated with the specified file.
ShellExecuteEx failed: File not found.

Any news on this topic? The hotfix does not appear to work (or at least not for this). Also tried a fresh wine prefix; didn't work either.

unit73e commented on 2021-04-16 23:07 (UTC) (edited on 2021-04-16 23:17 (UTC) by unit73e)

Works on Steam but standalone execution is not working after all. Not sure what the problem is yet, it just says 'ShellExecuteEx failed: File not found.' without much details. I'll check more tomorrow.

EDIT: Meanwhile I downgraded to 6.4 and it works. It seems like any version of 6.5 fails with that error.

EDIT2: Nevermind. The problem was already known. I'm upgrading manually to 6.6 to see what happens. I'll post a patch today. Scratch that, not released yet so anyone who wants to run standalone will have to use 6.4.

unit73e commented on 2021-04-12 08:43 (UTC)

@floriplum just tested. Works for me. Thanks.

floriplum commented on 2021-04-09 19:34 (UTC)

The hash was actually correct, the problem is that hot-fixes are released under the same URL.
While updating the checksum i also changed to sha512 as a hashing algorithm since these are now officially provided with the release.

osmium commented on 2021-04-09 18:31 (UTC) (edited on 2021-04-09 18:32 (UTC) by osmium)

[WORKAROUND] Skipping the validity check using yay:
yay -S --mflags --skipinteg proton-ge-custom-bin

zangoku commented on 2021-04-09 04:53 (UTC)

==> Validating source files with sha256sums... proton-ge-custom-6.5-GE-2_1.tar.gz ... FAILED supplementary.tar.zst ... Passed ==> ERROR: One or more files did not pass the validity check!

verifying the integrity fails for the reason mentioned by @le_tucan

le_tucan commented on 2021-04-08 20:20 (UTC) (edited on 2021-04-08 20:20 (UTC) by le_tucan)

The first sha256 hash is not correct in the PKGBUILD, 22418b5349e4f86c6ccd166f4dc126d94556ca648be0e35b9b36966f6803c194 is the correct hash.

« First ‹ Previous 1 .. 8 9 10 11 12 13 14 15 16 17 18 .. 26 Next › Last »