Yes, I added the staging repo. I thought that the April build meant that I did that, that’s what I was trying to say.
Are you using profiles?
No…
Okay, if people are still experiencing this:
- force debug in /usr/bin/mediacenter-osmc
- upload a debug log after the issue occurs
If there are a set sequence of steps to reproduce this reliably, that’d be good to know.
Sam
When I updated to the staging repo, I thought the issue was gone. But I made two reboots in a row today, and the OSMC skin was back, as were all my settings back to default.
I’m also install this devel on my Pi2 setup… at reboot estuary still remain active. In this last week apparently i don’t have obtain this little issue anymore.
i have update on the staging repo, i am not using profiles and i just got a settings reset.
Do you mean the skin got reset or only the system settings got reset. Only had issue with system settings. In meantime you can backup guisettings.xml when you set all settings.
Then restore it if reset happens again.
the_bo…
I have the same issue from time to time:
I use Estuary skin, done all settings (language, region, subtitles…).
I installed my addons and made all settings.
Everything seems to be ok.
I switched my Raspberry off.
For a few days everything is ok but sometimes – surprise - I was faced with OSMC skin again!
So, I had to select Estuary skin, again.
All addons are here, all settings within the addons are ok.
But the general setting of Estuary skin are set to default ones – language, region, character set, no subtitles…it takes a few minutes to set them back but it’s very annoying…Now I do backup restore to save the time…
Conclusion: during the same session I have Estuary skin all the time, even if I exit/reboot for a few times, but when I turn out my Raspberry off nobody knows what I’m going to find next time…
I already reported that to Sam a few weeks ago so I hope he will figured something about that…
My workaround (work’s with profile)
backup guisetting.xml
enable Loginscreen
check the screen, before login
and when it is the “bad” screen, replace guisettings.xml
i should tell my 75 year old parents that? lol
Why not, i can do it with 64 years. Sometime old people tell to ??? ----> Yes I can
PS: and I think that Sam works for found a solution, but sometime spend the time to “laught” isn’t enough for found the solution.
how do I backup and replace guisetting.xml on the pi?
Login via ssh
Backup: cp .kodi/userdata/guisettings.xml .
Restore:
sudo systemctl stop mediacenter
cp guisettings.xml .kodi/userdata/
sudo systemctl start mediacenter
Preesh
you can download windows program winscp which lets you drag and drop files from your pc over to your pi. much easier
Thanks but i’m currently on Lnux
Then just use ssh. Should be available on a linux systems.
ok so i’m apparently tarded, its asking for a password so I enter the default ‘raspberry’ and get access denied
User: osmc Password: osmc (assuming you haven’t changed them)