Package Details: open-goal-launcher-bin 2.10.4-3

Git Clone URL: https://aur.archlinux.org/open-goal-launcher-bin.git (read-only, click to copy)
Package Base: open-goal-launcher-bin
Description: A launcher for the OpenGOAL Project to simplify usage and installation
Upstream URL: https://github.com/open-goal/launcher
Licenses: ISC
Conflicts: open-goal-launcher
Submitter: WasabiThumbs
Maintainer: altermetax (WasabiThumbs)
Last Packager: WasabiThumbs
Votes: 1
Popularity: 0.000000
First Submitted: 2023-10-26 16:19 (UTC)
Last Updated: 2026-06-23 23:02 (UTC)

Latest Comments

1 2 Next › Last »

altermetax commented on 2026-07-05 11:57 (UTC) (edited on 2026-07-05 11:59 (UTC) by altermetax)

@WasabiThumbs Now that I've got some free time, I've tested this in several different ways and I can't reproduce your findings. The only two sonames that are needed by libraries in the appimage and are not present in the appimage are libpulsecommon and libpxbackend.

$ cd src/squashfs-root

$ find . -name '*.so*' -type f -print0 | \
    xargs -0 -I{} readelf -d {} | \
    awk -F'[][]' '/NEEDED/{print $2}' | sort -u > /tmp/needed.txt

$ wc -l /tmp/needed.txt
209 /tmp/all_needed.txt

$ ls shared/lib | sort -u > /tmp/have.txt

$ comm -23 /tmp/needed.txt /tmp/have.txt
libpulsecommon-16.1.so
libpxbackend-1.0.so

Please share your code that finds those dependencies.

WasabiThumbs commented on 2026-06-23 23:00 (UTC)

@jdigi78 Unfortunately as I'm no longer facing the issue I can't give upstream a reproducible example, however you can easily verify the discrepancy using the method I mentioned. As long as the discrepancy exists, it's not invalid for the PKGBUILD to require these dependencies.

WasabiThumbs commented on 2026-06-23 22:59 (UTC) (edited on 2026-06-23 22:59 (UTC) by WasabiThumbs)

@its87 You're right, not sure how I missed that. Fixing now

its87 commented on 2026-06-23 20:39 (UTC)

I have had an issue installing this package using yay regarding the dependency of nghttp3: nghttp3-git-r1324.f4c3c8d-1 and libnghttp3-1.16.0-1 are in conflict. Remove libnghttp3? [y/N]

On my system, I have already installed libnghttp3 which is the official name on Arch for that library.

When the installation is triggered, it tries to resolve the name nghttp3in the official repositories, since it does not exist with that exact name, yay resolves it via AUR and selects nghttp3-git but then, the system warns you about the content of that package replaces the existing one which is the official. If I install the package manually withmakepkg -si` this issue does not exist.

I know that this is not directly related to the package itself, but maybe you can take a look at this to improve compatibility.

jdigi78 commented on 2026-06-22 22:20 (UTC)

@WasabiThumbs That is quite a few missing dependencies for an AppImage. What issue were you having? It would be wise to create an issue upstream and see what they have to say about it.

WasabiThumbs commented on 2026-06-22 22:13 (UTC) (edited on 2026-06-22 22:22 (UTC) by WasabiThumbs)

@altermetax If you extract the AppImage and run ldd on the ELFs inside, you'll find that they link libraries which aren't included in the AppImage. Maybe intentional, maybe an upstream issue. The newly added dependencies provide those libraries and adding them to the PKGBUILD fixed a real issue for me. These packages are evidently fairly ubiquitous. Indeed the fact that they aren't unconditionally loaded by the application is suboptimal, but impact should be minimal. open-goal-launcher shouldn't require any changes since the depends already pull these libraries in as transitive dependencies, which is a more direct and clean way about it. I can share the code I used to generate the list you see in the PKGBUILD if you want.

altermetax commented on 2026-06-22 14:10 (UTC)

@WasabiThumbs your latest change added a bunch of dependencies, but I looked at this and none of them seem to really be needed, and even if they were, this package is installed as a raw appimage, so they would be bundled inside it.

Where do those dependencies come from?

jimsey-pickles commented on 2024-09-26 02:11 (UTC)

Any chance for an update?

WasabiThumbs commented on 2024-05-19 20:45 (UTC)

@K4LCIFER It may be necessary to reboot if installing this package caused you to install FUSE for the first time, otherwise try open-goal-launcher-bin --appimage-extract-and-run

K4LCIFER commented on 2024-04-20 23:14 (UTC)

When trying to launch it I get the following error:

Cannot Mount AppImage, please check your  FUSE setup.
You might still be able to extract the contents of this AppImage 
if you run it with the --appimage-extract option. 
See https://github.com/AppImage/AppImageKit/wiki/FUSE 
for more information

1 2 Next › Last »