Arch Linux User Repository

• This is a self-updating package that automatically attempts to use the latest prerelease AppImage.

  • Do not flag or comment to request mere version bumps until a month has passed since the last update.

• Problems:

  • Try building in a clean chroot. Shouldn't matter for this package, but worth trying.
  • Shutdown or uninstall appimagelauncher because it "intercepts all attempts to open an AppImage". Similar tools may have the same problem.
    • Restart binfmt: sudo systemctl restart systemd-binfmt

• Upstream developers have indicated they do not wish to be disturbed about downstream packaging issues.

  • Test the AppImage directly before reporting any bugs upstream. Properly confirmed bugs should have no need to mention downstream packaging.
  • Report problems with this package here.
    • Avoid flagging and commenting at the same time for the same issue.
    • Flag for common issues with standard solutions (eg, depends updates).
    • Comment for issues that require explanation or debugging.

I receive an error (/usr/bin/pcsx2-qt: line 10: /usr/bin/apprun-hooks/linuxdeploy-plugin-qt-hook.sh: No such file or directory) when starting the app. Looking into the package, this file is located under /opt/pcsx2/usr/bin/apprun-hooks/linuxdeploy-plugin-qt-hook.sh. So basically the same, but with /opt/pcsx2 prepended. Does anyone know how to work around, except for linking the file there?

I started get the following error today from yay

install: cannot stat '/home/user/.cache/yay/pcsx2-latest-bin/src/squashfs-root/PCSX2.desktop': No such file or directory

Is it because this package builds pcsx2-qt.desktop?

• This is a self-updating package that automatically attempts to use the latest prerelease AppImage.

  • Do not flag or comment to request mere version bumps until a month has passed since the last update.

• Problems:

  • Try building in a clean chroot. Shouldn't matter for this package, but worth trying.
  • Shutdown or uninstall appimagelauncher because it "intercepts all attempts to open an AppImage". Similar tools may have the same problem.
    • Restart binfmt: sudo systemctl restart systemd-binfmt

• Upstream developers have indicated they do not wish to be disturbed about downstream packaging issues.

  • Test the AppImage directly before reporting any bugs upstream. Properly confirmed bugs should have no need to mention downstream packaging.
  • Report problems with this package here.
    • Avoid flagging and commenting at the same time for the same issue.
    • Flag for common issues with standard solutions (eg, depends updates).
    • Comment for issues that require explanation or debugging.

Hey, thanks for making this package, I was thinking about something like this as well. I have one minor gripe though - when the upstream pushes a new commit, there seems to be some period of time where a github tag exists, but the download is still unavailable (right now I can't download a release from over half an hour ago because it doesn't exist).

So I think the "right" way to go about this would be to somehow fetch the newest release from pcsx2.net - I even had a shitty little local script that did something like this, but it broke at some point because of some kind of Cloudflare protection (I based it on what the website does itself):

curl -s https://api.pcsx2.net/v1/nightlyReleases | jq -r .data[0].version

If you happen to be in contact with upstream developers maybe something could be worked out to reliably get the newest release number?

This should neither conflict with nor provide pcsx2-git, per guidelines