20 Nov 2019 - TVDB Scraper v3.2.0 is now available which reinstates scraping. TVDB are still in the process of fixing a number of bugs so there may still be further breakages. See this post. 2901570 (post)

  •   
  • 1
  • 130
  • 131
  • 132(current)
  • 133
  • 134
  • 218
  •   
  Thread Closed
v17 LibreELEC Testbuilds for RaspberryPi (Kodi 17.0)
(2016-09-01, 05:27)thegooddoctor Wrote: -Skipping backwards now shows buffering window (my wire network is uncongested and optimized - there has never been an issue previously).

That is a deliberate skin change. Estuary didn't previous indicate buffering at all.
There is always buffering after a seek, but with fast network/disk it just takes a fraction of a second.
I must admit I'd prefer the buffering overlay on skin held off for about a second before appearing as it is ugly just popping up for half a second.
OpenVPN on LibreELEC (Krypton) v7.90.004 ALPHA on a Raspberry Pi 2

Hi.
I'm trying to connect to Hide.me VPN service with OpenVPN on LibreELEC (Krypton) v7.90.004 ALPHA on a Raspberry Pi 2.
I have this error:

Code:
LibreELEC:~/.kodi/addons/service.vpn.manager/HideMe # openvpn Milan\ \(UDP\).ovpn
Wed Aug 31 20:01:22 2016 OpenVPN 2.3.11 armv7ve-libreelec-linux-gnueabi [SSL (OpenSSL)] [LZO] [EPOLL] [IPv6] built on Aug  8 2016
Wed Aug 31 20:01:22 2016 library versions: LibreSSL 2.3.5, LZO 2.09
Wed Aug 31 20:01:22 2016 WARNING: file '/storage/.kodi/addons/service.vpn.manager/HideMe/pass.txt' is group or others accessible
Wed Aug 31 20:01:22 2016 WARNING: file '/storage/.kodi/addons/service.vpn.manager/HideMe/ta.key' is group or others accessible
Wed Aug 31 20:01:22 2016 Control Channel Authentication: using '/storage/.kodi/addons/service.vpn.manager/HideMe/ta.key' as a OpenVPN static key file
Wed Aug 31 20:01:22 2016 UDPv4 link local: [undef]
Wed Aug 31 20:01:22 2016 UDPv4 link remote: [AF_INET]159.122.133.197:4000
Wed Aug 31 20:01:22 2016 WARNING: this configuration may cache passwords in memory -- use the auth-nocache option to prevent this
Wed Aug 31 20:01:22 2016 VERIFY ERROR: depth=2, error=format error in certificate's notAfter field: C=MY, ST=Wilayah Persekutuan, L=Labuan, O=eVenture Limited, OU=Certificate Authority, CN=Hide.Me Root CA
Wed Aug 31 20:01:22 2016 OpenSSL: error:14090086:SSL routines:SSL3_GET_SERVER_CERTIFICATE:certificate verify failed
Wed Aug 31 20:01:22 2016 TLS_ERROR: BIO read tls_read_plaintext error
Wed Aug 31 20:01:22 2016 TLS Error: TLS object -> incoming plaintext read error
Wed Aug 31 20:01:22 2016 TLS Error: TLS handshake failed
Wed Aug 31 20:01:22 2016 SIGUSR1[soft,tls-error] received, process restarting


May be some Root CA missed in LibreSSL?

Just for your info, with OpenELEC 6.0.3 and with LibreELEC (Jarvis 16.1) v7.0.2 I was able to connect with the exactly same .ovpn file.

I hope in your help.
Thanks.
Kodi 18: Nvidia Shield TV (main device) and LibreELEC on Raspberry Pi 2 and Odroid C2
TV: Panasonic TX-55EZ950E (OLED)
AVR: Onkyo TX-NR509 (HDMI ARC)
This isn't the 7.90.004 support thread. Test with a build from this thread, or post your problem on the LibreELEC forum. Although to be honest it appears more likely that it's the server certificate that is invalid, as per the error message. 7.90.004 uses a different version of LibreSSL to OpenELEC 6.0.3, this could be one of many security issues "fixed".
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.
Hi.
Since the build #0827 the addon "radio" broke down.
In the log file (kodi.log) the follow message was show:

07:18:19 31748.623047 T:1362097056 NOTICE: [xbmcswift2] Request for "/" matches rule for function "show_root_menu"
07:18:22 31752.257812 T:1503204256 NOTICE: [xbmcswift2] Request for "/stations/my/" matches rule for function "show_my_stations"
07:18:22 31752.257812 T:1503204256 NOTICE: [plugin.audio.radio_de] __add_stations started with 11 items
07:18:26 31756.201172 T:1362097056 NOTICE: [xbmcswift2] Request for "/station/2255" matches rule for function "get_stream_url"
07:18:26 31756.203125 T:1362097056 NOTICE: [plugin.audio.radio_de] get_station_by_station_id started with station_id=2255
07:18:26 31756.203125 T:1362097056 NOTICE: [plugin.audio.radio_de] __api_call started with path=broadcast/getbroadcastembedded, param={'broadcast': '2255'}
07:18:26 31756.203125 T:1362097056 NOTICE: [plugin.audio.radio_de] __urlopen opening url=http://radio.de/info/broadcast/getbroadcastembedded?broadcast=2255
07:18:26 31756.351562 T:1362097056 NOTICE: [plugin.audio.radio_de] get_stream_url result: http://c22033-l.i.core.cdn.streamfarm.ne...de_128.mp3
07:18:28 31757.599609 T:1961611264 ERROR: exception in CApplication:Tonguerocess()

when the playback will start, there some stripe on the display, and the system reboot after few seconds.
My live TV and Radio has always been perfect, using rbp3 and media portal client.
(2016-09-01, 12:53)popcornmix Wrote:
(2016-09-01, 05:27)thegooddoctor Wrote: -Skipping backwards now shows buffering window (my wire network is uncongested and optimized - there has never been an issue previously).

That is a deliberate skin change. Estuary didn't previous indicate buffering at all.
There is always buffering after a seek, but with fast network/disk it just takes a fraction of a second.
I must admit I'd prefer the buffering overlay on skin held off for about a second before appearing as it is ugly just popping up for half a second.
I agree - for as brief as the buffering window appears it is annoying
It needs to be held off for a certain period, or have the option to deactivate the window
Over the last few weeks I've noticed that when an overlay pops up when hitting the info button or when a commercial is about to skip and while watching recorded mpeg2 1080i60 content, sometimes my Vizio TV will turn blue for a bit and then say "invalid format". If I switch to another input and back or turn the tv on and off it will show a picture again and continue to playback fine. I have tried all kinds of settings, adjust display rate on and off, sync playback to display on and off. Nothing seemed to help.

Finally tonight I tried various options for deinterlacing. My testing indicates that off and mmal Bob are ok but as soon as I switch to mmal advanced I can reproduce the problem by hitting the info button a few times to pop the info display up and take it away.

Not sure what that indicates other than mmal advanced and an overlay seem to produce an odd resolution or refresh rate for some period of time which confuses my tv. For now I can switch to mmal Bob and prevent the issue.
(2016-09-01, 20:52)hansdd Wrote: Hi.
Since the build #0827 the addon "radio" broke down.
In the log file (kodi.log) the follow message was show:
...
when the playback will start, there some stripe on the display, and the system reboot after few seconds.
Do you have the crashlog? Most likely candidate for the breakage is PR10236.
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.
New LibreELEC.tv Krypton build #0901: RPi / RPi2
(Supercedes previous build)

Code:
# uname -a
Linux rpi512 4.7.2 #1 Thu Sep 1 21:03:53 BST 2016 armv6l GNU/Linux

# vcgencmd version
Aug 23 2016 15:58:54
Copyright (c) 2012 Broadcom
version f23e65aeeffca65654550c93254a0ee55f34fb07 (clean) (release)

# lsb_release
LibreELEC (Milhouse) - Version: devel-20160901210254-#0901-gd416dad [Build #0901]

# vcdbg log msg 2>&1 | grep DTOK
002391.455: Kernel trailer DTOK property says yes

# Kernel device tree status: Enabled

Based on tip of LibreELEC.tv master (d416dad6, changelog) and tip of XBMC master (f39d849f, changelog) with the following modifications: Build Highlights:
  1. Minors
Build Details:
  1. LibreELEC.tv:
    • init: Add upgrade check to avoid incompatible upgrades [RFC,WIP] (PR:535, 1 commit, 1 file changed)
  2. peripheral.joystick:
    • Update to peripheral API v1.1.0: Add function to save button maps (PR:50, 5 commits, 14 files changed)
  3. Additional commits/pull requests/changes not yet merged upstream:
    • Added: [pkg] PR:10372: [cmake] fix sse detection
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.
@BigNoid & @smp1 - are USB game controllers still causing crashes/weird stacktraces in the latest build (not that I've intentionally fixed anything, but there have been some peripheral.joystick updates in the last few builds). Thanks.
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.
(2016-09-02, 07:18)Milhouse Wrote: @BigNoid & @smp1 - are USB game controllers still causing crashes/weird stacktraces in the latest build (not that I've intentionally fixed anything, but there have been some peripheral.joystick updates in the last few builds). Thanks.

Still crashes:
Code:
Thread 1 (Thread 0x664ff3a0 (LWP 6342)):
#0  0x0082e0c8 in NPT_BsdSocket::RefreshInfo() ()
#1  0x1501a8c0 in ?? ()
Backtrace stopped: previous frame identical to this frame (corrupt stack?)
############# END STACK TRACE ###############
(2016-09-01, 18:42)Milhouse Wrote: This isn't the 7.90.004 support thread. Test with a build from this thread, or post your problem on the LibreELEC forum. Although to be honest it appears more likely that it's the server certificate that is invalid, as per the error message. 7.90.004 uses a different version of LibreSSL to OpenELEC 6.0.3, this could be one of many security issues "fixed".

Hi Mr. Milhouse.
I'm quit sure that if I use the lastest build I will have the same problem....
The problem is that the Hide.me certificate will expires in year 2046 and the LibreSSL 2.3.x will not work well on the Raspberry Pi due to "Year 2038 bug".

See here:
https://github.com/libressl-portable/por...issues/207

This is the reason that with oldest version such as OpenELEC 6.0.3 or with LibreELEC (Jarvis 16.1) v7.0.2 I did not have this problem (beacuse the OpenSSL / LibreSSL is older version).

So, I expect, that all certificates that will expires after 03:14:07 UTC on 19 January 2038 will have the same problem on all LibreELEC with Kodi 17.0.

Hope in a fix.

Thanks.
Kodi 18: Nvidia Shield TV (main device) and LibreELEC on Raspberry Pi 2 and Odroid C2
TV: Panasonic TX-55EZ950E (OLED)
AVR: Onkyo TX-NR509 (HDMI ARC)
(2016-09-02, 06:06)zaphod24 Wrote: Not sure what that indicates other than mmal advanced and an overlay seem to produce an odd resolution or refresh rate for some period of time which confuses my tv. For now I can switch to mmal Bob and prevent the issue.

Overclocking will likely resolve this. sdram_freq, core_freq and v3d_freq could all help (roughly in that order of likelihood).
(2016-09-02, 13:29)popcornmix Wrote:
(2016-09-02, 06:06)zaphod24 Wrote: Not sure what that indicates other than mmal advanced and an overlay seem to produce an odd resolution or refresh rate for some period of time which confuses my tv. For now I can switch to mmal Bob and prevent the issue.

Overclocking will likely resolve this. sdram_freq, core_freq and v3d_freq could all help (roughly in that order of likelihood).

Thanks for the suggestions. Any suggestions for values to start with and if overvolting is needed?
(2016-09-02, 12:10)outcave Wrote:
(2016-09-01, 18:42)Milhouse Wrote: This isn't the 7.90.004 support thread. Test with a build from this thread, or post your problem on the LibreELEC forum. Although to be honest it appears more likely that it's the server certificate that is invalid, as per the error message. 7.90.004 uses a different version of LibreSSL to OpenELEC 6.0.3, this could be one of many security issues "fixed".

Hi Mr. Milhouse.
I'm quit sure that if I use the lastest build I will have the same problem....
The problem is that the Hide.me certificate will expires in year 2046 and the LibreSSL 2.3.x will not work well on the Raspberry Pi due to "Year 2038 bug".

See here:
https://github.com/libressl-portable/por...issues/207

This is the reason that with oldest version such as OpenELEC 6.0.3 or with LibreELEC (Jarvis 16.1) v7.0.2 I did not have this problem (beacuse the OpenSSL / LibreSSL is older version).

So, I expect, that all certificates that will expires after 03:14:07 UTC on 19 January 2038 will have the same problem on all LibreELEC with Kodi 17.0.

Hope in a fix.

Thanks.

Thanks. Yes, this is a 32-bit OS issue (more specifically, a 32-bit ABI issue). Your certificate would be fine in a 64-bit OS, indeed there is no problem with the sample certificates shown on github when testing the latest LibreELEC Generic (x86_64) builds.

However there are no immediate plans for a 64-bit version of LibreELEC for RPi (which would only support RPi3 hardware), so fixing this in libressl to support post-2038 dates on 32-bit platforms is the only practical solution. I would expect this to be resolved in libressl at some point as it's going to affect a lot of platforms, but until then it might be easier for certificate authorities to avoid using outlandish post-2038 expiry dates.
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.
  •   
  • 1
  • 130
  • 131
  • 132(current)
  • 133
  • 134
  • 218
  •   
  Thread Closed
 
Thread Rating:
  • 19 Vote(s) - 4.63 Average



Logout Mark Read Team Forum Stats Members Help
LibreELEC Testbuilds for RaspberryPi (Kodi 17.0)4.6319