•   
  • 1
  • 55
  • 56
  • 57(current)
  • 58
  • 59
  • 86
  •   
v19 LibreELEC Testbuilds for RaspberryPi (Kodi 19.0)
(2020-03-13, 07:24)Milhouse Wrote:
(2020-03-13, 06:28)bill_orange Wrote:
(2020-03-12, 23:23)Milhouse Wrote: Yes - those are not crash logs, you should have at least one crash log in /storage/.kodi/temp - try uploading the latest zip from the Logfiles samba share as that should include all the crash logs. 
Okay here you go: https://1drv.ms/u/s!AmXKqAwyCrbxiN1I8hvl...A?e=zWP0Is 

Thanks. Your zip contains only 3 crash logs (we retain the 10 most recent crash logs) which makes me wonder where the rest are - or maybe kodi isn't crashing when the CEC source is changed?

2 of the crash logs are from 8 March (based on #0306) and show "normal" crashes on Kodi shutdown, while the remaining crash log is from 4 March (based on #0225) and seems to crash at 06:18 in the morning: http://ix.io/2e66 - there's not a huge amount of detail in the traces, unfortunately.

In your original post you showed a log extract with date 2020-03-06 but there's no corresponding crash log for this period - did you upload all the crash logs? If you did, then it doesn't look like kodi is crashing - one other possibility is that it's being killed by the out of memory process killer as this doesn't leave a tell-tale crash log, and the details would be in the system log (journalctl -a | pastebinit). 
There were two or three other crash logs but they were from early February. The crash occurs nearly every day. On the next spontaneous reboot (crash?), I will collect the system log.  I was suspicious of the SD card before.  Its very old. I am really suspicious now.
Reply
Last night I tried to update from #305 to #312.  It downloaded and rebooted and upgraded.  Then the screen went black.  I know there was a firmware update, so I let it go for 15 minutes.  Then I pulled the power and tried again and still just a black screen.  If I plug the SD card into my mac, I can see the files, so I know it's not that the SD card went bad.  Is there a way to recover from this?
Reply
(2020-03-13, 15:14)quig Wrote: Last night I tried to update from #305 to #312.  It downloaded and rebooted and upgraded.  Then the screen went black.  I know there was a firmware update, so I let it go for 15 minutes.  Then I pulled the power and tried again and still just a black screen.  If I plug the SD card into my mac, I can see the files, so I know it's not that the SD card went bad.  Is there a way to recover from this?
Can you describe your setup? Model of Pi. Any hardware connected? Ethernet or wifi? Any custom settings in config.tx (like overclock)?
Reply
(2020-03-13, 16:10)popcornmix Wrote:
(2020-03-13, 15:14)quig Wrote: Last night I tried to update from #305 to #312.  It downloaded and rebooted and upgraded.  Then the screen went black.  I know there was a firmware update, so I let it go for 15 minutes.  Then I pulled the power and tried again and still just a black screen.  If I plug the SD card into my mac, I can see the files, so I know it's not that the SD card went bad.  Is there a way to recover from this?
Can you describe your setup? Model of Pi. Any hardware connected? Ethernet or wifi? Any custom settings in config.tx (like overclock)?   
Pi 3B+ with a RemotePi board using Ethernet.  config.txt
Reply
New LibreELEC.tv Matrix build #0313: RPi / RPi2
(Supercedes previous build)

SHA256 Checksum: b73c2dc348624c6a6b96f11ca11483b2f4941d7a4fda60899e68eaf4ef1db7c5 (RPi)
SHA256 Checksum: a1c1a3e1126665e4e7ed9b76e37119dc83cb6cdc561581ebc506fbbcefc03c99 (RPi2)

# uname -a
Linux rpi512 5.4.24 #1 Fri Mar 13 21:04:12 GMT 2020 armv6l GNU/Linux

# vcgencmd version
Mar 10 2020 18:38:51
Copyright © 2012 Broadcom
version 74d7f53b091e465285f38fb96896a8fc328e4c47 (clean) (release) (raspberrypi_full_legacy)

# lsb_release
LibreELEC (Milhouse): devel-20200313210330-#0313-g396788e [Build #0313]

# Kodi version
Kodi (19.0-ALPHA1 Git:53978dc). Platform: Linux ARM 32-bit

Based on tip of LibreELEC.tv master (396788e, changelog) and tip of XBMC master (53978dc, changelog) with the following modifications: Build Highlights:
  1. systemd: add RemainAfterExit=yes to our oneshot systemd services
  2. Implement range check in URIUtils::resolvePath
Build Details:
  1. LibreELEC.tv:
    • update_binary-addons: drop kodi-platform bump (PR:4259, 1 commit, 1 file changed)
    • Allwinner: Add support for H5 (PR:4253, 3 commits, 11 files changed)
  2. XBMC:
    • AESinkAUDIOTRACK: Allow RAW and IEC distinguishing (PR:17133, 2 commits, 2 files changed)
    • Android: Skip HW acceleration if not needed (PR:17121, 1 commit, 1 file changed)
  3. pvr.sledovanitv.cz:
    • src: Refactor types and file names (506f23d)
    • git: Remove .gitignore (e30be82)
    • addon: Do better logging (2686240)
    • Data: Trigger updates only if needed (e5e3f8e)
    • Data: Check "radio" flag for groups (c830d49)
    • Add option for overriding product (b09f351)
    • ApiManager: Delete old pairing if existed (403ab36)
    • ApiManager: Add User-Agent specification (6f0c920)
    • ApiManager: Use correct parameters (0e45171)
    • Increase version 2.4.0 (b06fdc5)
    • ApiManager: Add (needed?) request parameters (846f58f)
    • Round getting EPG to midnight (03f0bf1)
    • Increase version 2.4.1 (3e790ca)
    • Data: Fix build when time_t<==>unsigned (528d386)
  4. kernel 5.4.y:
    • New commits in this build:
      • Kbuild: Allow .dtbo overlays to be built, adjust. (61113c54)
      • media: ov5647: Fix return codes from ov5647_write/ov5647_read functions. (23f71716)
      • media: ov5647: Add basic support for multiple sensor modes. (9e584d9d)
      • media: ov5647: Add V4L2 controls for analogue gain, exposure and AWB (d9d333b7)
      • media: ov5647: Add extra 10-bit sensor modes. (28c0004a)
      • media: ov5647: change defaults to better match raw camera applications. (8bc19bae)
      • drm/vc4: fkms: Change crtc_state structure name to avoid conflict (c0b2ca6a)
      • drm/fourcc: Add packed 10bit YUV 4:2:0 format (0d392a43)
      • drm/vc4: Add DRM_FORMAT_P030 support to firmware-kms (531d3d5c)
  5. Additional commits/pull requests/changes not yet merged upstream:
    • Updated: [env] PR:4237 (perma): linux (Generic/Allwinner): update to linux-5.5.13
    • Updated: [env] PR:4255 (perma): kodi: next update (end of March 2020?)
    • Added: [env] PR:4261 (perma): add RemainAfterExit=yes to our oneshot systemd services
    • Added: [pkg] PR:17492 (perma): Implement range check in URIUtils::resolvePath
Texture Cache Maintenance Utility: Preload your texture cache for optimal UI performance. Remotely manage media libraries. Purge unused artwork to free up space. Find missing media. Configurable QA check to highlight metadata issues. Aid in diagnosis of library and cache related problems.
Reply
(2020-03-13, 15:04)bill_orange Wrote:
(2020-03-13, 07:24)Milhouse Wrote:
(2020-03-13, 06:28)bill_orange Wrote: Okay here you go: https://1drv.ms/u/s!AmXKqAwyCrbxiN1I8hvl...A?e=zWP0Is 

Thanks. Your zip contains only 3 crash logs (we retain the 10 most recent crash logs) which makes me wonder where the rest are - or maybe kodi isn't crashing when the CEC source is changed?

2 of the crash logs are from 8 March (based on #0306) and show "normal" crashes on Kodi shutdown, while the remaining crash log is from 4 March (based on #0225) and seems to crash at 06:18 in the morning: http://ix.io/2e66 - there's not a huge amount of detail in the traces, unfortunately.

In your original post you showed a log extract with date 2020-03-06 but there's no corresponding crash log for this period - did you upload all the crash logs? If you did, then it doesn't look like kodi is crashing - one other possibility is that it's being killed by the out of memory process killer as this doesn't leave a tell-tale crash log, and the details would be in the system log (journalctl -a | pastebinit).  
There were two or three other crash logs but they were from early February. The crash occurs nearly every day. On the next spontaneous reboot (crash?), I will collect the system log.  I was suspicious of the SD card before.  Its very old. I am really suspicious now. 
Here is the system log from journalctl -a 

https://1drv.ms/u/s!AmXKqAwyCrbxiN1N2HMJ...w?e=gKQcq2
Reply
(2020-03-12, 23:36)Milhouse Wrote:
(2020-03-12, 22:16)dantist Wrote:  
Yes, in LE10 (ie. these nightlies) we use zstd compression for the squashfs SYSTEM image, but LE 8.x (and earlier) doesn't support zstd decompression so it's not able to mount the zstd compressed SYSTEM image from LE10.

The trick is to upgrade from LE8.x (or earlier) _via_ LE 9.x as the LE9.x kernel supports zstd decompression (but the LE9 SYSTEM image doesn't *use* zstd compression). Once you're on LE 9.x you can then upgrade to LE10 (ie. these nightly test builds).

Alternatively you can write the 9.2.1 img.gz to your SD card, and then you can upgrade directly to these "LE10" nightly test builds.       

I installed 9.2.1 and upgraded to the latest nightly, but almost nothing is working now. I cannot install skins, e.g.:
Quote:ERROR: CAddonInstallJob[skin.unity]: Die Abhängigkeit auf script.skinshortcuts in Version 1.0.8 konnte nicht aufgelöst werden.

or addons, like netflix:
Quote: ERROR: CAddonInstallJob[plugin.video.netflix]: Die Abhängigkeit auf xbmc.python in Version 2.26.0 konnte nicht aufgelöst werden.

The YouTube addon could be installed but isn't working:
Quote:2020-03-14 15:58:31.296 T:588   ERROR: Control 55 in window 10025 has been asked to focus, but it can't
2020-03-14 15:58:31.352 T:1848  NOTICE: [plugin.video.youtube] Running: YouTube (6.6.0.1) on Krypton (Kodi-19.0) with Python 3.7.6
                                                Path: /
                                                Params: {}
2020-03-14 15:58:32.617 T:1848  NOTICE: [plugin.video.youtube] Running: YouTube (6.6.0.1) on Krypton (Kodi-19.0) with Python 3.7.6
                                                Path: /special/popular_right_now/
                                                Params: {}
2020-03-14 15:58:32.851 T:1848   ERROR: [plugin.video.youtube] Error reason: |accessNotConfigured| with message: |Project 294899064488 has been scheduled for deletion and cannot be used for API calls. Visit https://console.developers.google.>
2020-03-14 15:58:32.853 T:1984   ERROR: GetDirectory - Error getting plugin://plugin.video.youtube/special/popular_right_now/
2020-03-14 15:58:32.856 T:588   ERROR: CGUIMediaWindow::GetDirectory(plugin://plugin.video.youtube/special/popular_right_now/) failed
2020-03-14 15:58:32.862 T:1848  NOTICE: [plugin.video.youtube] Running: YouTube (6.6.0.1) on Krypton (Kodi-19.0) with Python 3.7.6
                                                Path: /
                                                Params: {}
 

What did I do wrong?
Reply
(2020-03-14, 18:00)dantist Wrote: What did I do wrong?

Unfortunately since #0301 the Python ABI changed to 3.0.0, which means addons must now support this new version. If they don't then they can't be installed. Frustratingly, if a script dependency of an 3.0.0-compatible add-on doesn't yet support 3.0.0 then the add-on still won't install.

So it's a waiting game until add-ons update to 3.0.0.

You could go back to #0229 (the last non-3.0.0 Kodi 19 build) but as add-ons and scripts update to 3.0.0 in the Matrix repo, you'll not be able to use the updated add-ons.

It's going to be a mess for some time yet. Sad

(2020-03-14, 18:00)dantist Wrote: The YouTube addon could be installed but isn't working:

For you tube - this is unrelated to any recent Python changes. The API key used by the YouTube add-on has been abused by other developers/addons, so now you need to configure YouTube with a personal API key: https://forum.kodi.tv/showthread.php?pid...pid2681560
Texture Cache Maintenance Utility: Preload your texture cache for optimal UI performance. Remotely manage media libraries. Purge unused artwork to free up space. Find missing media. Configurable QA check to highlight metadata issues. Aid in diagnosis of library and cache related problems.
Reply
New LibreELEC.tv Matrix build #0314: RPi / RPi2
(Supercedes previous build)

SHA256 Checksum: 912b8d46ad7993c18e1d00160df65495f1d480c3e36b024915092e01c2e3eb16 (RPi)
SHA256 Checksum: 61d9959f9ccf5c83851fac59877a492e236250f3fcdc612049c7c675930d5d9b (RPi2)

# uname -a
Linux rpi512 5.4.24 #1 Sat Mar 14 21:04:15 GMT 2020 armv6l GNU/Linux

# vcgencmd version
Mar 10 2020 18:38:51
Copyright © 2012 Broadcom
version 74d7f53b091e465285f38fb96896a8fc328e4c47 (clean) (release) (raspberrypi_full_legacy)

# lsb_release
LibreELEC (Milhouse): devel-20200314210330-#0314-g6c08564 [Build #0314]

# Kodi version
Kodi (19.0-ALPHA1 Git:8d8e164). Platform: Linux ARM 32-bit

Based on tip of LibreELEC.tv master (6c08564, changelog) and tip of XBMC master (8d8e164, changelog) with the following modifications: Build Highlights:
  1. Minors
Build Details:
  1. LibreELEC.tv:
    • apache-ant: update to apache-ant-1.10.7 (PR:4263, 1 commit, 1 file changed)
  2. XBMC:
    • Android: Don't reset user set volume (PR:17241, 1 commit, 1 file changed)
    • Revert "AESinkAudioTrack: Support multi channel float" (PR:17463, 1 commit, 2 files changed)
    • PVR documentation change for specials (PR:17486, 1 commit, 2 files changed)
    • [addons][videocodec] add documentation to STREAMCODEC_PROFILE (PR:17462, 1 commit, 1 file changed)
    • [addons] fix stupid circumstance with addon settings on folder with file extension (PR:17449, 1 commit, 1 file changed)
Texture Cache Maintenance Utility: Preload your texture cache for optimal UI performance. Remotely manage media libraries. Purge unused artwork to free up space. Find missing media. Configurable QA check to highlight metadata issues. Aid in diagnosis of library and cache related problems.
Reply
(2020-03-14, 20:20)Milhouse Wrote:
(2020-03-14, 18:00)dantist Wrote: What did I do wrong?

Unfortunately since #0301 the Python ABI changed to 3.0.0, which means addons must now support this new version. If they don't then they can't be installed. Frustratingly, if a script dependency of an 3.0.0-compatible add-on doesn't yet support 3.0.0 then the add-on still won't install.

So it's a waiting game until add-ons update to 3.0.0.

You could go back to #0229 (the last non-3.0.0 Kodi 19 build) but as add-ons and scripts update to 3.0.0 in the Matrix repo, you'll not be able to use the updated add-ons.

It's going to be a mess for some time yet. Sad
(2020-03-14, 18:00)dantist Wrote: The YouTube addon could be installed but isn't working:

For you tube - this is unrelated to any recent Python changes. The API key used by the YouTube add-on has been abused by other developers/addons, so now you need to configure YouTube with a personal API key: https://forum.kodi.tv/showthread.php?pid...pid2681560   

Thanks for explaining the issues. I followed the steps to enable YouTube exactly, but it fails when logging in:
Quote:ERROR: [plugin.video.youtube] LoginException: [401] deleted_client: The OAuth client was deleted.

I know nothing of this is your fault, but as a long time user I have never seen such a mess before. Basically nothing is working right now except for local files.
Reply
Please don't remove OMXPlayer from the rpi2 release.
MMAL video quality/smoothness it's not au pair with OMXPlayer, it's far away.
Reply
I am running LibreELEC on a raspberry PI B+.  Starting somewhere between version #310 and version #313, I lost wireless connectivity.  The "connectivity' window was blank.  I hooked up my wired connection and went back to version #228 and all was well.  There was no particular reason to reverting to that version except to be sure the problem went away. 

I notice that on my other PIs there was a recent firmware update including new network drivers.

Can anyone confirm this behavior?
Reply
New LibreELEC.tv Matrix build #0315: RPi / RPi2
(Supercedes previous build)

SHA256 Checksum: 54a40ae3cd38915cfb3376dda463278d384a161590a2a620d79e774f44df92cf (RPi)
SHA256 Checksum: fb419d0c36d8633417089cf6ad40b32224e31e1a22c62eb99fe30377720d78e1 (RPi2)

# uname -a
Linux rpi512 5.4.24 #1 Sun Mar 15 21:51:16 GMT 2020 armv6l GNU/Linux

# vcgencmd version
Mar 10 2020 18:38:51
Copyright © 2012 Broadcom
version 74d7f53b091e465285f38fb96896a8fc328e4c47 (clean) (release) (raspberrypi_full_legacy)

# lsb_release
LibreELEC (Milhouse): devel-20200315215033-#0315-g6c08564 [Build #0315]

# Kodi version
Kodi (19.0-ALPHA1 Git:fe157eb). Platform: Linux ARM 32-bit

Based on tip of LibreELEC.tv master (6c08564, changelog) and tip of XBMC master (fe157eb, changelog) with the following modifications: Build Highlights:
  1. bluez: update to bluez-5.54
  2. USBCECAdapterDetection: Limit scan to USB subsystem (libcec)
Build Details:
  1. XBMC:
    • Implement range check in URIUtils::resolvePath (PR:17492, 1 commit, 1 file changed)
    • [pvr] add defines for invalid season and episode values (PR:17496, 1 commit, 2 files changed)
  2. pvr.sledovanitv.cz:
    • Fix re-pairing device for failed login (a029382)
  3. Additional commits/pull requests/changes not yet merged upstream:
    • Added: [env] PR:4266 (perma): bluez: update to bluez-5.54
    • Added: [pkg] PR:494 (perma): USBCECAdapterDetection: Limit scan to USB subsystem (libcec)
Texture Cache Maintenance Utility: Preload your texture cache for optimal UI performance. Remotely manage media libraries. Purge unused artwork to free up space. Find missing media. Configurable QA check to highlight metadata issues. Aid in diagnosis of library and cache related problems.
Reply
New LibreELEC.tv Matrix build #0316: RPi / RPi2
(Supercedes previous build)

SHA256 Checksum: 7775497d8ab08366c4244ae96d6dbda6384eee7867305508b04a873e052e51f6 (RPi)
SHA256 Checksum: cd7843c1e8e3250973747788536735e0b2c1e806bef4408eea5e24f17101aaa5 (RPi2)

# uname -a
Linux rpi512 5.4.24 #1 Tue Mar 17 00:09:42 GMT 2020 armv6l GNU/Linux

# vcgencmd version
Mar 10 2020 18:38:51
Copyright © 2012 Broadcom
version 74d7f53b091e465285f38fb96896a8fc328e4c47 (clean) (release) (raspberrypi_full_legacy)

# lsb_release
LibreELEC (Milhouse): devel-20200317000858-#0316-g9542570 [Build #0316]

# Kodi version
Kodi (19.0-ALPHA1 Git:365c4cd). Platform: Linux ARM 32-bit

Based on tip of LibreELEC.tv master (9542570, changelog) and tip of XBMC master (365c4cd, changelog) with the following modifications: Build Highlights:
  1. gcc: update to gcc-9.3.0
  2. alsa-lib: use hda_intel driver on Intel boards with a DSP
    Quote:Should fix the missing audio some Intel NUC users experience.
  3. USBCECAdapterDetection: Only scan tty (libcec)
    Quote:Second attempt at addressing the excessive load caused by CEC bus scans
Build Details:
  1. LibreELEC.tv:
    • Allwinner: Update Cedrus patches (PR:4267, 2 commits, 3 files changed)
  2. XBMC:
    • [Music]Fix music library migration to MyMusic74 (PR:17507, 1 commit, 1 file changed)
    • [EPG] change season/episode infolabels for specials (PR:17488, 1 commit, 3 files changed)
  3. Additional commits/pull requests/changes not yet merged upstream:
    • Updated: [env] PR:4242 (perma): rpi-eeprom: update to rpi-eeprom-<next>
    • Added: [env] PR:4262 (perma): gcc: update to gcc-9.3.0
    • Added: [env] PR:4268 (perma): alsa-lib: use hda_intel driver on Intel boards with a DSP
    • Added: [pkg] PR:495 (perma): USBCECAdapterDetection: Only scan tty (libcec)
Texture Cache Maintenance Utility: Preload your texture cache for optimal UI performance. Remotely manage media libraries. Purge unused artwork to free up space. Find missing media. Configurable QA check to highlight metadata issues. Aid in diagnosis of library and cache related problems.
Reply
(2020-03-13, 07:24)Milhouse Wrote:
(2020-03-13, 06:28)bill_orange Wrote:
(2020-03-12, 23:23)Milhouse Wrote: Yes - those are not crash logs, you should have at least one crash log in /storage/.kodi/temp - try uploading the latest zip from the Logfiles samba share as that should include all the crash logs. 
Okay here you go: https://1drv.ms/u/s!AmXKqAwyCrbxiN1I8hvl...A?e=zWP0Is  

Thanks. Your zip contains only 3 crash logs (we retain the 10 most recent crash logs) which makes me wonder where the rest are - or maybe kodi isn't crashing when the CEC source is changed?

2 of the crash logs are from 8 March (based on #0306) and show "normal" crashes on Kodi shutdown, while the remaining crash log is from 4 March (based on #0225) and seems to crash at 06:18 in the morning: http://ix.io/2e66 - there's not a huge amount of detail in the traces, unfortunately.

In your original post you showed a log extract with date 2020-03-06 but there's no corresponding crash log for this period - did you upload all the crash logs? If you did, then it doesn't look like kodi is crashing - one other possibility is that it's being killed by the out of memory process killer as this doesn't leave a tell-tale crash log, and the details would be in the system log (journalctl -a | pastebinit).  
Here is the system log from journalctl -a 

**EDIT link regenerated **

https://1drv.ms/u/s!AmXKqAwyCrbxiN1Njylo...Q?e=gwAfui
Reply
  •   
  • 1
  • 55
  • 56
  • 57(current)
  • 58
  • 59
  • 86
  •   



Logout Mark Read Team Forum Stats Members Help
LibreELEC Testbuilds for RaspberryPi (Kodi 19.0)8
This forum uses Lukasz Tkacz MyBB addons.