-
Notifications
You must be signed in to change notification settings - Fork 32
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
Launcher not working but emulationstation does #62
Comments
same issue here. Executing 'emulationstation' in the terminal and executing "RetroPie/scripts/retropie.sh" is working just fine. Only the addon-launcher seems to be broken because it only restarts kodi. |
Ultimately I gave up and used PINN to dual boot Kodi and RetroPie. It
installs a tool to switch between the two OS’s so its a cleaner solution
for keeping each side updated IMO. Follow this guide -
https://www.matthuisman.nz/2017/03/retropie-kodi-dual-boot.html
On 17 April 2019 at 19:32:36, Felix ([email protected]) wrote:
same issue here. Executing 'emulationstation' in the terminal and executing
"RetroPie/scripts/retropie.sh" is working just fine. Only the
addon-launcher seems to be broken because it only restarts kodi.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<#62 (comment)>, or mute
the thread
<https://github.com/notifications/unsubscribe-auth/ALOP6Q2JPCW5NHBTF6PWUZTPQ5UMJANCNFSM4G2N4K7A>
.
|
the fix for this is to add "cd /home/osmc" to retropie.sh.. found here: https://discourse.osmc.tv/t/howto-retropie-and-osmc-retrosmc-retrogaming-on-osmc/6671/1454 |
Indeed, this is enough to have it working. Will #61 be integrated? |
I've tried both the System.Exec custom action, and the Launcher addon for my OSMC install, but neither works.
When I SSH in however, I can get emulationstation to run by executing 'emulationstation' from the command line, so we can see the install worked correctly.
When I try to run ./retropie.sh I get 'permission denied' and even after trying chmod -x the message persists.
The text was updated successfully, but these errors were encountered: