2019-12-24 21:39:04.943 T:140611201242880 ERROR: ## LibreELEC Addon ## bluetooth::dbus_error_handler ## ERROR: (Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.)If other Bluetooth devices pair, then it's probably option one of the log line.
Okay, second try, got to the network setup again and ... black screen.
Please try the last 9.1.x version, and in case of success upgrade by GUI to the latest.
No problem. Marry X-Mas and some great time in 2020! 
I bet Steam OS has the capability to re-install the boot loader (BIOS MBR in your case). Then you don't need an unwanted extra Linux.
The point is that sometimes (like after major Win 10 updates) you have to re-install the boot loader. Do a research whether Steam OS has such capability, just to be sure. The boot loader will find all installed OS'es, including LE.
I'm not sure whether Win 10 likes the shrinking. If you have to re-install all OS's, do Win 10 first, then Steam OS (if it can re-install the boot loader), then LE.
Is there a easier way to proceed? Is there any update on this? My ultmate goal is to use my Intel Nuc with Windows 10, LibreElec, then Steam OS.
You will have those problems with any other multi-boot Linux OS, too. That is no special LE question.
However, I had dual boot Win 10 / Ubuntu for a long time. This year Win 10 updates sucked so much, that I've been deleted Win 10.
My multi-boot install was like this:
If you have trouble to find any OS after reboot, use Super Grub2 Disk to boot into Linux, and reinstall the boot loader (EFI partition).
The problem is that LE don't have the capability to do this. So, I suggest to have one Linux OS installed (Ubuntu etc.), which let you reinstall the boot loader. This means, the first OS after the Win 10 installation should be such a complete Linux. Maybe Steam OS has such capability, too, but I don't know.
Sometimes, if you can't reboot into an OS, you have to re-select the first bootable partition at the EFI settings (usually the Linux partition, which leads to the GRUB boot selection screen).
Looks like an NFS config error:
2019-12-19 17:21:53.384 T:1554932608 ERROR: Open - Unhandled exception
2019-12-19 17:21:53.384 T:1554932608 ERROR: Open - Error opening nfs://192.168.42.40/volume1/Video/The Circle/the_circle.iso
2019-12-19 17:21:53.384 T:1554932608 DEBUG: CNFSFile::Close closing file volume1/Video/The Circle/the_circle.iso
2019-12-19 17:21:53.384 T:1554932608 ERROR: Error opening image file or Error on dvdnav_open_stream
2019-12-19 17:21:53.384 T:1554932608 ERROR: CVideoPlayer::OpenInputStream - error opening [nfs://192.168.42.40/volume1/Video/The Circle/the_circle.iso]Compare the NFS config of the RPi4B and your lower device versions.
The Blue-ray ISO's maybe have different Linux permissions, so they work.
Use advancedsettings.xml to activate log level 2 (copy the content of "Example 1").
This should create a useful kodi.log at boot time.
Your add-on is not a reliable way to use an MCE remote.
Disable or uninstall the add-on, and use the built-in solution instead.
The MCE remote should work without enabling LIRC.
I did
Then you can run the reboot command on SSH. Does it still go into safe mode after reboot?
The instructions of my above link should work for getting the logs (read the tab "Via SSH").
Check your NFS device, because it seems to work with errors.
You have to use the username root to successfully login.
Generally spoken, whenever safe mode appears, login by SSH, and enter the reboot command.
Hopefully everything runs fine after that reboot.
Then grab available log files from /storage/.kodi/temp to find the cause of the crash.
The interesting log files after reboot are kodi.old.log and kodi_crashlog_<your_current_date>.log.
Read here about logging on LE.
Your current log says, you have an NFS error:
2019-12-15 12:17:16.452 T:140247249708800 ERROR: Failed to open(//Seagate_Expansion_Drive_2_3/Kodi addons/Logo/) opendir call failed with "NFS: Lookup of /Seagate_Expansion_Drive_2_3/Kodi addons/Logo failed with NFS3ERR_NOENT(-2)"
2019-12-15 12:17:16.452 T:140247249708800 ERROR: GetDirectory - Error getting nfs://10.0.0.60/nfs/Seagate_Expansion_Drive_2_3/Kodi addons/Logo/
2019-12-15 12:17:16.459 T:140247249708800 ERROR: Failed to open(//Seagate_Expansion_Drive_2_3/Kodi addons/Logo/) opendir call failed with "NFS: Lookup of /Seagate_Expansion_Drive_2_3/Kodi addons/Logo failed with NFS3ERR_NOENT(-2)"
2019-12-15 12:17:16.459 T:140247249708800 ERROR: GetDirectory - Error getting nfs://10.0.0.60/nfs/Seagate_Expansion_Drive_2_3/Kodi addons/Logo/Then everything Worked!. (Irserver needed to be started Before LCDProc)
BUT.... The Remote seems abit slow, when im Navigating up, down left or right in menus , and say press down 2 times fast, kodi would only register one key press? on windows OS, it didnt do this?
LCDProc shows errors at the log. Do you get better IR response if you disable LCDProc?
Thanks. Read here about log files. Post the link to the log.
You can't expect answers if you don't give answers. That's a fair game in my eyes.
At least a log file is needed to say anything.
I had a similar issue on my RPi 3B+: The picture was darker than regular TV. After switching to a better PSU, the picture is as bright as TV. This is still a mystery to me, because HDMI is digital, and digital has no strong and weak signals. Probably it's about signals before HDMI.
Tell us details about your hardware.
Which PC / NUC do you use?
Which IR receiver do you use? (adapter or built-in)
What's the complete model name of your remote control?
Does the remote control work with other OS'es, like Windows?
