Newest log: https://paste.osmc.tv/isizipajeq
You should have your database still.
ls -lh .kodi/userdata/Database ls -lh .kodi.save/userdata/Database cat .kodi.save/userdata/advancedsettings.xml
Show me the output of those commands please.
osmc@osmc:~$ ls -lh .kodi/userdata/Database total 2.0M -rw-r--r-- 1 osmc osmc 1.3M Jul 13 23:02 Addons27.db drwxr-xr-x 2 osmc osmc 4.0K Jul 13 23:02 CDDB -rw-r--r-- 1 osmc osmc 28K Jul 13 23:02 Epg12.db -rw-r--r-- 1 osmc osmc 212K Jul 13 23:02 MyMusic72.db -rw-r--r-- 1 osmc osmc 368K Jul 13 23:02 MyVideos116.db -rw-r--r-- 1 osmc osmc 40K Jul 13 23:02 TV32.db -rw-r--r-- 1 osmc osmc 76K Jul 13 23:12 Textures13.db -rw-r--r-- 1 osmc osmc 20K Jul 13 23:02 ViewModes6.db osmc@osmc:~$ ls -lh .kodi.save/userdata/Database total 38M -rw-r--r-- 1 osmc osmc 28K Aug 5 2018 ADSP0.db -rw-r--r-- 1 osmc osmc 1.4M Jul 13 22:48 Addons27.db drwxr-xr-x 2 osmc osmc 4.0K Aug 5 2018 CDDB -rw-r--r-- 1 osmc osmc 28K Aug 5 2018 Epg11.db -rw-r--r-- 1 osmc osmc 28K Apr 22 01:43 Epg12.db -rw-r--r-- 1 osmc osmc 344K Jan 16 21:04 MyMusic60.db -rw-r--r-- 1 osmc osmc 376K Jun 15 21:50 MyMusic72.db -rw-r--r-- 1 osmc osmc 15M Apr 21 23:54 MyVideos107.db -rw-r--r-- 1 osmc osmc 14M Jul 13 22:27 MyVideos116.db -rw-r--r-- 1 osmc osmc 32K Aug 5 2018 TV29.db -rw-r--r-- 1 osmc osmc 40K Apr 22 01:43 TV32.db -rw-r--r-- 1 osmc osmc 7.6M Jul 13 22:27 Textures13.db -rw-r--r-- 1 osmc osmc 28K Jun 23 20:17 ViewModes6.db osmc@osmc:~$ cat .kodi.save/userdata/advancedsettings.xml cat: .kodi.save/userdata/advancedsettings.xml: No such file or directory osmc@osmc:~$
Ok, do this then to get the database back:
sudo systemctl stop mediacender mv .kodi/userdata/Database .kodi/userdata/Database.save cp -r .kodi.save/userdata/Database .kodi/userdata/Database cp .kodi/userdata/Database.save/Addons27.db .kodi/userdata/Database/Addons27.db sudo systemctl start mediacenter
That should restore the databases.
osmc@osmc:~$ sudo systemctl stop mediacender Failed to stop mediacender.service: Unit mediacender.service not loaded. osmc@osmc:~$ mv .kodi/userdata/Database .kodi/userdata/Database.save osmc@osmc:~$ cp -r .kodi.save/userdata/Database .kodi/userdata/Database osmc@osmc:~$ cp .kodi/userdata/Database.save/Addons27.db .kodi/userdata/Database/Addons27.db osmc@osmc:~$ sudo systemctl start mediacenter osmc@osmc:~$ Connection to 192.168.50.226 closed by remote host.
Database is back.
What about settings?
You mean the gui settings? Try stopping kodi again and:
cp .kodi.save/userdata/guisettings.xml .kodi/userdata/guisettings.xml
and start Kodi again.
Maybe I need to install all these skin addons first.
What exactly isn’t working now? Still getting the error? Because starting with a new Kodi config should have reset all of the default addons. If you had any other addons then you will have to reinstall them.
Yeah that error is gone for sure now.
But unfortunately so are all my settings and movie sets and my childrens profile and…
It’s pretty much as if I just got it for the first time right now.
Time to grab a beer I guess and do this from scratch.
Unless you got another trick up your sleave?
AFAIK movie sets are stored in the database, so that may just be a setting to get it to show the sets.
You did do
systemctl stop mediacenter
before copying guisettings.xml, right?
As to the childrens profile, you will find the original in .kodi.save/userdata/profiles
Create a new profile (using the same name) for the kids. Then stop Kodi and copy all the file in .kodi.save/userdata/profiles/ to .kodi/userdata/profiles/. Something like this:
rm -rf .kodi/userdata/profiles/Kids/* cp -r .kodi.save/userdata/profiles/Kids/* .kodi/userdata/profiles/Kids
should do the trick.
The problem is all my settings are default, so I enabled movie sets that fixed that.
I view everything in list mode but for some reeson when I go into a movie set it displays as wall.
So I changed it, then went into another set and that new set was displayed as wall.
Do I need to change this on every set now (I didn’t before) or is ther some global option/setting I’m missing?
I’m not sure where that information is stored, so it may be easier to just fix them manually if you don’t have lots of them. I’m gonna have one more beer myself and then it’s bedtime for me as I have to be up in 8 hours since I work today. I could dig into where the set information is being saved but it won’t be until I get home from work. At least I got you back up and running mostly
Thanks for all your help!
No problem. Sorry I didn’t get it completely fixed for you, but at least we got close. I think I know where I went wrong in my instructions but I’d have to do some testing to be sure. I think where I was wrong was when I had you do the original
cp -r .kodi.save.. I now think it should have been
cp -r --remove-destination .kodi.save...
Small update… the skin helper error is completely gone now and I can customize my home menu again.
I had to go back and fix a bunch a settings too get things back to how they were before but that is now all done.
The only issue I have now is with movie sets appearing as “wall” instead of “list” by default.
I went into every movie set and changed them from “wall” to “list” one by one but if I add a new movie set it still wants to display them as a wall.
I do everything as a list (movies, tv eps, etc.) and in the past all new movie sets were displayed as a list by default.
So something has changed somewhere so that the new default is “wall”.
I’ve done a lot of work to move from one minor annoyance (skin helper errors) to another minor annoyance (movies sets display as wall by default instean of list).
I’d imagine theres a global setting hidden somewhere and I’m just missing it.
Great to hear that!
From what I can see here on my test setup: If you have your movie library view set to list, the collections will use list as well. If you’ve set it to wall, they’ll use wall by default.
Only if you change the view of a collection to something different than the rest of the movie library, the view setting will stick for that collection. Some interesting logic, Kodi has implemented there.
Can you guys look at this thread and see if that issue may have been caused by something we did resolving this issue, maybe an unintended consequence.
Has nothing to do with this.