Posts by mglae


    For kodi_crash.log (symlink to kodi_crashlog_20170519182358.log): YXAJ
    For kodi_crashlog_20170519182231.log: CgdT

    Addon vizualization.wavforhue terminates Kodi:

    Code
    Thread 1 (Thread 0x74f84000 (LWP 1718)):
    #0  __GI_raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/raise.c:58
    #1  0x7538d400 in __GI_abort () at abort.c:89
    #2  0x66de229c in WavforHue::SaveState(std::string) () from /storage/.kodi/addons/visualization.wavforhue/visualization.wavforhue.so.1.0.0
    #3  0x66dee14c in WavforHue_Thread::GetPriorState() () from /storage/.kodi/addons/visualization.wavforhue/visualization.wavforhue.so.1.0.0
    #4  0x66ddf418 in Start () from /storage/.kodi/addons/visualization.wavforhue/visualization.wavforhue.so.1.0.0
    #5  0x007081c4 in ADDON::CVisualisation::Create(int, int, int, int, void*) ()


    Deinstalling the plugin should solve the crashes.

    Quote


    I wasn´t able to find out, why only some picons are in the list and some channels without the picons.
    Even I don´t understand the system of filenames like e.g. 1_0_1_1_1_9_5A0000_0_0_0.png to research for a solution.

    The file names are generated from the channel parameters: vdr-plugin-vnsiserver/vnsiclient.c at master · FernetMenta/vdr-plugin-vnsiserver · GitHub

    You can try geting the sources from GitHub - picons/picons-source and generating the picons from your VDR channels.conf. But be warned, I did need some tweaking to get all my DVB-C picons a few months ago.

    There seem to be issues with mpeg2 acceleration on Intel VAAPI.

    Try activating "Expert" Settings Level and disabling "Use MPEG-2 VAAPI" in "Player" - "Videos" settings.

    When still not working you can test disabling VAAPI acceleration completely.

    IMO you need to eliminate the kernel oops before examining any other errors.

    I can only guess the cause, but the first oops occurs directly after the failed ddbridge driver initialization ...

    Digital devices cards are supported with CvH's digital devices image. Give it a try.


    So that's another/different problem?
    Kodi is shutting down before a timer is getting set?

    Yes, according to your log kodi seems to be hanging on shutdown while/after disconnecting VNSI and is killed finally. This is behaviour by design of the LibreELEC kodi SIGTERM implementation.

    Kodi will even fail when going further and trying to set the timer because it cannot read its own settings any more.

    Quote


    Does setting a timestamp (using setwakeup.sh date '+%s' -d '+ 10 minutes') works on your system?
    I am getting an error but there is always a timer 5 minutes ahead.
    So could you try with 10 minutes pls?

    Busybox's "date" does not accept parameters like "+ 10 minutes". You have to use something like

    Code
    setwakeup.sh $(($(date +%s)+600))

    There is not the expected message

    Code
    DEBUG: CSettingsManager: requested setting (pvrpowermanagement.enabled) was not found.


    in your log because Kodi seems to be killed before exit completes.

    The functionality can be restored using this Kodi patch. I do create a bug report the next days so it can be fixed upstream.


    So here's what I did: 1) copy over the contents of /storage to the flash drive, 2) replace contents of cmdline.txt, and 3) reboot:

    Code
    # systemctl stop kodi
    # rsync -rtv /storage/ /var/media/TV-201702/
    # mount -o remount,rw /flash
    # nano /flash/cmdline.txt

    Unfortunately your rsync line does not copy all content, i.e. symlinks are skipped.

    I recommend wiping the USB disk and retry with

    Code
    rsync -a /storage/ /var/media/TV-201702/