Please try again and if there is no update, post a log.
I can see the changes have been pushed.
Hi SAm,
I’m running update from ssh:
root@osmc:~# sudo apt-get update && sudo apt-get dist-upgrade
Hit:1 http://archive.itimmer.nl/raspbian/moonlight stretch InRelease
Ign:2 http://ftp.debian.org/debian stretch InRelease
Hit:4 http://ftp.debian.org/debian stretch-updates InRelease
Hit:5 http://security.debian.org stretch/updates InRelease
Hit:7 http://ftp.debian.org/debian stretch Release
Hit:3 http://ftp.fau.de/osmc/osmc/apt stretch InRelease
Hit:6 http://ftp.fau.de/osmc/osmc/apt stretch-devel InRelease
Reading package lists... Done
N: Skipping acquire of configured file 'main/binary-arm64/Packages' as repository 'http://archive.itimmer.nl/raspbian/moonlight stretch InRelease' doesn't support architecture 'arm64'
Reading package lists... Done
Building dependency tree
Reading state information... Done
Calculating upgrade... Done
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
root@osmc:~#
Seem’s that I’m on latest.
Log from last try: https://paste.osmc.tv/xedunutaya.xml
going to bed now…
top notch customer care as always Sam, thank you.
Anthrax
I’m looking in to this now.
Seems to work again - after I tried another update something was installed.
happy, happy, happy
Anthrax
Mine is not working still. Ran some update through GUI just now.
https://paste.osmc.tv/quvogefato
Is there a way to downgrade?
I’m a bit mystified about something in your log. Perhaps you, or someone else, can explain.
Your logs show that the version of vero3-mediacenter-osmc you’ve been running since 12 April is 18.8.23. The version of kodi.bin on your system was compiled on 11 April, so the dates both agree.
The current version of vero3-mediacenter-osmc in the staging repository (stretch-devel) is 18.2.0-14. Since version 18.8.23 is a higher number than 18.2.0-14, it will not automatically update to the latest version of the package.
It might be possible to force a reinstall to version 18.2.0-14 but do you have any idea how you are on version 18.8.23 of the vero3-mediacenter-osmc package?
Looks like he is running a v19 nightly
Sam
I don’t know. I was beta testing Lelia before official release. I thought I made the changes to stop downloading nightly builds. Could you please tell me best way to fix to get back up and running and prevent updating to betas?
You can try this:
sudo apt-get update
sudo apt-get install --reinstall vero3-mediacenter-osmc=18.2.0-14From the Kodi log: Starting Kodi (18.2-RC1)
I ran those commands. Went through downgrade process and rebooted. Still not working.
osmc@osmc : ~ $ dpkg -l | grep mediacenter-osmc | awk ‘{ print $3 }’
18.2.0-14
Does this help:
systemctl stop mediacenter
cd
mv .kodi kodi-backup
systemctl start mediacenterThat basically reset device. No more settings, media, etc. Do I have to start over now or is there a way to revert?
You can revert.
This is a test to see if the Kodi code is failing or if there is something in your configuration that is causing the problem.
To revert:
systemctl stop mediacenter
cd
mv .kodi kodi-new
mv kodi-backup .kodi
systemctl start mediacenter
But first, I’d suggest that you add some data sources and see if it’s still stable.
Ok. Added source and played a couple movies fine. Reverted back. Played one movie fine then failed for next couple tries. What do you suggest now? Thank you for assistance.
Tried changing to default skin. Still failed.
It seems that it’s something in your configuration, possibly a setting, or combination of settings, that Kodi doesn’t like, or possibly a data corruption.
You now know how to move between your new and old configuration, so I’d suggest that you return to the new (clean) configuration and first add all your sources. Then, step by step, add the rest of the changes you want to make – and remember to test each time you make a change.
Matrix builds are in a separate repo so you would’ve had to add these too.