skin.shortcut is an extension add-on in kodi that let’s users generate custom shorcuts
Since I’m using artic zephyr as my default skin and it had support for custom shortcuts there hasn’t been any issues for me
Strange that it behaves like that.
I just copy the default menu file from /usr/share/… , modify it and then put it into the userfolder in home so not sure why it should break custom shortcuts.
As a quick workaround, you could just delete that file and create the shortcut yourself. Or maybe this is a permission issue not really sure if I copy that file as root…
Sorry, been away from my setup for a longer time so don’t really had time to play in the last weeks. Will have another look.
Edit: Try to delete the file /home/osmc/.kodi/userdata/addon_data/script.skinshortcuts/mainmenu.DATA.xml
Make a backup beforehand of course and restart kodi.
Just a warning:
I ran the script again today and it messed up my osmc installation.
It seems to delete the basefiles package during the binary installation.
Might be at a point now where too much has changed from mainline jessie or raspbian to make this safe to run.
So I will probably put a big warning sign over this while thead now and wait for the osmc team to do something appropriate.
Hope this will not take too long.
It was nice as long as it lasted, but I don’t have the time to work around the rapid changes to osmc anymore.
If anyone wants to continue this, feel free to fork the the project on GITHUB of course 
If I get more time, I will try to make an alternative and safe emulator package. This will be a good amount of time in the future though.
Thank you for your efforts and your support for your thread. I am gonna try a base RetroPie install and add Kodi and Limelight to that… should be same net effect. I hope we see some tested/approved OSMC addons SOON to enable what is clearly a popular idea
Oh dear…
I used this method today on OSMC, and now I can’t use my wireless keyboard with OSMC (Kodi). I can use it whenever I’m in the console (text-based interface you know), but as soon as I start Kodi again (sudo systemctl start mediacenter.service) my keyboard is dead.
I can still use Kodi via my TV’s remote, and my Kodi remote app (I’m using YASU since it works for me), but I would still like to be able to use my keyboard.
Oh, and the shortcut that the script created in Kodi doesn’t work at all. It restarts Kodi, nothing else.
And NOW I read this;
I don’t have time for this…
Is there any way to revert the changes this script did?
Sorry to tell you that, but it would probably be the easiest solution for you to revert to a backup on a new osmc installation (you can probably still make a backup of your user Settings).
You have been warned that this could happen even while installing it, in the first post of this thread and in the readme.
Yeah, I don’t blame anyone but myself, just wondered if there was a solution, or maybe this was a common problem.
And I should say that I started the installation about 5 hours ago, before your last post, but I’ve been so busy that I left it to do other stuff and came back to do the rest a couple of hours ago 
I did realize that your solution might be the only one, but I don’t have time for it today. Thanks for the reply anyway 
should be a easy fix is the wireless keyboard connected via bluetooth then just add some lines in the startup script for retropie.sh and retropie_watchdog.sh
I used this method today on OSMC, and now I can’t use my wireless keyboard with OSMC (Kodi). I can use it whenever I’m in the console (text-based interface you know), but as soon as I start Kodi again (sudo systemctl start mediacenter.service) my keyboard is dead.
Very similar issue here. Ran the script on a clean install (so no harm done really) but when it boots to Kodi the keyboard and mouse are both unresponsive. Keyboard works fine after I SSH into the pi2 and kill kodi manually.
I’ll dink around with it if I get a chance this weekend. I’ve never really had to troubleshoot Kodi before so who knows what’s wrong.
I just read this thread (all of it).
I installed OSMC RC3 about a week ago. It has done a couple of automatic update. I am really pleased with it.
I ran this for educational purposes. I made a backup image before I started.
I ran it as the osmc user via sudo. I did the binary install and I canceled the retropie setup script as instructed. Everything seemed to work really well. Once it as all done, I went to reboot "“sudo shutdown -r now”
This is when I found out things were bad. It said the sudo command was not found. I logged in as root and rebooted. When it came back up, OSMC was broken with a sad face icon.
I restored from my image and tweaked the script a little. I removed part that modified the skin. I removed the part that cleans up unneeded things. I removed the part that changes the SDL. I was going for a really clean install of RetroPie on OSMC.
The results were the same. This latest version of OSMC and the latest version of RetroPie just do not work well together.
I thought everyone should know.
Yeah, thats what I said some posts ago.
It actually is the retropie setup script that uninstalls needed components of the system for some reason.
Haven’t run into those issues at all got both updated and no issues at all, although i haven’t cleaned up unnecessary files since there isn’t an issue to leave em be
@mcobit, thanks for making this script. While I was reading this, I saw you coming in here, supporting everyone that tried it. I cannot imagine coming in here and putting up with people that just hit the reboot option in the retropie script. 
@Toast, do you recall which OSMC you installed? was it RC2? I am thinking that I might be able to install an older version, install RetroPie on it and then let it update (as you have). I am just curious which image I should start from.
think i started out with rc2 but i didnt do the install until i was at rc3
So I found my old quake 3 arena cd, and i was hoping to put the full paks into the baseq3 folder, but i can’t seem to find it in osmc. all the folders people suggest are using straight pi and not osmc. when i try to ftp in to drop the pak files, i can’t find any baseq3 folder, any suggestions as to why this might be? im trying to ssh, and i see Quake\ III\ as folders, but i don’t think i understand enough linux to really do this correctly… help?
I think all the files are in your homefolder RetroPie/roms/ports/quake…
BTW I am working on some new way to get emulators to osmc.
Right now it only works for the retroatch emus and is very experimental. But it shouldn’t interfere with any system stuff.
I try to get the retropie folders and all the needed libs together into a package that can easily be installed and uninstalled by some scripts.
But it will take time till it’s ready.
That is the weird part, that folder is empty…
What about a simple find command to get the location of pak0.pak ?
Like
find -name pak0.pak
Found the files. They are in /opt/retropie/ports/quake3/baseq3/