OpenSUSE Tumbleweed nothing loads and the text "TypeError: Load Failed" is displayed

[Kizaing]

When loading up the launcher AppImage everything fails to load, and this is the error I am seeing:

I tried launching via the console to see if there was any other errors but this is all that is displayed:

/usr/bin/AppImageLauncher: /lib64/libcurl.so.4: no version information available (required by /usr/bin/../lib/x86_64-linux-gnu/appimagelauncher/libappimageupdate.so)
[2024-01-21][21:35:39][DEBUG][reqwest::connect] starting new connection: https://releases.yarg.in/

** (yarc-launcher:31232): WARNING **: 16:36:04.420: atk-bridge: get_device_events_reply: unknown signature

Hopefully it can be fixed! Thanks

[EliteAsian123]

Hi, thanks for the report!

Can you send the log files? They should be in $HOME/.config/in.yarg.launcher/logs on Linux, iirc. Thanks!

[Kizaing]

Thanks for the response! This is the content of the log file:

[2024-01-19][21:39:33][DEBUG][reqwest::connect] starting new connection: https://releases.yarg.in/
[2024-01-19][21:39:35][DEBUG][reqwest::connect] starting new connection: https://github.com/
[2024-01-19][21:39:36][DEBUG][reqwest::async_impl::client] redirecting 'https://github.com/YARC-Official/YARC-Launcher/releases/download/v0.3.1/yarc-launcher_0.3.1_amd64.AppImage.tar.gz' to 'https://objects.githubusercontent.com/github-production-release-asset-2e65be/646274645/50341a07-b866-49fa-830a-be7951b294d9?X-Amz-Algorithm=AWS4-HMAC-SHA256&X-Amz-Credential=AKIAVCODYLSA53PQK4ZA%2F20240119%2Fus-east-1%2Fs3%2Faws4_request&X-Amz-Date=20240119T213936Z&X-Amz-Expires=300&X-Amz-Signature=6f69765847f142adaf3652ac1c01419b6a557487650fe14d9f90edb4738c8ff5&X-Amz-SignedHeaders=host&actor_id=0&key_id=0&repo_id=646274645&response-content-disposition=attachment%3B%20filename%3Dyarc-launcher_0.3.1_amd64.AppImage.tar.gz&response-content-type=application%2Foctet-stream'
[2024-01-19][21:39:36][DEBUG][reqwest::connect] starting new connection: https://objects.githubusercontent.com/
[2024-01-19][21:39:47][DEBUG][reqwest::connect] starting new connection: https://releases.yarg.in/
[2024-01-19][21:41:10][DEBUG][reqwest::connect] starting new connection: https://releases.yarg.in/
[2024-01-19][21:42:57][DEBUG][reqwest::connect] starting new connection: https://releases.yarg.in/
[2024-01-20][00:04:08][DEBUG][reqwest::connect] starting new connection: https://releases.yarg.in/
[2024-01-20][00:10:16][DEBUG][reqwest::connect] starting new connection: https://releases.yarg.in/
[2024-01-21][04:47:27][DEBUG][reqwest::connect] starting new connection: https://releases.yarg.in/
[2024-01-21][21:30:55][DEBUG][reqwest::connect] starting new connection: https://releases.yarg.in/
[2024-01-21][21:34:50][DEBUG][reqwest::connect] starting new connection: https://releases.yarg.in/
[2024-01-21][21:35:39][DEBUG][reqwest::connect] starting new connection: https://releases.yarg.in/

[EliteAsian123]

Hmm, weird. To me, it looks like the launcher is unable to connect to GitHub, or out releases CDN for whatever reason. I'm not sure what could be causing this; is there some sort of firewall or something blocking this network activity?

[Kizaing]

Very strange... I checked my firewall and there shouldn't be anything blocking it. From my terminal i can curl https://releases.yarg.in/index.json without issue

[EliteAsian123]

/usr/bin/AppImageLauncher: /lib64/libcurl.so.4: no version information available

Potentially something to do with this, then? Sorry, I'm not too knowledgeable about Linux.

[Kizaing]

I was curious about that, I have that file on my host system but I'm not too sure about how AppImages are packaged. I will attempt to compile it from source and run it to see if the same issue occurs and report back

[Kizaing]

Update: Compiling from source and launching it works as intended, for some reason the AppImage (specifically in OpenSUSE Tumbleweed) can't connect

[EliteAsian123]

Very strange. Thanks for doing all of that!

[Kizaing]

No problem! Personally it's only like, mildly inconvenient to run this way haha, but hopefully it's something that can get fixed in a later update for others if they run into this issue

Edit: Looks like building my own AppImage using npm run build works? But the one downloaded from the release page does not, very strange

[EliteAsian123]

Edit: Looks like building my own AppImage using npm run build works? But the one downloaded from the release page does not, very strange

That is very strange. I wonder if this was fixed too as of recently in Tauri? I'll let you know whenever there's a new build and you can test it then.

[krminix]

Hello, I am experiencing the same issue as @Kizaing. I used yarc-launcher_0.3.1_amd64.AppImage on my fresh install of Tumbleweed and nothing loads. I haven't built from source yet. I'll report back if I make any progress on this. Here is my log file.

YARC Launcher.log

[junetried]

Same issue here on snapshot 20240425. Also broken on Leap 15.5.

[sheltpat]

Same issue here on Tumbleweed (up-to-date), on precompiled YARC 0.3.2.

An error has occurred: TypeError: Load failed

One line in log: [2024-07-03][17:04:08][DEBUG][reqwest::connect] starting new connection: https://releases.yarg.in/

Can ping yarg.in from the console, though.

Is it possible to download a (portable I guess?) version of YARG via the Browser or another device and paste it manually in the (which?) appropriate directory for the time being?

-

Edit: Running the AppImage from console provides an additional error (note: the 22... is the time stamp. 10ms off a glorious one.): ** (yarc-launcher:3728): WARNING **: 22:22:22.212: atk-bridge: get_device_events_reply: unknown signature

Sudo'ing it: (yarc-launcher:3536): Gtk-WARNING **: 22:17:21.401: cannot open display: No additional text after the ":".

I don't know what to make of this, but maybe someone else does.

To reiterate, the last two messages are taken from the live console output, not from the log file.

Additional info: Right-clicking on either YARG button on the sidebar opens the context menu. When clicking on "Open Link", the window briefly flashes the "Fun Fact YARG stands for..." loading screen and ends with the topical error message.

If there's anything I can try or simply click on, let me know. FWIW every screen/menu of the launcher ends with the error. The error message even appears left to the big Discord banner on the initial home screen (which is empty besides that).

[EliteAsian123]

Hello, thank you for all y'all's patience. Unfortunately, none of us developers use Linux so diagnosing these problems is quite difficult.

Recently in our Discord, we've had a development regarding this issue. This appears to be a problem with maybe missing dependency, which for whatever reason isn't packaged within the AppImage. As Kizaing did above, building the launcher from the source does work, however, a Discord user discovered that after building the launcher and downloading all of the dependencies to do so, the original AppImage works... sometimes (as opposed to never before building). The manually built version of the launcher does work all of the time though.

Again, I have close to zero experience with Linux, so if anyone has any ideas of why this could be, please let me know. As a temporary solution, however (as others did above), it does work properly when building from source. I'm quite certain however that the problem is a missing dependency within the AppImage, I just don't know what it could be.

Thanks, and sorry.

[EliteAsian123]

Hello,

Recently we released v1.0.0 of the launcher. Can anyone here test it out and see if it works on there?

Thanks!

[sheltpat]

@EliteAsian123

Starting the AppImage on a fresh OpenSuse Tumbleweed installation, this shows up on 1.0 after a brief loading bar with the fun fact. Still just the "starting new connection" in the log file.

When I try building it (I'm a noob mind you), after npm install and npm run dev it always fails because a lot of missing dependencies.

I tried finding each package that was required by npm'ing over and over again and installing each one over YaST Software Management, but I gave up since figuring each one out took really long, so sorry for that.

-

Maybe the dependencies are on the devs' team distro but not on OpenSuse? Maybe the "package.json" is incomplete? Might that explain why npm always fails building and asking for dependencies?

@Kizaing How did you go about building it from source? I followed the README.md, but npm always asks for another package that is required, like: Compiling [PackageNameX] error: failed to run custom build command for [PackageNameY] Sorry to ask, I rarely build and don't even remember when I built last.

[Kizaing]

@sheltpat Sadly I don't remember the exact libraries I had to install, but I used the OBS to install them vs YaST (that would take forever as you've seen haha)

I just pulled the latest code and successfully compiled the 1.0 appimage and its working for me

I uploaded it here in case anyone wants to test it or see what the difference between the official appimage might be

[sheltpat]

Disclaimer: I'm neither a dev nor particularly knowledgeable, so the assumptions below may only be (slightly educated) guesses. _

@Kizaing Thanks for the tip with OBS, I need to figure that out. So far I'm completely lost and only managed to clone their AppImage template and possibly import the launcher source in a second package/project. I'm not sure if I just needed a spec file at the point I was, but I'll figure it out eventually.

Edit: Actually, could you share your spec file for OBS or point me in a direction of how I would figure out which dependencies I'd have to include? Maybe even create another issue or pull request for it for this project, if that is how it works. Or listing your dependencies, so that the dev team could compare it or something.

Edit2: It's possibly just a noob (me) jumping to possible conclusions, but the dependencies prompted missing when npm run dev'ing seem to be not included in package.json. Maybe the devs are on Debian/Ubuntu and these are already included, and OpenSUSE comes without these. So possible need to list more/additional SUSE-base dependencies in package.json? _

Anyway, I took your AppImage and the official one, renamed them to *.7z and had a brief look at their content. The folder structure differs for example, the x64 libs are in usr/lib64, while in the official one the libs are in usr/lib/x86_64-linux-gnu. It's the biggest difference I could see, I'm not knowledgeable enough to comment on minor differences like file sizes or versions. _

So, maybe an issue in the building pipeline? Different prerequisites in the folder structure between distros (Ubuntu/Debian vs SUSE)?

[junetried]

Anyway, I took your AppImage and the official one, renamed them to *.7z and had a brief look at their content. The folder structure differs for example, the x64 libs are in usr/lib64, while in the official one the libs are in usr/lib/x86_64-linux-gnu. It's the biggest difference I could see, I'm not knowledgeable enough to comment on minor differences like file sizes or versions. _

So, maybe an issue in the building pipeline? Different prerequisites in the folder structure between distros (Ubuntu/Debian vs SUSE)?

This is normal and almost certainly is not a problem. AppImages set up their own environment - this is what makes them distro-agnostic (ish), so it doesn't matter what the structure actually looks like.

[sheltpat]

so it doesn't matter what the structure actually looks like.

Gotcha, already thought as much. It confused me, since Kizaing's has usr/lib and usr/lib64 (and was built on/for OpenSUSE), while the official one has the x64 stuff inside in usr/lib/x86_64-linux-gnu. But I guess the respective AppImage points to the right place, if you say they're somewhat agnostic.

Also, File Roller would extract the official one without a problem, while the unofficial one errors about "a command exit[ing] abnormally" for whatever reason. So I only did a brief visual structure comparison instead comparing actual libs (or seeing if they're even there).

Edit: Oh, I forgot to mention the AppImage Kizaing linked above works for me as well, despite not being correctly extractable by File Roller. I don't know if the contents could just be replaced (or added) for testing. It may be, by extracting it and repacking it with appimagetool. But that's probably something to try for someone who actually knows what they're doing. That's all I can do know for now as an amateur.