(2017-06-14, 15:32)kkoa Wrote: [ -> ]Addon settings do not work at all anymore. It doesn't show anything.
I guess this is due to the settings refactor. How can this be fixed and shouldn't it be at least backwards compatible?
This is what it looks like for all addons: https://www2.pic-upload.de/img/33335681/...hot001.png
(2017-06-15, 00:38)Milhouse Wrote: [ -> ]CEC Adapter settings have been broken since #0609, specifically because of PR12276 - revert this PR and the settings are visible again. I guess this is one for @Montellese, or maybe @opdenkamp.
Is this related? I first noticed it on #606 but not on #531
(2017-06-15, 01:05)kkoa Wrote: [ -> ][quote='kkoa' pid='2603153' dateline='1497447155']
Is this related? I first noticed it on #606 but not on #531
Quite possibly, quite possibly.
(2017-06-15, 01:08)Milhouse Wrote: [ -> ] (2017-06-15, 01:05)kkoa Wrote: [ -> ][quote='kkoa' pid='2603153' dateline='1497447155']
Is this related? I first noticed it on #606 but not on #531
Quite possibly, quite possibly.
Because you mentioned it being like this since 609 which would not be the case then as I noticed it 3 builds before already.
Are you aware of any fix being in progress? Do the devs even know about this?
(2017-06-15, 01:10)kkoa Wrote: [ -> ]Because you mentioned it being like this since 609 which would not be the case then as I noticed it 3 builds before already.
I'm only saying the CEC Settings (based on my testing) is first broken first with #0609 - the CEC Settings are visible in in #0608, but not visible in #0609.
I don't use PVR addons, so I'm not testing those, but if they're broken then it probably all stems from the same settings refactor introduced in #0604.
(2017-06-15, 01:10)kkoa Wrote: [ -> ]Are you aware of any fix being in progress? Do the devs even know about this?
No. And I'm not reporting these issues either - been there, done that, not worth the hassle.
If the developers are reading this thread they'll know about the problem, if not that's too bad. Feel free to open a trac ticket.
(2017-06-15, 01:15)Milhouse Wrote: [ -> ] (2017-06-15, 01:10)kkoa Wrote: [ -> ]Because you mentioned it being like this since 609 which would not be the case then as I noticed it 3 builds before already.
I'm only saying the CEC Settings (based on my testing) is first broken first with #0609 - the CEC Settings are visible in in #0608, but not visible in #0609.
I don't use PVR addons, so I'm not testing those, but if they're broken then it probably all stems from the same settings refactor introduced in #0604.
PVR was just an example. Unfortunately it is with all addons, no matter if binary or non-binary.
Also bundled addons like Joystick Support and AAC encoder.
(2017-06-15, 01:32)trogggy Wrote: [ -> ] (2017-06-15, 01:18)kkoa Wrote: [ -> ] (2017-06-15, 01:15)Milhouse Wrote: [ -> ]I'm only saying the CEC Settings (based on my testing) is first broken first with #0609 - the CEC Settings are visible in in #0608, but not visible in #0609.
I don't use PVR addons, so I'm not testing those, but if they're broken then it probably all stems from the same settings refactor introduced in #0604.
PVR was just an example. Unfortunately it is with all addons, no matter if binary or non-binary.
Also bundled addons like Joystick Support and AAC encoder.
I'm guessing it's this.
Oh yeah guess it's due to my custom Estuary then. Thanks for pointing that out.
// EDIT: Still the same even with stock Estuary.
// EDIT 2: Ok it is working though not for all addons.
02:28:22.504 T:1943056400 ERROR: CAddon[plugin.video.a]: failed to load addon settings from special://profile/addon_data/plugin.video.a/settings.xml
(2017-06-15, 02:28)trogggy Wrote: [ -> ] (2017-06-15, 02:04)kkoa Wrote: [ -> ]// EDIT: Still the same even with stock Estuary.
Confluence ftw. 
I like Estuary more
When the XML tag starts with a number, Kodi is unable to load the settings.xml. Probably non-standard XML though it was supported before and maybe should be now.
<1abc></1abc>
After some time i did an update yesterday to #0614 and ran into a Bootloop.
I cannot remember from what version i was updating but after some downdating it seems that #0529 was the last working one for me
without Bootloop.
Looked into the crashlog and got an error like kkoa:
Code:
20:27:14.241 T:1651544992 ERROR: CAddon[plugin.video.youtube]: failed to load addon settings from special://profile/addon_data/plugin.video.youtube/settings.xml
here is the whole crashlog:
https://pastebin.com/TRBB3dyd
@
Puschl that's a crashlog from #0612. You could try #0614 and see if that's any better, or go back to #0603 for now, which should work without too many issues.
(2017-06-15, 12:04)Milhouse Wrote: [ -> ]@Puschl that's a crashlog from #0612. You could try #0614 and see if that's any better, or go back to #0603 for now, which should work without too many issues.
Hi Milhouse,
tried the #0614 and still got the reboot issue.
after the CEC adapter initialise the screen freezes and went straight to the Libreelec Bootlogo.
Last working version for me was #0526 which i will upload now so the wife is happy
btw here is the crashlog:
https://pastebin.com/HcZEHa7f
Sidequestion: what is Indigo? After going back to #0526 the popup says it has never started and i should look into the logfile (which i didnt yet)
Greets
New LibreELEC.tv Leia build #0615:
RPi /
RPi2
(Supercedes previous build)
Code:
# uname -a
Linux rpi512 4.11.5 #1 Thu Jun 15 21:54:35 BST 2017 armv6l GNU/Linux
# vcgencmd version
Jun 13 2017 14:53:44
Copyright (c) 2012 Broadcom
version 22340f772ce101854acbc46045358dae832dd513 (tainted) (release)
# lsb_release
LibreELEC (Milhouse) - Version: devel-20170615215249-#0615-gd5801af [Build #0615]
# Kodi version
(18.0-ALPHA1 Git:423072a). Platform: Linux ARM 32-bit
Based on tip of
LibreELEC.tv master (d5801af0,
changelog) and tip of
XBMC master (d7ea2b0b,
changelog) with the following modifications:
- Includes newclock5 patches
- Excludes the LibreELEC linux-01-RPi_support patch in favour of sourcing these and possibly more recent patches directly from kernel branch rpi-4.11.y
- Includes latest bcm2835-driver master (0ab90562, ahead +3)
- Includes latest kodi-platform master (36fb4937)
- Includes latest libcec master (3953f8dc, ahead +12)
- Includes latest libnfs master (128ac2f7, ahead +97)
- Includes latest p8-platform master (2d90f986)
- Includes latest addons: inputstream.adaptive (f1f5539d), inputstream.rtmp (d93d32d4), peripheral.joystick (6764788e), pvr.argustv (b281e04f), pvr.demo (ffee02b8), pvr.dvblink (6d42eae1), pvr.dvbviewer (8078aae7), pvr.filmon (300c595e), pvr.hdhomerun (9073b99b), pvr.hts (090c3195), pvr.iptvsimple (dbf6011e), pvr.mediaportal.tvserver (07d73f3a), pvr.mythtv (f2da22ca), pvr.nextpvr (239dbef3), pvr.njoy (4785afd2), pvr.octonet (9bbd7cf3), pvr.pctv (f61e2541), pvr.stalker (151e3d3f), pvr.vbox (df9efea4), pvr.vdr.vnsi (40dc17d0), pvr.vuplus (83a729ea), pvr.wmc (93cebfc7), vfs.rar (4ce78b0f)
- Include [env] compare: kodi18a1 latest updates
- Include [env] compare: linux: update to linux-4.11.5
- Include [env] patch: Bump included addon versions to prevent online updates
- Include [env] patch: Add experimental splash video for RPi
- Include [env] patch: HACK: Disable multiple PVR addons during migration. Always enable inputstream.* and os.*
- Include [env] patch: Add kodi binary addons (pvr, adsp, inputstream, vfs, other)
- Include [env] patch: busybox: SH is none
- Include [env] PR:1469: samba: update to samba-4.6.4
- Include [env] PR:1690: Enable -fPIC for some packages
- Include [env] PR:1693: minor package bumps
- Include [env] PR:1694: busybox: update to 1.26.2
- Include [pkg] PR:67: Revert "Revert "change smbd and nmbd location"" (service.libreelec.settings)
- Include [pkg] PR:352: Fix: set wrong variable (libcec)
- Include [pkg] PR:12110: smbclient: cleanup smbclient configuration
- Include [pkg] PR:12281: [network] CHTTPJsonRpcHandler: limit any other request method than POST to ReadData permissions on the JSON-RPC API
- Include [pkg] PR:12300: [GUI] Prevent parse step of VisibleConditions if expression is already?
- Revert [pkg] PR:11954: [bluray][win32] Update libbluray (reason: needs newclock5 rebase)
Build Highlights:
- New 4.11.5 kernel
- Bump ffmpeg-3.3.2-Leia-Alpha (in Kodi18a1 patch set)
- Enable -fPIC for some packages
- Update busybox, alsa
Build Details:
- LibreELEC.tv:
- add some missing dependencies (PR:1668, 2 commits, 2 files changed)
- chromium-addon: libva-vdpau-driver libraries, now under /usr/lib/dri instea… (PR:1683, 1 commit, 1 file changed)
- Correcting VendorID for TP-Link T4U v2 (PR:1682, 1 commit, 1 file changed)
- XBMC:
- [Python] Fix xbmcgui.Window methods to get the actual size of a Window (PR:12279, 3 commits, 4 files changed)
- [screensaver] fix wrongly removed call (PR:12302, 1 commit, 1 file changed)
- [bluray][win32] Update libbluray (PR:11954, 10 commits, 15 files changed)
- Additional commits/pull requests/changes not yet merged upstream:
- Added: [env] compare: linux: update to linux-4.11.5
- Added: [env] patch: busybox: SH is none
- Added: [env] PR:1690: Enable -fPIC for some packages
- Added: [env] PR:1693: minor package bumps
- Added: [env] PR:1694: busybox: update to 1.26.2
- Reverted: [pkg] PR:11954: [bluray][win32] Update libbluray (reason: needs newclock5 rebase)
(2017-04-09, 21:17)Milhouse Wrote: [ -> ] (2017-04-09, 17:31)mikeb8591 Wrote: [ -> ]in build #0403 this change
estuary fix watched status for videos (PR:11921, 1 commit, 1 file changed)
was listed. Since that build, all my unwatched recordings show a check mark, (which previously only showed after a recording was watched)
a partially watched video still shows a half-light/half-dark circle, but instead of folders (for series) and squares (for individual recordings) all my recordings show a check mark.
Is this correct? I'm using the NextPVR client, in case that makes a difference.
That particular change, PR11921, was first included as an umerged change in build #0330.
If you are sure the problem is first seen with build #0403 then it's unlikely PR11921 is the source of this problem.
I finally had a chance to check this on a windows kodi 18-alpha build (0604) and found that the behavior is correct there. It's running 3.0.4 of the pvr.nextpvr plugin, and PI builds are running 999.3.0.4 for what that's worth.
This is really kind of annoying. I did trace it down to a build where it started, even if I called out a change that was unlikely to be the problem.
Are other pvr clients seeing this issue, or just nextpvr?
Thanks!
@
mikeb8591 can you provide a screenshot of how it looks in RPi #0615 and #0402, so that we can see the difference? I'll upload a build of #0403 with a PR reverted which might be useful to test.