Posts by Da Flex

I don't think LE has options to solve this. Can you change the HDMI cabling to NUC -> TV? That's my setup, too, with optical S/PDIF audio from TV to receiver.

Could you describe your HDMI cabling please?

If it's NUC -> receiver -> TV, then your new receiver might block (don't update) HDMI communication after suspend.

2019-11-29 12:31:15.857 T:2858812272   ERROR: ffmpeg[AA660370]: [matroska,webm] EBML header parsing failed
2019-11-29 12:31:15.857 T:2858812272   ERROR: Open - Error, could not open file smb://ben/mass2/Video/jaun.mkv
2019-11-29 12:31:15.857 T:2858812272   ERROR: ExtractThumb - Error creating demuxer

Maybe the source file has errors, and re-encoding it by ffmpeg fixes it. Go into analysis of the source file.

OK, if it's reproducable, then feel free to write a bug report.

Write step-by-step until you reach the bug, and provide all other necessary data.

I never had this bug on my RPi 3B+.

I don't think it's a bug. Most people simply forget to use root as their user name. Do ssh root@<YOUR_LIBREELEC_IP> from console.

I assume you haven't found any fitting add-on.

Some people run Java on LE, and then you could run jNut. Or use docker, which might be more efficient.

Untested, but try this variant:

#/bin/sh

IDLE_SHUTDOWN_ALLOWED_LAST_STATE=-1

while true
do
    KODI_RUNNING=`ps -A | grep kodi.bin | grep -v grep | wc -l`

    if [ 1 == $KODI_RUNNING ] ; then
        SSH_ACTIVE=`netstat -tnpa | grep 'tcp.*:22.*ESTABLISHED.*' | wc -l`
        NFS_ACTIVE=`netstat -tnpa | grep 'tcp.*:111.*ESTABLISHED.*' | wc -l`
        SMB_ACTIVE=`netstat -tnpa | grep 'tcp.*:445.*ESTABLISHED.*' | wc -l`  
        [ $SSH_ACTIVE -gt 0 -o $NFS_ACTIVE -gt 0 -o $SMB_ACTIVE -gt 0 ] && IDLE_SHUTDOWN_ALLOWED=1 || IDLE_SHUTDOWN_ALLOWED=0 

        if [ $IDLE_SHUTDOWN_ALLOWED_LAST_STATE != $IDLE_SHUTDOWN_ALLOWED ] ; then
            IDLE_SHUTDOWN_ALLOWED_LAST_STATE=$IDLE_SHUTDOWN_ALLOWED
            kodi-send --action="AllowIdleShutdown"
            if [ 0 == $IDLE_SHUTDOWN_ALLOWED ] ; then
                kodi-send --action="InhibitIdleShutdown(false)"
            else
                kodi-send --action="InhibitIdleShutdown(true)"
                IDLE_SHUTDOWN_ALLOWED_LAST_STATE=-1
            fi
        fi
    fi
    sleep 60
done

Sorry for my misunderstanding of virtualization technology and virtual machine.

Quote from robmcc83

Think I'll have a play with some bios settings for now see if anything changes.

Good idea. Check the audio options, too.

Quote from robmcc83

virtualization is what VM has something to do with which stands for virtual machine.

So you use a virtual machine to run LE. I don't use VM, but there is a chance that it does an encapsulation of hardware / software, which may lead to the "system mode" (see above).

I think LE programming will stay as close as possible on hardware level to get max. performance, so I don't expect a fix by update.

If you have more than one OS (LE + X), try Grub boot manager, and don't use VM for LE anymore.

Quote from robmcc83

Ive done a little research on these 2 and appears 1 is related to the amd vega 8 graphics that is built into my amd ryzen 3 2200g, and the other is related to VM.

What does VM mean, and which error triggers it?

As expected, you can try LE 9.2 now, and give feedback from there.

Quote from robmcc83

http://ix.io/22pj

Thx for testing. The above error is still there - could be a pulseaudio error then. You could play around with the audio output device settings.

PS: Both logs say, you're running LE in system mode:

Nov 25 10:36:31 LibreELEC pulseaudio[320]: W: [pulseaudio] main.c: Running in system mode, but --disallow-module-loading not set.
Nov 25 10:36:31 LibreELEC pulseaudio[320]: W: [pulseaudio] main.c: Home directory of user 'root' is not '/var/run/pulse', ignoring.
Nov 25 10:36:31 LibreELEC pulseaudio[320]: W: [pulseaudio] caps.c: Normally all extra capabilities would be dropped now, but that's impossible because PulseAudio was built without capabilities support.
Nov 25 10:36:31 LibreELEC pulseaudio[320]: W: [pulseaudio] main.c: OK, so you are running PA in system mode. Please make sure that you actually do want to do that.

Quote from robmcc83

I have a logitech Bluetooth dongle plugged into my computer, but I don't have any Bluetooth addon installed.

I use the Bluetooth dongle for ps3 controllers which work just fine without any modifications.

Sounds OK to me. In relation to your first screenshot ("Invalid Connector...") it could be a Bluetooth bug on LE 9.1.502.

You can try with disabled Bluetooth to check my theory.

It's probably not the right time to go into this issue too much, because I expect the LE release 9.1.503 or 9.2 every moment.

Quote

Code

Nov 25 10:36:31 ROBS-PC pulseaudio[320]: E: [pulseaudio] bluez5-util.c: GetManagedObjects() failed: org.freedesktop.DBus.Error.ServiceUnknown: The name org.bluez was not provided by any .service files

Do you have Bluetooth active, and / or any Bluetooth related add-ons installed?

It's hard to find the cause of unstable WiFi connections. If you don't want to take care about ANY WiFi driver issues, then try this idea from Iridium.

Quote from warrenjb

How do i confirm if my wifi adapter is supported and anyway to add support if it is not?

A complete compatibility list does not exist (you have to watch LE's Linux kernel for that).

When the product descriptions says Linux compatible, and it's not from Realtek, then give it a try.

Here is an incomplete list for OpenELEC on RPi, just to give a small overview: RPi USB Wi-Fi Adapters

Hint: An adapter with an antenna works better.

I did this at /storage/.kodi/userdata/keymaps/remote.xml to get the GUI context menu when pressing the blue remote control button:

<keymap>
  <global>
    <remote>
      <blue>ContextMenu</blue>
    </remote>
  </global>
</keymap>

Unfortunately it does not affect full screen mode. Maybe you can adapt it for your needs.

Looks like Dell is blocking max. performance at firmware level. Maybe max. performance leads to heat problems, or whatever issues.

The only "solution" I see is a firmware hack.