Unfortunately this only worked for the older of my systems which is still running Kodi 18!
The system I allowed to upgrade from Kodi 18 to Kodi 19 a couple of days ago refuses to enable the main menu configuration!
It seems to start ok by downloading the needed add-ons, but then comes a series of alerts “blabla is not compatible with this version of Kodi”. There are a number of such notices, like 4-6 (did not count) until it exits without enabling configuration of the main menu.
One would have imagined that the upgrade from 18 to 19 would have handled this, especially since there was a nag message every time I switched to Kodi from the TV, but not…
So now I have a system with way too many main menu items, which I cannot configure…
I have this same issue in v19. This was recently upgraded from v18 also, and the customization features were working in the previous version.
Unable to use “Enable Main Menu Customization” option, same errors about addons not being compatible.
“Skin Shortcuts” addon is installed but disabled. Cannot be enabled due to not being compatible error. “Skin Helper” Service was installed but I was able to remove from addons menu in attempt to fix, but when trying to reinstall it I get the same compatibility error.
Thanks for the reply, then I am not alone in this…
Seems like it should not be dismissed as “calm down” when a working system stops working properly after a suggested upgrade…
I wonder if there is a way to uninstall Kodi itself without touching the operating system and then install fresh from apt or similar?
The settings for media etc should be saved if possible.
All on an SSH command window preferably.
I went to the problem system and tried to find this, but failed…
On my system this is where I got:
Home → Settings → AddOn Browser →
But here there is no item “Kodi Repository”…
This is what I have on this page:
Install from repository
Install from zipfile
So how do I get to the item you mention (Kodi repository)
How to I activate the “Context menu”, I only have a remote control on the TV via CEC transfer…
So I went there and inside that I used the left arrow button and there was only “check for updates”, which I used. The result was a report popping up saying that there are updates available.
But nowhere could I see where I can command an update of the Kodi repository itself, which is what I understood is what is needed.
Rather I have not enabled automatic updates in the first place, I generally do not like software to self-update behind the scenes suddenly rendering it unusable or changed in major ways without I knowing why…
But the major problem was that when I tried to enable the home menu configuration it told me that it needed to install new add-ons to do that, which presumably meant that there was missing add-ons for that function and that they were going to be installed. Which failed…
So that add-on cannot need update since it is not even installed, it needs a new install and that is what is failing by the looks of it.
Can some of these things be done from the command line instead with commands like sudo apt install xxx or similar?
It feels like one could get much more control that way…
So, has the update for the skinshortcuts script been installed correctly and is the home menu customization working again? I’m not sure I can quite figure that out from your previous post.
The problem is, to be frank, exactly this. The Kodi migration process from v18 to v19 is dependant on addons pulling updates from the Kodi repo that are needed to let them stay functional under v19. This is not loosing control that you’re forced to do, but inherent logic of an update… Addons need to update in the process as well and if you disable this happening automatically, you need to trigger the process manually…
This is indeed unfortuntate and misleading. Our skin shows this information because the broken (v18) script seems to be flagged as not usable and thus basically not installed by Kodi. The info is passed on to the skin and we simply show what Kodi delivers. It should say the addon is disabled at least, I have to admit. Not much we can do about that though, but you might report this over at the Kodi forum: broken/non-functional addons shouldn’t trigger feedback to the skin indicating that the addon is not installed at all.
No, it is not working since I found no way to update the repository (I assume this means something like sudo apt update, which gets the lists of applications updated).
But I will walk over now and enable app updates and see what happens then.
Well, should be pretty self explanatory… You click on this:
…and press “Install all” or only on the skinshortcuts script entry.
To be honest, when selecting that one doesn’t want updates to install automatically, it’s not really too much to ask to know or at least figure out (by using Google or browsing the Kodi wiki directly) how to install them manually, if needed: https://kodi.wiki/view/Add-on_manager#Updating
And personally, I’d say, that checking for addon updates should be a no-brainer after having performed an upgrade to the system while having set addon updates to manual and running into an issue with such an addon. But that’s just my two cents…
I went over to the problem Kodi19 system again and tried to run updates for all with pending updates.
Some succeeded but NOT the one it seems like it is needed, namely “Skin Shortcuts” now it claims that:
“dependency on python 2.x.x not satisfied” (I was not quick enough to note down the numbers)
So it seems like it cannot find python with the correct version…
But from my command window (PuTTY) into the RPi system:
Thanks for this reply. I presumed Addon version mismatches were the issue here, but its been a while since ive used repositories, so forgot you could run those updates.
Happy to report this function is now working fine for me after updating all addons.
I went ahead and did this, essentially hosing all of my previous settings and starting over.
Now it was possible to enable home menu configuration which installed the Skin Shortcuts add-on successfully.
But in the process all of my configurations done over a number of years are gone and I have to either back-track or start over configuring the media center…
Anyway the problem with the add-on is now located in the .kodi_backup directory and not in the newly created active .kodi dir…