Looks like the de_de language file might be corrupted.
Can you run:
cat /storage/.kodi/addons/resource.language.de_de/resources/langinfo.xml | pastebinitand post the url?
Then run:
rm -fr /storage/.kodi/addons/resource.language.de_de
rebootand this will hopefully stop Kodi crashing - your language will now be "None" in Kodi. Flick the language back to English, then select German again so that it can be re-installed, and hopefully you should be all good!
I'm torn because I care about both, but as an outsider and an amlogic user, I see that there are things that don't work in libreelec but do in coreelec. I'm currently using libreelec but planning to switch to coreelec due to the above, however, reading these messages, I'm not sure it's the right thing to do.
We/I don't dispute that CoreELEC is likely a better option right now for Amlogic users, so don't feel bad if you want to switch, we won't hold it against you! 
The simple fact is that a while ago we (LibreELEC) came to the conclusion/realisation that Amlogic on a largely unmaintained and end-of-life 3.14.y vendor kernel had no long-term future without hacks (kernel, Kodi and numerous other packages) so we opted to put Amlogic 3.14 on ice/life support while focusing development effort on mainline Amlogic support which is only now - finally - coming to fruition. You'll be back, trust me... 
There seems to be some bad paranoia going down here.
Shoog
Sure, sure.
Whats your nightmare is everyone else's joy. When it comes down to it all the average user should care about is a working OS which is what adams team has delivered. Take a chill pill all this hate is bad for you.
Shoog
The "hate" is pretty much in one direction - towards us - hence the sock-puppet accounts you'll find on the internet where hate is spewed towards chewitt, myself and LibreELEC in general even though we have and want nothing to do with CoreELEC.
If CoreELEC works for you that's absolutely fantastic, I totally get that as a user you only care about the product and not personalities, but we (as a development team) don't want or need others harassing/abusing _our_ members, and interfering with and generally spreading FUD about _our_ project, thank you very much.
This shows a non inclusive behavior from your part. Technical limitations and strategic/political decisions apart, this type of messages don't help the community (or communities) to get a long.
Being an outsider, and have only followed up the story via forum posts, I personally don't see the need to send someone f* up.
It's offensive and it shows a utter lack of respect for the next.
Unfortunately you probably aren't aware of the back story[1] to all of this, but the "smurfette" socket puppet is the CoreELEC admin (AdamG) spreading FUD - this is at least his second or third LibreELEC forum account to be banned after trash talking the LE project and/or members, and he also impersonates LibreELEC forum members on other sites spewing more hate towards LibreELEC team members.
It's pathetic, so yeah, the non-inclusive behaviour is fully warranted!
1. I'll give you a potted summary: the CoreELEC founders claim they were "thrown out of Team LibreELEC" when in fact they left of their own accord because they couldn't handle their Amlogic contributions being peer-reviewed, and since then they've been sniping at LibreELEC while consuming _everything_ we produce and giving _nothing_ back. They left, it was their choice, and they're full of animosity/hate - there's little we can do about how they feel to be honest, but we certainly won't tolerate their sh*t on our forum.
RPi3B+ HEVC support is very good up to 720p, but you will experience frame drops with some (possibly, most) 1080p @ 30fps content (1080p @ 24fps is usually handled pretty well). A small overclock may help (particularly SDRAM, which is the limiting factor with 30fps content) but unfortunately the RPi3B+ is already on the edge of what it's capable of with HEVC, so there's no guarantees with 1080p @ 30fps HEVC content.
Edit: to clarify difference between 1080p@30 and 1080@24.
where the system cannot 'shutdown' or 'suspend', due to Xorg getting 'stuck' (and it's process running-away at 100% CPU) during the 'shutdown' process (as per tailing the 'kodi.log' file).
When this happens, can you pastebin the contents of /var/log/Xorg.0.log and post the link?
I have the same issue but no one is responding.
Because it's almost certainly a Kodi issue - LibreELEC is just the OS that runs Kodi, if there's a problem with the way Kodi processes JSON requests then the OS is unlikely to be the issue. Try testing on Windows instead of LibreELEC and see if you get the same results, I'm pretty sure you will.
Whoever advised you that LibreELEC is at fault has advised you incorrectly - you should be reporting this directly to Kodi on their github.
You know the use case could be to make the transition easier. And since hyperion is using it so you could update it.
Until Kodi 19 uses Python 3 as a language interpreter, including Python 3 (as an add-on or not) would not help with the transition as Kodi would continue to use only Python 2 when executing Python add-ons.
Installing Python 3 into the image as well as Python 2 is a very niche requirement, which is why it hasn't been done so far. And for much the same reason nobody has submitted a Python 3 add-on as there isn't really the demand for it.
Also, the version of hyperion that is supported by LibreELEC 9.0 is using Python2. If someone wants to use a different and unsupported version of hyperion that has different Python language requirements then that is not our problem to solve.
And Cryologic has a use case. Package is already there.
@Crylogic hasn't explained what his use case actually is - he only asked why we don't include Python 3, which has now been explained.
And to my knowledge a package for a Python 3 add-on does not exist, but if anyone wants to submit it as a PR we can consider it, or better yet a community builder can build it/host it as it will have a very short life span.
Why Coreelec, Alexelec have Python 3? Only you cannot use Python 3? why?
Installing both Python3 (that cannot be used by Kodi) side-by-side with Python2 (which is used by Kodi) makes no sense for a size optimised distribution like LibreELEC that targets Kodi - including Python3 at this time would benefit almost nobody and be a waste of space for everyone else. LibreELEC will replace Python2 with Python3 during the Kodi 19 development cycle.
Not all add-ons are compatible with Python 3, that will change as Kodi 19 mandates Python 3 support but for now Python 2 is the best way to ensure add-on compatibility with existing add-ons.
Not really sure, unfortunately - it's a Kodi issue (as kodi is crashing) so it might be best to report it on the Kodi Github (open an issue).
Try enabling wait for network in LibreELEC settings, as you've enabled wake on access support in kodi which is most likely crashing when it doesn't have a network.
Yes sorry, I had misread the posts in this thread and thought the problem was with the cputemp script. I've closed the PR now.
The easiest solution to fix the problem with Kodi is to add:
<advancedsettings>
<cputempcommand>/usr/bin/cputemp</cputempcommand>
</advancedsettings>in advancedsettings.xml.
Display MoreSorry, got busy.
http://ix.io/1qe0
I hate to combine issues, but one of my libreELEC installs always shows the GUI elements when it has the black bars in a movie. its like its not clearing the screen.
https://ibb.co/f5jjvq
Any idea?
Remove custom calibration settings from Kodi and set your TV to 1:1 pixel mapping.
I'd say it's probably "no", but your welcome to get creative with variable substitution: smb.conf and see if that can work for you.
Fur example, try creating /storage/.kodi/.smb/user.conf with the line:
include /storage/.kodi/.smb/%j.confthen in (for example) /storage/.kodi/.smb/192_168_0_20.conf you can try configuring the required client settings whenever you connect to the server that is 192.168.0.20.
It's in LE master so any recent LE9-based build will have it. For LibreELEC 8.2.y you'll be dependent on a custom backport.
Network booting on RPi 3B+ is unreliable due to kernel and firmware issues that were resolved after the release of LibreELEC 8.2.5. Since we have no plans to issue further 8.2.y releases you'll need to switch to a LibreELEC 9.0 alpha release such as 8.90.003.
It looks like the addon is out of date, or had a dependency on another addon (possibly Chrome) which no longer includes those libraries.
Try installing this version of the addon - it's for LE9, so may not work with LE8.2.5:
service.tigervnc-9.0.103.zip