search

goatcorp / XIVLauncher.Core

Cross-platform version of XIVLauncher, optimized for Steam Deck
GNU General Public License v3.0
84 stars 35 forks source link

Could not find file '~/.xlcore/ffxiv/boot/ffxivlauncher.exe' #136

Closed Furyspark closed 1 month ago

Furyspark commented 1 month ago

Distro Arch Linux Kernel Tried both linux-lts and linux GPU Radeon RX 7900 XTX CPU AMD Ryzen 9 7900X

I could log in just fine last night (with xivlauncher-rb, although this issue seems to be with both versions of the launcher), but as of today, I'm missing files, apparently.

I'm going to hazard a guess and say Squenix is removing 32 bit binaries, since ffxivlauncher64.exe does exist.

Unfortunately, symlinking ffxivlauncher64.exe to ffxivlauncher.exe did not work. Or rather, it works in that it then shows it's missing ffxivupdater.exe. But after symlinking ffxivupdater64.exe to ffxivupdater.exe, it's showing a new error: 'Boot conflict, need reinstall'.

I then tried renaming the .xlcore base directory to .xlcore.bak, so I can try installing it anew. Unfortunately, after a minor update, it shows the exact same error: 'Could not find file /home/username/.xlcore/ffxiv/boot/ffxivlauncher.exe`.

lupenq commented 1 month ago

same on steam deck

Mox-Human commented 1 month ago

Distro: Nobara Linux 39 (GNOME) Kernel: 6.7.6-201.fsync.fc39.x86 GPU: NVIDIA GeForce RTX 2080 SUPER CPU: AMD Ryzen 5 3600

Same issue here, Have tried deleting all game files, deleting all versions of FFXIV loader, and reinstalling. Tried on V1.0.8-Fedora and V1.0.7-RPM and V1.0.6 Flatpack with a clean install each time.

Have tried steps as above, copying FFXIVLAUNCHER64 and renaming the copy to FFXIVLAUNCHER leads to needing updater, which leads to Boot conflict, need reinstall.

Blooym commented 1 month ago

Issue has already been resolved in XIVLauncher 1.0.8. For now most users just need to wait until a package update is available from wherever you installed the launcher to play again.

DiamondDust132 commented 1 month ago

Yeah, that's what I figured. Thanks for the reply (and saving me the time of writing up a probably useless reply lol) Great to know this has already been fixed.

lupenq commented 1 month ago

Issue has already been resolved in XIVLauncher 1.0.8. For now most users just need to wait until a package update is available from wherever you installed the launcher to play again.

And how do you update on Steam Deck? Discovery has the latest version 1.0.6, so it's not even 1.0.7 yet

and do you have ETA for flathub?

Furyspark commented 1 month ago

Ah, cheers. The xivlauncher-git package from the AUR seems to work just fine, indeed.

For anyone on an Arch-derivative like SteamOS, you can probably just do the same thing. Enable the AUR in your package manager configuration (if it isn't already) and download xivlauncher-git. The package label still looks like an outdated version, but -git packages are just going to be the latest version of the software it's installing, with the label having to be manually updated (afaik), so don't worry about that.

Everyone else might just have to wait or manually compile the launcher.

And if you're on Arch at this time of writing, be aware of an issue with pacman which can be detrimental. @rankynbass mentioned this on one of the AUR packages, but there's a way around it:

There's a bug in pacman right now, which is causing the binary to be stripped even with the !strip option. You can fix it by changing the PKGBUILD options. options=('!strip') should be options=('!strip' '!debug')

Mox-Human commented 1 month ago

Confirmed, Manually updating my version to 1.0.8 and patching SSL to it has fixed this issue.

Osysix commented 1 month ago

Confirmed, Manually updating my version to 1.0.8 and patching SSL to it has fixed this issue.

Could you walk me through this? I installed XIVlauncher via the Discover store on Steam Deck.

Mox-Human commented 1 month ago

Confirmed, Manually updating my version to 1.0.8 and patching SSL to it has fixed this issue.

Could you walk me through this? I installed XIVlauncher via the Discover store on Steam Deck.

Im not sure how the steam deck handles files / flatpacks etc so I cant give you specifics, my apologies.

I just grabbed the files directly from the release page and copied them into my XIVLauncher folder in /opt/ , and then applied the SSL patch from https://github.com/goatcorp/XIVLauncher.Core/issues/104 to fix my OPENSSL issue (which im not sure if the steamdeck has)

NotNite commented 1 month ago

I can't believe every time XLCore goes down for a few hours people patch their launchers manually by replacing files. Do not do this. Be patient and wait for a proper update from your application storefront. To quote @reiichi001 from Patch 6.5:

I want to be super clear as a project administrator about something.

please for love of all that is good do not go around trying to patchwork files into the flatpak. Seriously.

I've seen that mentioned in the discord server chat and on github and I'm absolutely horrified.

Osysix commented 1 month ago

I can't believe every time XLCore goes down for a few hours people patch their launchers manually by replacing files. Do not do this. Be patient and wait for a proper update from your application storefront. To quote @reiichi001 from Patch 6.5:

I want to be super clear as a project administrator about something. please for love of all that is good do not go around trying to patchwork files into the flatpak. Seriously. I've seen that mentioned in the discord server chat and on github and I'm absolutely horrified.

Thank you for the warning. I'll wait.

Mox-Human commented 1 month ago

I can't believe every time XLCore goes down for a few hours people patch their launchers manually by replacing files. Do not do this. Be patient and wait for a proper update from your application storefront. To quote @reiichi001 from Patch 6.5:

I want to be super clear as a project administrator about something. please for love of all that is good do not go around trying to patchwork files into the flatpak. Seriously. I've seen that mentioned in the discord server chat and on github and I'm absolutely horrified.

Apologies here, I patched the launcher manually as the flatpack has not been updated for 6 months I assumed it was no longer maintained. (I only installed FFIX for the first time this morning)

Happy to hear it is still being actively maintained! I will wait for the official patch to land :)

tommadness commented 1 month ago

The flatpak was on 1.0.7, there was a display error showing 1.0.6 but it was indeed on 1.0.7

NotNite commented 1 month ago

It's still maintained, Flatpak just takes a bit of effort to get releases out and there hasn't been a reason to update it in a while. Hang tight - most people who can get Flatpak updated are busy right now (reminder that it's morning in the US and working hours in the EU).

reiichi001 commented 1 month ago

Thanks @NotNite.

For everyone else, please for the love of all that is good, give the package maintainers some time to wake up, get off work, and/or otherwise be available.

It takes hours for flathub to process an update. You'll see it in your flatpak package manager (the discover store for Steam Deck users) and all community packages need to be updated by their maintainers. (They'll work on it when they can. They've been notified. I like helping, but I'm not waking up at 5am for anyone here.)

Your patience is appreciated.

Houndie commented 1 month ago

For those of us on Nixos, you can watch the update progress here: https://github.com/NixOS/nixpkgs/pull/297179

Thanks XL maintainers for having this fixed and ready to go!