OSMC's February update is ready with a wide range of improvements and fixes to keep your OSMC device running in tip-top shape. Team Kodi have now announced that they have started the official alpha release cycle for Kodi v18 (Leia). Test builds for Raspberry Pi and Vero devices are available in our forums.
i got âan error occured while installing the following package: (unknown package)â. It then tells me to report this on the forum. I donât have logs enabled and after reboot it says i got February update installed.
tried :
root@osmc:/home/osmc# sudo apt-get update && sudo apt-get -y dist-upgrade
Ign:1 Index of /debian stretch InRelease
Hit:2 Index of /debian stretch-updates InRelease
Hit:4 http://security.debian.org stretch/updates InRelease
Hit:5 Index of /debian stretch Release
Hit:3 Index of /osmc/osmc/apt stretch InRelease
Reading package lists⌠Done
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:/home/osmc#
After the installation of this update and after a reboot, no IP address is assigned. It says Internet is not working, although it could download the update and install. Now it is not reachable.
Using My OSMC: I see the Wired network adapter is disabled. Tried enabling it without success. Donât know why. This is bad.
Unfortunately itâs hard to advise what the issue is as you havenât told us which device youâre running OSMC on or whether youâre using WiFi or a Wired connection.
To get a better understanding of the problem you are experiencing we need more information from you. The best way to get this information is for you to upload logs that demonstrate your problem. You can learn more about how to submit a useful support request here.
Please start a new post as this thread is not intended for troubleshooting.
It seems this update has broken my Bluetooth dongle (official dongle, bought from the OSMC store). After the update the Bluetooth menu item was missing from MY OSMC/Network but I could make the system recognize it by plugging out and in. Still, turning on the device does not work. Neither from the GUI nor using bluetoothctl (power on command).
I get a generic error:
[bluetooth]# power on
Failed to set power on: org.bluez.Error.Blocked