-
Notifications
You must be signed in to change notification settings - Fork 25
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Doesn't work on RetroArch Flatpak #15
Comments
Is Dolphin installed? Probably need to change the command to run a flatpak run command with Surprised you even got the core running with Flatpak! Nicely done 👍 |
Wow! Thanks for the fast response! =) I'm digging into source code right now. I'm doing a lot of changes on system(command) to try to figure out what is happening. I'm not a developer by the way, and I messed my GCM rom file from Resident Evil 1 testing if Flatpak can access the userspace (I think that somehow it sandboxes the RetroArch and it cannot access /usr from the system itself), but I discovered (from the hard way) that it can access my ROM file. The command that I issued was: echo oi > /home/eduardo/ResidentEvil1Disc1.gcm And it successfuly overwrite my rom file. I'll have to rip it again! XD I'll make some tests with Dolphin from flatpak instead of the one from the repo of my Linux distribution. |
Having troubles running one Flatpak application from another. |
When I try to run a GameCube game on RetroArch using libretro-dolphin-launcher, it shows the following message:
sh: dolphin-emu-nogui: command not found
sh: dolphin-emu: command not found
...
dolphin-emu-nogui not found, trying dolphin-emu
The command "dolphin-emu" works on my machine. I believe it is somehow related to Flatpak (I installed RetroArch flatpak).
I know that by now we have an official Dolphin libretro implementation, but it's still in Alpha stage and, on my machine, is too slow. Dolphin Emulator standalone works perfect.
If I can provide some more help to troubleshooting the problem, I'm here for it.
The text was updated successfully, but these errors were encountered: