[agb2]

1. When playing music from the FILE menu, I can not see the FANART. (When playing from the media library, the fanart is visible). In the official firmware this works.
2. Profiles are unstable, sometimes when the profile is switched, the system reboots. When choosing a profile, the response of the system is 10-15 seconds,  in the official version the response of the system instantly.

P13b.I have observed that in builds after #421 switching profiles always crashes LE.
At a guess this is related to the 'reuse python thread' changes.
I have reverted to #421.      

To try and pinpoint the problem, I cloned my installation to a fresh partition and renamed .kodi.
I then set the LE config to manually update from the Milhouse LE9 repo. and updated to #427.
I created 2 test profiles, added some media and tried logging on/switching profiles.
With all profiles using Estuary, this works fine.
I then installed Confluence and the common cache addon.
Profile test1 uses Confluence, Master and test2 use Estuary.

Switching to test1 crashed Kodi.
Crashlog here - http://ix.io/18Vp

Thread 1 (Thread 0x6cefc380 (LWP 1924)):
#0 0x00a6a3dc in CPythonInvoker::execute(std:tring const&, std::vector<std:tring, std::allocator<std:tring> > const&) ()
Hope this helps to identify the problem.
I will keep my main installation on #421 and test newer builds in the test installation.

I should add that this is all on a tweaked NOOBS setup, with several Kodi installations, each with their own 16GB partition on a 128GB SSD.
I will make one change to the test installation, as I noticed in the crashlog that it had become the 'master browser', which I do not want.

[agb2]

On a hunch, on the 'test' installation I disabled *in Master User* the addons I had installed - Confluence, common plugin cache and weather.yahoo.
Switching profiles no longer crashes Kodi.

In my main installation I went through all the installed service addons and skins and disabled *in Master user*.
Again, switching profiles no longer crashes Kodi, unless I go direct from profileX to profileY, when it does crash.
So to switch from profileX to profileY I logoff ProfileX, logon Master, logoff Master, logon profileY.

This is a workaround, rather than a solution, and is still a PITA.
It's arguable that switching profiles and crashing LE is as quick/quicker than the indirection above.

[Milhouse]

New LibreELEC.tv Leia build #0428: RPi / RPi2
(Supercedes previous build)

SHA256 Checksum: 253d3adc6b325586620db6ca677f1e275ea4079782d66bc6408840b0faea2efd (RPi)
SHA256 Checksum: d8ca61a7d1a3f1215d9b25617e3c502e22d92686cc537fbac24c5b7e26e1950b (RPi2)

text:
# uname -a

Linux rpi512 4.14.37 #1 Sat Apr 28 21:05:09 BST 2018 armv6l GNU/Linux



# vcgencmd version

Apr 26 2018 23:18:12 

Copyright © 2012 Broadcom

version 90a06d6c6299583cfbf40033bbf895a45920fa71 (clean) (release)



# lsb_release

LibreELEC (Milhouse): devel-20180428210313-#0428-g7b120c1 [Build #0428]



# Kodi version

(18.0-ALPHA2 Git:cd6c3fa). Platform: Linux ARM 32-bit

Based on tip of LibreELEC.tv master (7b120c1, changelog) and tip of XBMC master (94737c2, changelog) with the following modifications:

• Includes newclock5 patches
  
• Includes latest commits from kernel branch rpi-4.14.y
  
• Includes latest bcm2835-driver master (983b091)
  
• Includes latest kodi-platform master (e8574b8)
  
• Includes latest libcec master (8adc786, ahead +26)
  
• Includes latest libnfs master (8b064bf, ahead +125)
  
• Includes latest p8-platform master (a822e19)
  
• Includes latest addons: inputstream.adaptive (0f0ced4, +5), inputstream.rtmp (3b5058d), peripheral.joystick (80224e1), pvr.argustv (377f796), pvr.demo (d5e5cd1), pvr.dvblink (c61ea73), pvr.dvbviewer (3799782, +4), pvr.filmon (0ca1665), pvr.hdhomerun (484b91d), pvr.hts (9533cce), pvr.iptvsimple (77156cb), pvr.mediaportal.tvserver (9702684), pvr.mythtv (9d15025), pvr.nextpvr (de30ff2), pvr.njoy (bd6581f), pvr.octonet (54680a3), pvr.pctv (5e95300), pvr.stalker (da6f0f8), pvr.teleboy (a84e5ef), pvr.vbox (3cf15ad), pvr.vdr.vnsi (d6fe796), pvr.vuplus (00a963f), pvr.wmc (2acca13), pvr.zattoo (1244e14, +2), vfs.libarchive (e7d149e)
  
• Exclude [env] kodi-0100-temp-add-pr13594.patch: merged upstream
  
• Include [env] compare (perma): dmidecode: initial package
  
• Include [env] patch: RPi/RPi2: enable Broadcom WiFi debugging (see details)
  
• Include [env] patch: libcec: fix PR390
  
• Include [env] patch: libcec: don't link non-existant libtinfo
  
• Include [env] patch: rev hack for kodi
  
• Include [env] patch: HACK: Disable multiple PVR addons during migration. Always enable inputstream.* and os.*
  
• Include [env] patch: Add experimental splash video for RPi
  
• Include [env] patch: Bump included addon versions to prevent online updates
  
• Include [env] patch: Add kodi binary addons (pvr, adsp, inputstream, vfs, other)
  
• Include [env] PR:2449 (perma): Adding support for AMD GPUs
  
• Include [env] PR:2536 (perma): kodi: libinput fixes
  
• Include [env] PR:2572 (perma): update dvb addons
  
• Include [env] PR:2623 (perma): RPi, Generic: backport proposed patch to reduce IR latency
  
• Include [env] PR:2654 (perma): kodi: Early May 2018
  
• Include [env] PR:2666 (perma): retire DEVTOOLS
  
• Include [env] PR:2672 (perma): make: fix build against actual host glibc
  
• Include [pkg] patch: skin.estuary: reduce system info font size (kodi)
  
• Include [pkg] PR:13274 (perma): Mode whitelist
  
• Include [pkg] PR:13803 (perma): windowing: add overrides for UseLimitedColor for specific platforms
  
• Include [pkg] PR:13814 (perma): Reusepython
  

Build Highlights:

1. lirc: work around buggy client lib
   
2. [fix] save resume points on exit
   

Build Details:

1. LibreELEC.tv:
   • remove u-boot-tools package dependency for WC & WP (PR:2674, 3 commits, 8 files changed)
     
   • RPi: fix sha256 for firmware 983b091 (PR:2676, 1 commit, 2 files changed)
     
2. XBMC:
   • lirc: work around buggy client lib (PR:13823, 1 commit, 2 files changed)
     
   • [fix] save resume points on exit (PR:13822, 1 commit, 1 file changed)
     
3. Additional commits/pull requests/changes not yet merged upstream:
   • Updated: [env] PR:2572 (perma): update dvb addons
     

[Milhouse]

To try and pinpoint the problem, I cloned my installation to a fresh partition and renamed .kodi.
I then set the LE config to manually update from the Milhouse LE9 repo. and updated to #427.
I created 2 test profiles, added some media and tried logging on/switching profiles.
With all profiles using Estuary, this works fine.
I then installed Confluence and the common cache addon.
Profile test1 uses Confluence, Master and test2 use Estuary.

Switching to test1 crashed Kodi.
Crashlog here - http://ix.io/18Vp

Thread 1 (Thread 0x6cefc380 (LWP 1924)):
#0 0x00a6a3dc in CPythonInvoker::execute(std:tring const&, std::vector<std:tring, std::allocator<std:tring> > const&) ()
Hope this helps to identify the problem.
I will keep my main installation on #421 and test newer builds in the test installation.

I should add that this is all on a tweaked NOOBS setup, with several Kodi installations, each with their own 16GB partition on a 128GB SSD.
I will make one change to the test installation, as I noticed in the crashlog that it had become the 'master browser', which I do not want.

Thanks, yes - looks to be Python related. @peak3d any ideas?

[Milhouse]

1. When playing music from the FILE menu, I can not see the FANART. (When playing from the media library, the fanart is visible). In the official firmware this works.

Are you able to identify the first build with this issue?

Can you post an example directory listing (to show filenames etc.)?

I've created a fanart.jpg file in various Artist and Album folders but never see any fanart artwork and I went back as far as #0301 so either this isn't a recent issue, or I'm not able to reproduce.

[agb2]

To try and pinpoint the problem, I cloned my installation to a fresh partition and renamed .kodi.
I then set the LE config to manually update from the Milhouse LE9 repo. and updated to #427.
I created 2 test profiles, added some media and tried logging on/switching profiles.
With all profiles using Estuary, this works fine.
I then installed Confluence and the common cache addon.
Profile test1 uses Confluence, Master and test2 use Estuary.

Switching to test1 crashed Kodi.
Crashlog here - http://ix.io/18Vp

Thread 1 (Thread 0x6cefc380 (LWP 1924)):
#0 0x00a6a3dc in CPythonInvoker::execute(std:tring const&, std::vector<std:tring, std::allocator<std:tring> > const&) ()
Hope this helps to identify the problem.
I will keep my main installation on #421 and test newer builds in the test installation.

I should add that this is all on a tweaked NOOBS setup, with several Kodi installations, each with their own 16GB partition on a 128GB SSD.
I will make one change to the test installation, as I noticed in the crashlog that it had become the 'master browser', which I do not want.

Thanks, yes - looks to be Python related. @peak3d any ideas?  

Circumstantial evidence would suggest that among the criteria for attempting to reuse a python addon/invoker/thread etc. should be whether
the skin has changed.

[beamdream]

Hello
Since the build 2104 the skin Aeon Nox Silvo is no more supportet. It crash when going into the createt menu.

Thanks

[beamdream]

I createt a second sd card with the same build and updated to build 2804 and compared to my working build 2004. I tested every build since 2104 and had the same problem in each build with skin aeon nox silvo. Don't know if it is a issue Kodi or aeon nox silvo.

thanks

[Aux_]

Hello
Since the build 2104 the skin Aeon Nox Silvo is no more supportet. It crash when going into the createt menu.

Thanks

 Read post 1 "Skin Usage"...

[brunis]

A few comments, not specifically related to latest and greatest build.

1. Browsing movies, leaves the previously cached background image visible until a new one is fetched for the actively hoverede movie. I'm sure if you have a fast connection and live near imdb.com's servers you'll never see this. But i'm in Africa on 10 mbit. So if you could clear and show a blank background when you change title hover, until you fetched the new one?
2. Will some of the old more underlying issues ever be fixed? Like, will we ever see a hardware pointer? Will we ever move to other rendering form that doesn't suck the life out of a device like the Pi? I'm not assuming anyone will write a full vulkan driver for the Pi's chipset, but i'm still dreaming.
3. After all these package updates, i think a few new default settings are in order. Like adding a default samba user, so it doesn't have to be an "expert" setting just to be able to browse your movie library. Same goes for your gigantic default overscan, it makes every side of the screen unreadable on every screen i ever used Kodi on. How about making it a bit smaller, so it'll fit by default and then leave it to the experts to expand it? Yes, the overscan setting is actually called video "calibration".

Hoping you'll consider some of these fixes/suggestions.

[tjost]

crashlog

I'm sorry but its getting worse with the builds.
1. the safety boot is crap. it resets all the settings this is terrible.
2. live tv problem. after switching channel it going to normal video player. I have to stop the video and start live tv again.
    also stuttering and lags of the live-tv.
it reboots and without any reason and switch on my television in the middle of the night. I´m doing nothing.
please support sleep mode and the usage of pin.3 to wake up the pi again. this would be the best way to prevent these error.

[RappaSan]

By the way: Is it possible to view Live-TV with Chorus2?
I can't find anything about that.

[Milhouse]

I createt a second sd card with the same build and updated to build 2804 and compared to my working build 2004. I tested every build since 2104 and had the same problem in each build with skin aeon nox silvo. Don't know if it is a issue Kodi or aeon nox silvo.

thanks

@beamdream please try and use standard build codes (#0428, #0420, #0421 etc.) - just makes your posts easier to comprehend.

Also, try and reproduce the problem with stock Estuary.

[Milhouse]

1. the safety boot is crap. it resets all the settings this is terrible.

Yep, that's by design - a setting might be the cause of the original boot loop that has now triggered Safety Mode.

Safety Mode does at least allow you to enable ssh/samba if you hadn't already, upload crash logs from the failing installation, get advice, fix the issue etc. It's not intended as a mode in which you would watch movies - it's so you can resolve the crash loop.

Your original crashing installation will be restored on the next reboot when it will most likely continue to crash loop unless you have fixed the underlying issue.

If you don't find Safety Mode useful and would prefer the blackness that results from a crash loop then you can disable Safety Mode entirely with touch /storage/.config/safemode.disable.

2. live tv problem. after switching channel it going to normal video player. I have to stop the video and start live tv again.
    also stuttering and lags of the live-tv.

Does removing the banned addons help? Try a clean install without the banned add-ons and repositories.

[tjost]

1. the safety boot is crap. it resets all the settings this is terrible.

Yep, that's by design - a setting might be the cause of the original boot loop that has now triggered Safety Mode.

Safety Mode does at least allow you to enable ssh/samba if you hadn't already, upload crash logs from the failing installation, get advice, fix the issue etc. It's not intended as a mode in which you would watch movies - it's so you can resolve the crash loop.

Your original crashing installation will be restored on the next reboot when it will most likely continue to crash loop unless you have fixed the underlying issue.

If you don't find Safety Mode useful and would prefer the blackness that results from a crash loop then you can disable Safety Mode entirely with touch /storage/.config/safemode.disable.

2. live tv problem. after switching channel it going to normal video player. I have to stop the video and start live tv again.
    also stuttering and lags of the live-tv.

Does removing the banned addons help? Try a clean install without the banned add-ons and repositories. 

 i have. but it worked with the add-ons before. 
After reboot out off safety boot the settings still reset. I have to enable German, with timezone, my skin, my audio settings aswell. 
What about the insecure repository. It is my own homepage and plug ins from your website as well. What can I do to my Homepage.