FitGirl games installation stuck at around 0.0% (Linux)

I've tried to install the following games:

The Last of us Part I
One More Night

but for both, the game installation stuck at around 0.0%, so I think this is not a problem with games per se but maybe with my pc/wine configuration. The fun fact is that, a week ago, I was able to install Clair Obscure Expedition 33 without issue. Can anyone help me?

This is my pc configuration:

ChachyOS with zen-kernel
CPU: Ryzen 5 2600X
GPU: RX 7800 XT
16 GB of RAM at 2133 MHz
1 TB nvme SSD

I tried the following fixes:

verify BIN files before installation
use the Russian language for the installer
deleted any special character in the folder name of the executable and put such folder in a subfolder of the C drive
install the game in a subfolder of the C drive
limit installer to 2 GB of RAM usage
every wine tricks in the FitGirl troubleshooting page
use brand-new wine prefix

UPDATE: I resolved this issue launching the setup through Lutris (here's a tutorial)

21 comments

You can try running it with proton-ge, instead of pure wine. Use Lutris to make things easier
- Yep! Wine does NOT work with larger Fitgirl Repacks (>1 GB).
  Lutris with Proton-GE works flawlessly though. Never had any issue.
  
  How is the process now? Last time I tried, a few years ago, the whole thing was so confusing to me that it was much easier to get a second ssd and dual boot windows. Now I'm planning to ditch windows completely but I haven't looked into it yet.
  I remember there was a add game button then add the installer but once the installer finished I didn't know where the game went. I only remember installing successfully the witcher 3 not being sure how.
FitGirl often repacks Dodi's repacks to make them smaller. I've heard people having trouble with FitGirl's repacks often succeed with Dodi's instead. Maybe try that if it's possible.
- This was the case for me with RDR2
I find it very funny that it says 0.2% in the picture and you describe it as "around 0.0%" in the headline. Don't know, makes me chuckle.
https://fitgirl-repacks.site/repacks-troubleshooting/
- Thanks, but I already tried them.
you have encountered the same bug as me (https://lemmings.world/post/28452192) the problem is that arch (or cachyos) now defaults to using wine-wow64 builds (no 32 bit libraries required) and that has something to do with it. I have not beeen able to fix it, and do not know where to report (wine team will not consider bugs concerning pirated installers)
On the bright side, you can listen to that zen music for eternity.
unarc.dll and ISDone.dll are common culprits with Fitgirl on Linux I think in an unresolved YMMV situation.
Try DODI instead.
- Have had way more luck with DODI so seconded.
I'd highly recommend using Dodi instead. I dont know what causes it, but FitGirls installers have been doing this for years. There are some steps that can fix it, but its very inconsistent. Meanwhile, I havent had a Dodo install fail.
If you'd really prefer FitGirls repacks you can run the installer in a Windows VM and move the files to the host.
I can’t say this is your problem, but when I’ve had similar issues with the install getting stuck, it was a corrupted file and redownloading solved it.
For Linux, this is kind of a stupid workaround but I've had success, add the installer as a non-steam game and run it through proton by switching to it in the "game's" compatibility. Running it through wine has been hit or miss for me, it'll crash or freeze up, but proton has worked pretty well so far.
Then after unpacking, install the game's .exe as a non-steam game and run that through proton, deleting the first installer from your library
i never get those working either. i use virtualbox w10, unpack there, and then move the folder back to linux
What's the process's CPU usage? Can you run it with strace?
Fit girl has issues with Linux, stuff like DODI and RUNE which are direct downloads usually just work
Ran into this issue recently. Saw a random post on the other site about it being a wine bug. That led me down the path of trying older versions of wine and that solved the problem.
Grab the last version of wine 9 from https://github.com/Kron4ek/Wine-Builds and run the installer from the directory where wine 9 was unpacked.
./wine /path/to/game/installer
Hopefully it'll get fixed soon in wine 10 but given the nature of the bug, that could take a while.

21 comments