HGL
metropolitan-bronze
Sims 4 unable to start due to bwrap error
13 Replies
metropolitan-bronzeOP•7mo ago
[cli] INFO: Logging in...
[Core] INFO: Trying to re-use existing login session...
[1mumu-launcher version 1.1.3 (3.13.0 (main, Oct 8 2024, 00:00:00) [GCC 14.2.1 20240912 (Red Hat 14.2.1-3)])[0m
[33mWARNING: [1mExecutable not found: start[0m
[1msteamrt is up to date[0m
pressure-vessel-wrap[1961170]: W: Unable to share "/usr/lib64/heroic-games-launcher-bin/resources/app.asar.unpacked/build/bin/x64/linux" with container: Path "/usr" is reserved by the container framework
bwrap: Can't chdir to /usr/lib64/heroic-games-launcher-bin/resources/app.asar.unpacked/build/bin/x64/linux: No such file or directory
helpful-purple•7mo ago
how did you install heroic? looks like some files are missing
metropolitan-bronzeOP•7mo ago
I replaced the AppImage with the copr repository which was referenced in the README:
https://github.com/Heroic-Games-Launcher/HeroicGamesLauncher?tab=readme-ov-file#fedora
GitHub
GitHub - Heroic-Games-Launcher/HeroicGamesLauncher: A games launche...
A games launcher for GOG, Amazon and Epic Games for Linux, Windows and macOS. - Heroic-Games-Launcher/HeroicGamesLauncher
metropolitan-bronzeOP•7mo ago
Btw, I'm seeing a similar error when launching Starwars Battlefront 2.
Is this an easy fix or should I just switch back to the AppImage?
Oddly enough it looks like the folder does exist.
Could this be caused by a permissions issue? ls -lR /usr/lib64/heroic-games-launcher-bin/resources/app.asar.unpacked/build/bin/x64 /usr/lib64/heroic-games-launcher-bin/resources/app.asar.unpacked/build/bin/x64: total 0 drwxr-xr-x. 1 root root 72 Nov 20 09:09 linux drwxr-xr-x. 1 root root 46 Nov 20 09:09 win32 /usr/lib64/heroic-games-launcher-bin/resources/app.asar.unpacked/build/bin/x64/linux: total 37304 -rwxr-xr-x. 1 root root 11812824 Sep 20 20:00 comet -rwxr-xr-x. 1 root root 7328696 Sep 20 20:00 gogdl -rwxr-xr-x. 1 root root 8078856 Sep 20 20:00 legendary -rwxr-xr-x. 1 root root 10236536 Sep 20 20:00 nile -rwxr-xr-x. 1 root root 731336 Sep 20 20:00 vulkan-helper /usr/lib64/heroic-games-launcher-bin/resources/app.asar.unpacked/build/bin/x64/win32: total 60 -rw-r--r--. 1 root root 61204 Sep 20 08:41 GalaxyCommunication.exe
Could this be caused by a permissions issue? ls -lR /usr/lib64/heroic-games-launcher-bin/resources/app.asar.unpacked/build/bin/x64 /usr/lib64/heroic-games-launcher-bin/resources/app.asar.unpacked/build/bin/x64: total 0 drwxr-xr-x. 1 root root 72 Nov 20 09:09 linux drwxr-xr-x. 1 root root 46 Nov 20 09:09 win32 /usr/lib64/heroic-games-launcher-bin/resources/app.asar.unpacked/build/bin/x64/linux: total 37304 -rwxr-xr-x. 1 root root 11812824 Sep 20 20:00 comet -rwxr-xr-x. 1 root root 7328696 Sep 20 20:00 gogdl -rwxr-xr-x. 1 root root 8078856 Sep 20 20:00 legendary -rwxr-xr-x. 1 root root 10236536 Sep 20 20:00 nile -rwxr-xr-x. 1 root root 731336 Sep 20 20:00 vulkan-helper /usr/lib64/heroic-games-launcher-bin/resources/app.asar.unpacked/build/bin/x64/win32: total 60 -rw-r--r--. 1 root root 61204 Sep 20 08:41 GalaxyCommunication.exe
helpful-purple•7mo ago
yes, it can be a permissions issue, if the app can't access that folder it will think it doesn't exist
metropolitan-bronzeOP•7mo ago
I just tried running
sudo chmod -R john:john /usr/lib64/heroic-games-launcher-bin
but that didn't seem to work.
so i restarted heroic via command line and this is the output I"m seeing when I attempt to launch the game
metropolitan-bronzeOP•7mo ago
metropolitan-bronzeOP•7mo ago
oh i guess this is only a warning
alright. let me try removing that directory all together then reinstalling the package
it recreated the directory but I'm still seeing the same error
helpful-purple•7mo ago
honestly, if it was working with the app image and you had no issues before you can just use that one
I'm not a fedora user so I don't know if there's anything important needed there
metropolitan-bronzeOP•7mo ago
yea looks like i have to reinstalll them again but it's at least working again with appimage
idk i guess that i would have just rathered to have this all managed by a package manager
helpful-purple•7mo ago
not sure how it works on fedora, but at least on mint when I use the flatpak version of heroic it shows up in the package manager so it gets updated with the rest of the system
maybe you can try flatpak instead of appimage
metropolitan-bronzeOP•7mo ago
yea initially i was going to give the flatpak a shot but I wasn't sure which configuration files would need to be copied over. Both the AppImage and COPR installations seem to share the same paths so it was just convenient
you wouldn't happen to know which files I'd need to copy over in order to avoid reimporting everything
Actually I'm just going to file a bug report. I just confirmed that the RPM also seems to work as expected so I'll use that one for now.
rising-crimson•4mo ago
Today I got the same issue in #A Way Out on Epic (EA) not starting/installing. Did you manage to fix this somehow or do you know something new?