Vero 4K: should I move to Kodi v19 safely?

I am still using Kodi v18 (without any issue) and I’m wondering if I should upgrade to Kodi v19. Is it mandatory? What should I do before upgrading to avoid any trouble?

Nothing is mandatory in the opensource world :wink:

Suggest to do a backup via MyOSMC.
And maybe check on if all your addons are supported.

Backup done and upgrade launched. But after reboot I’m stuck on Building Menu (more than 30 minutes). Aeonnox is the skin.

Did the Database upgrade already happen?
If the building menu doesn’t finish I suggest to ssh into OSMC and remove .kodi/userdata/guisetttings.xml and reboot.

Yes fzinken, the upgrade of the database was done.

Connected: It says

osmc@vero:~$ .kodi/userdata/guisetttings.xml
-bash: .kodi/userdata/guisetttings.xml: No such file or directory

There was a t too much in my post and I meant to remove it, means executing rm .kodi/userdata/guisettings.xml if you want to keep it for later checking can run mv .kodi/userdata/guisettings.xml .kodi/userdata/guisettings.xml.bak

But without the extra T, it is the same reply:

osmc@vero:~$ rm .kodi/userdata/guisettings.xml
rm: cannot remove ‘.kodi/userdata/guisettings.xml’: No such file or directory

That is scary, whats the output of ls -lah .kodi/userdata/

It gives:

osmc@vero:~$ ls -lah .kodi/userdata/
total 112K
drwxr-xr-x 10 osmc osmc 4.0K Dec 30 12:12 .
drwxr-xr-x 8 osmc osmc 4.0K Apr 16 2020 …
drwxr-xr-x 3 osmc osmc 4.0K Dec 30 12:29 Database
-rw-r–r-- 1 osmc osmc 389 Nov 18 2019 RssFeeds.xml
drwxr-xr-x 2 osmc osmc 4.0K Nov 18 2019 Savestates
drwxr-xr-x 19 osmc osmc 4.0K Nov 18 2019 Thumbnails
drwxr-xr-x 30 osmc osmc 4.0K Dec 16 2020 addon_data
-rwxr–r-- 1 osmc osmc 186 Nov 11 09:44 advancedsettings.xml
-rw-r–r-- 1 osmc osmc 2.3K Oct 31 10:34 favourites.xml
-rw-r–r-- 1 osmc osmc 159 Dec 30 10:30 fstab
-rw-r–r-- 1 osmc osmc 38K Dec 30 11:17 guisettings.xml.bak
drwxr-xr-x 2 osmc osmc 4.0K Nov 18 2019 keymaps
drwxr-xr-x 2 osmc osmc 4.0K Nov 18 2019 library
-rw-r–r-- 1 osmc osmc 188 Apr 18 2020 passwords.xml
drwxr-xr-x 2 osmc osmc 4.0K Apr 17 2020 peripheral_data
drwxr-xr-x 5 osmc osmc 4.0K Nov 18 2019 playlists
-rw-r–r-- 1 osmc osmc 960 Dec 30 11:18 profiles.xml
-rw-r–r-- 1 osmc osmc 2.7K Oct 31 10:28 sources.xml
-rw-r–r-- 1 osmc osmc 256 Dec 30 11:17 upnpserver.xml

So means you already executed the mv command. So all good.
Now sudo systemctl restart mediacenter

Restarted. Now logged with the default skin.

Yes, that is what removing the guisettings file initiated. You could try to change Skins now.

Now every thing now works. :+1:
A big thanks to you. :raised_hands:

1 Like