???
I do not expect ANY software to be error free 
I was under the impression that the whole point of alpha releases is to get some testing so at least the number of errors can be kept at a minimum.
Sorry for misunderstanding. Will only report problems in release versions in the future.
Also this might help you.
The above is from my keymap.xml. I'm not familiar with that specific Harmony remote, so I do not know whether you need to change also your remote.conf. So I recommend to just enable debug logging and check the kodi.log for the button names. If these look fine, you do not need to change your remote.conf. For more understanding of how these things work you might to look here, here and here.
If your current kernel configuration is based on one that has been working before, the kernel is probably just find and your boot problems have some other reason.
I have redefined some keys in my Lircmap.xml and am using the following in my keymap.xml (this is with an USB MCE, not a Harmony):
<global>
<remote>
<display>FullScreen</display>
<start>ActivateWindow(home)</start>
</remote>
</global>
So you need to find out what corresponds to the button names "display" and "start" on your remote. You can find out by enabling debug logging in kodi and running "tail -f .kodi/temp/kodi.log" while pressing buttons.
Since I'm running leia on my kodi client I get many error messages in the kodi.log. This only happens when watching recordings and it seems to not have any negative effects. Watching live TV is fine though. The server is running LE 8.2.3, the client latest master as of today. Not sure if this is really just a cosmetical issue...
The vdr server does not report any problems (default loglevel 1).
Try "lan951x-led-ctl f0 d0 l0"
I have thought that NFS-server is not (and can not easily be) enabled in Libreelec?
I solved the problem by mounting the remote filesystem with sshfs (Network Tools addon).
Ahh, I thought that libreELEC is the client.
It is a shame that libreELEC (linux based) is missing the tiny NFS server but provides the much bigger samba stuff.
The mangled names function in Samba was deprecated aeons ago so it's not the solution. You have two choices:
a) Investigate the "catia" vfs module which can map the illegal : character into something legal
b) Rename files so they don't use the illegal : character
c) Use NFS instead of samba which does not have this limitation
Maybe try the combination of nohup and the ampersand: "nohup command &".
If I issue this command from a shell, log out from the kodi box and re-login again I can see the command still running. Which does not mean it will work for you as well, but you might give it a try.
Always doing a "make clean" is not necessary. The build system ensures that only new stuff gets rebuilt. So if you just add some patch to eg. kodi itself, only kodi will get rebuilt but all the rest of the system is unchanged. Why are you wasting so much time and always do a "make clean"?
The version number is part of the build tree, so when going from 8.2.1 to 8.2.3 everything needs to get rebuilt. Renaming the existing tree does not help as the absolute path is contained in many files. If your changes survive in the new version depends on how you did it. Did you commit them and did you set up your git to rebase on pulls?
Try "nohup /usr/bin/pegasus-fe.sh"
ERROR: CAESinkALSA::Initialize - failed to initialize device "Default"
I know self-follow-ups are lame, but this error message gave me another idea: I just re-installed the latest milhouse build and explicitly tried to set the audio output. With the newer kernel, I have two more options and guess what: One of them is working just fine (it is HDMI#2 which did not exist with kernel 4.11.12).
And channel switching in Live TV works just fine by using page up/down instead of cursor up/down. So not a regression, but a dumb user (usually I'm using a remote and no keyboard, so I got it wrong).
It's definitely a kernel bug. I just built 9.0 alpha with kernel 4.11.12 (that had been used in LE 8.2.3) and the problem is gone. Really like the improved seeking and skipping in videos; much more instant and reliable!
Live TV also (mostly) works. I just cannot switch channels by using up and down keys. But when picking from the channel list, I can switch to any channel.
kodi.log still contains this scary line:
ERROR: CAESinkALSA::Initialize - failed to initialize device "Default"
But sound is working just fine.
Next I'm trying to find out why building goom is failing.
On my current setup I have a i3 4th GEN (1150) which I wouldn't mind using instead of replacing and I'd rather get a board which needs external 12 or 19 volt power as the case I use is very small and there is no room for internal PSU.
Are you aware of the picoPSU ? I'm using it with an J3455-ITX in a very small case. Works great!
I never tried it, but maybe you can map "System.Exec" to the power button. See here.
