In the absence of any pastebin'd debug logs or sample configuration our best guess is "user error" 
Posts by chewitt
-
-
"journalctl -b 0 --no-pager | paste" and share the URL generated
-
Someone PR the required changes to GitHub pls.
-
Use English please.
-
Make sure the BIOS is current, see MrChromebox.tech - and if things continue submit a Kodi debug log. If Kodi is in debug mode the events that lead up to the crash should be in /storage/.kodi/temp/kodi.old.log
-
Skins are a very personal choice .. which is why Kodi ships with a simple and well-maintained default skin and an add-on repo where more exotic skins can be found if people feel the need for them. There's nothing to stop us from creating an official LE skin, apart from low enthusiasm among the team for the long and skilled task of actually making one.
-
Top right above the "edit thread" and "reply" buttons there's two icons. The right-most one allows you to manage subscriptions.
-
There are no current plans to add the dual-audio
hackpatch to standard LE image(s). -
Hard to say. Your NAS has basically no configuration options for Samba so the only part that can be changed is the SMB client in Kodi. If this refuses to talk to your NAS even when restricted down to SMB1 something weird is wrong. I'd ask to see the log files from the NAS but that requires you to pastebin a log file and not send twenty screenshots, and I have zero knowledge on QNAP products (or any desire to obtain any) so I won't be giving detailed instructions on how that's done. Plan Z .. stick with LE 8.0.2 if it works.
-
LDAP has fcuk all to do with SMB support.
-
Apparently I'm unable to upgrade between the two. When I put the .tar in the updates folder and restart, I get a message that the .tar is incompatible with my "WeTek Hub aarch64" hardware.
The update script performs compatibility checks and switching arch is not supported unless the canupdate.sh script embedded in the target image has been tweaked to allow the update path <= GDPR-1
-
As long as the USB is formatted (avoid the HFS+ macOS format) all you need to do is connect it and it will auto-mount.
-
Any other ideas are welcome
^ open two terminal windows: first window has the LE 8.2 branch cloned and second window has kernel sources cloned. Start the git bisect process on the kernel and use it to generate githashes you can use with the LE build system linux package. Create test images and test them, then mark the githashes good/bad until the bisect process identifies the problem commit. The way we patch things might require occasional fettling but the kernels are normally quite stable. NB: I would start with doing a test without the big RPi update patch; if things are not right without it you can drop that from builds. It is rebased with each kernel bump so it's the main item that will create problems for the bisect process.
-
In future bump an existing thread please - don't repost the same thread twice
-
We switched forum software several months ago and the new board is not supported by Tapatalk (and no signs of them updating the old/broken plugin they made in the past). The mobile interface on the board isn't bad so it's not something we plan to investigate further.
-
LE supports 4k output on devices that support 4k output, there is nothing particularly magic about OSMC in that regard. Sam is normally focussed on having OSMC support the hardware that OSMC sells/supports so the answer is "probably, as S9XX boxes are all pretty similar, but it's up to you to figure out how to accommodate differences and make things run" and if you need help with that you are definitely in the wrong forum.
-
I'd assume there's no key for the disc in the DB because Kodi can only see the encrypted filesystem. There's not much we can do about that.
-
BlueBorne is nasty due to the immense volume of vulnerable devices but Bluetooth is a short-range PAN protocol and in practical terms this means an attacker needs to be within 3-5m of the box to exploit it, i.e. in the same room. As a result we're not too concerned and our advice would be to continue using things as normal. Once patches for kernels and bluez are available and we've been able to test things we will roll them into our next normal release or maintenance release.
