probonopd
commented
4 months ago You don't neet /etc insnide the AppDir. We are not using sandboxing.
Is ffmpeg deployed using go-appimage?
Closed Samueru-sama closed 1 month ago
probonopd
commented
4 months ago You don't neet /etc insnide the AppDir. We are not using sandboxing.
Is ffmpeg deployed using go-appimage?
Samueru-sama
commented
4 months ago You don't neet /etc insnide the AppDir. We are not using sandboxing.
The etc directory gets created by go-appimage when deploy everything gets used, it contains a fonts dir inside.
Given that there was an etc directory I thought that the issue was a lack of a resolv.conf file but it wasn't that anyway.
Is ffmpeg deployed using go-appimage?
If I'm not mistaken ffmpeg is statically linked inside the mpv binary. Local videos do play in both without issues.
Also for some reason the mpv binary inside the appimage deployed with go-appimage is much bigger than the mpv binary inside the linuxdeploy made appimage 🤔
I think I need to test without deploying everything with go-appimage to see if the internet errors are still there.
Samueru-sama
commented
4 months ago Alright the issue only happens when the bundle everything mode is used, it doesn't happen when not everything is deployed with go-appimage.
https://github.com/Samueru-sama/mpv-AppImage/releases/tag/continuous
The one with deployall in the title has the connection errors, while the one titled go-appimage doesn't use the deploy everything mode and doesn't have the issue.
And the third one is just the one made with the old method using linuxdeploy which I will remove for the go-appimage method once I finish testing it.
It's a shame I get those connection errors when deploy everything is used, as that appimage works everywhere including on alpine linux.
probonopd
commented
4 months ago You'd now need to find out what is going on (what fails) using tools like strace...
Samueru-sama
commented
1 month ago Alright the issue has been "fixed" or better said I don't know if there was an issue even, turns out that all that needed to be done was build mpv on ubuntu 24.04, so here is what happens:
Building on 20.04 causes yt-dlp to break on all systems. However we discovered that if the ld-linux.so is copied again into the lib64 dir (that is skip the patches that go-appimage makes to ld-linux the issue goes away for all glibc systems, but it still breaks on musl).
Building on 22.04 and skipping the ld-linux.so patches also works and this time it also works on musl systems, but I get a bunch of vulkan errors in alpine linux when testing yt-dlp, it still works but there are those errors.
Building on 24.04 fixes all the issues for glibc and musl and yt-dlp works without issues and there is no need to avoid the ld-linux.so patches.
I also tested building on alpine linux and it that case it also breaks yt-dlp, I have no idea why it only works when built on ubuntu 24.04.
Hello, I have this appimage of mpv that I'm trying to migrate to using
go-appimagefor deploy: https://github.com/Samueru-sama/mpv-AppImage/releases/tag/continuousIt uses the static build scripts of mpv and that's why it is that small.
The 16 MiB appimage is made using
linuxdeployand as far as all the tests I've done, it works perfectly, including playing youtube videos providedyt-dlpis installed on the system.The bigger appimage that contains
anylinuxin its title was made using theappimagetoolfromgo-appimagewith the deploy everything mode. Local videos play but I cannot get it to play youtube videos.At first running the deploy everything appimage with a youtube link causes it to give python errors, which are caused because python isn't bundled in the appimage.
Unsetting the
$PYTHONHOMEvariable inside theAppRungets rid of the python errors, however now I get a different error that seems to be a lack of internet connection?I tried copying my
/etc/resolv.confto the AppDiretc/resolv.confand it didn't work, same error. So now I'm stuck, I have a feeling that I'm missing something very simple lol.