Posts by mglae

From the technical view the sound device is closed in Kodi and opened in Chrome.

To control the volume in Chrome install and test one of the Chrome Sound/Volume Apps.

Untested:

#!/bin/sh

WATCH_PROCS="chrome"

watched_procs() {
  for p in $WATCH_PROCS; do
    pidof $p >/dev/null && return 0
  done
  return 1
}

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 ] || watched_procs ) && 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)"
        fi
      fi
  fi
  sleep 60
done

Fixed in kodi, not yet included into LE.

Somewhere down the line iw moved to the image. Just type iw.

Console access: Log Files - LibreELEC.wiki

Nightly addons are available on Index of /addons

Apr 11 16:28:36 LibreELEC fsck: /dev/mmcblk0p1: 220 files, 18484/65501 clusters
Apr 11 16:28:36 LibreELEC fsck: STORAGE: clean, 1228/8192 files, 32113/32768 blocks

chewitt STORAGE is not expanded. But I have no experience what is best practice to do it manually on RPI4.

You may have to manually update your binary addons from Index of /addons/9.80.9

You may have to look for beta addon version for Matrix that need to be installed manually.

It's a pulseaudio bug:

bluealsa: Unsupported RTP payload type: 1 · Issue #13 · Arkq/bluez-alsa · GitHub

RTP payload type: 1 (#591) · Issues · PulseAudio / pulseaudio · GitLab

bluez5-device: use correct RTP payload type (!48) · Merge Requests · PulseAudio / pulseaudio · GitLab

Assuming you are using LE 9.2.6 this should be fixed in LE 10 nightlies.

From MySQL/Advanced notes - Official Kodi Wiki

Quote

Kodi also supports using MySQL for PVR (tvdatabase and epgdatabase) as well as the ADSP database. However, there is little to no practical benefit to using MySQL for those databases, and there has been very little testing with them (expect bugs!). Unless you simply want to experiment, or have a very specific need, you should avoid using MySQL for PVR and ADSP.

There are only a few tools available in initramfs i.e dmesg to look for errors or ping to check network configuration.

Most likely the iscsi parameters are not correct.

Remove all quotes.

With "tarfile" of Python3 the tar format changed from POSIX 1003.1-1988/ustar to POSIX 1003.1-2001/pax.

Update your tool or choose another.

In addition pure wireguard can be used: RE: wireguard troubleshooting : no reply

It's again the same ffmpeg error message:

2021-01-30 22:48:57.397 T:938     ERROR <general>: ffmpeg[0x320be90X]: [h264] get_buffer() failed
2021-01-30 22:48:57.397 T:938     ERROR <general>: ffmpeg[0x320be90X]: [h264] thread_get_buffer() failed
2021-01-30 22:48:57.397 T:938     ERROR <general>: ffmpeg[0x320be90X]: [h264] decode_slice_header error
2021-01-30 22:48:57.397 T:938     ERROR <general>: ffmpeg[0x320be90X]: [h264] no frame!

I have no idea which component fails on the broken video stream. You can try to open a kodi issue on github.

Wireguard - changes the default route although not configured

Quote from JoeAverage

- pastecrash didn't work (no link returned) -

Unfortunately ix.io silently fail if the file is too long. Use

 pastecrash -c >~/crashlog_$(date -Iseconds).log

and post the file manually.

Regarding the VAAPI decoder errors you can try the older intel driver by creating:

MESA_LOADER_DRIVER_OVERRIDE=i965
LIBVA_DRIVER_NAME=i965