Hope all that makes sense
Nope. We like debug logfiles. They explain more than humans.
Posts by chewitt
-
-
If you can import from OVA there is a vmware image: Mirror List
If not.. I doubt there's an option as ISO is an optical media format and all our boot/run things are designed for disk media.
-
I have been using "adjust refresh rate to match video" on LE/OE systems since ~2010. It requires advanced/expert mode to be visible.
-
SSH to the IP address of the box Accessing LibreELEC - LibreELEC
-
There is an Emby GUI add-on in the Kodi repo. Never used it so can't speak of how good/bad/ugly it is.. but it's there.
-
Share files from Ubuntu over SMB or NFS and configure the shares in Kodi .. it's not hard. Look in the Kodi wiki for instructions if you need them.
-
Contact pimoroni and ask if they have spares. Have a look at the OSMC remote if an original Slice one isn't available. It's pretty similar in size and layout and you can steal the remote.conf from OSMC's github repo.
-
Your box does not technically violate our forum rules (yet) but the intent is clear and I have no interest in assisting users with the installation of pirate crapware that damages the name of Kodi and our project.
-
The replacement main board and PSU was handed over in Spain and it all works again. It's lost its spot as the family main box, but at least I can test stuff before publishing now.
-
I looked at updating the cacert.pem bundle we embed which is obtained from here: curl - Extract CA Certs from Mozilla but the update doesn't make any changes to Symantec/Verisign certs and the bundle doesn't need to contain intermediate CA details; in broad terms the signing chain will be followed through live queries until you reach a trusted or revoked certificate; and if neither is reached the process fails.
It's possible this is just another indeterminate LibreSSL problem - we've seen some random/unexplainable issues and it's the reason we switched back to OpenSSL in preparation for LE 8.2/9.0. If you can test a current milhouse Leia build (Generic and Pi hardwar) on a spare USB/SD card that would confirm if that solves the issue.
-
I can see lots "unable to connect to server" messages. I cannot see any references to .so not loading. We have no real expertise in the add-on; we simply build whatever upstream developers publish so it's probably best to start with the support thread in the Kodi forums.
-
The certs are baked into the system image so updating them requires the image to be rebuilt. It's something we can look at for 8.2 release, which should be in beta test soon-ish.
-
We got the overlayfs stuff needed for Docker working for the 3.14 kernel used in WP2 but the 3.10 kernel in WP1 is too old.
-
inputstream.adaptive for Krypton is being updated up with backports from master in prep for the 17.4-RC1 release. The k17_2 branch in peak3d's github repo is (or will become) the production repo for it. Current git HEAD fixed a bunch of issues that I was seeing - we did some joint debug and test last night.
-
Kodi debug log please.
-
It's not required for YouTube.
-
You can also uUse our USB/SD creator app (or Win32 disk imager, rufus, etc.) and restore bootsector.img to the USB. If the USB is not defected/damaged it should show in Windows as unformatted; and you can re-format.
-
Debug Kodi log from the RPI3 please.