Thread Closed
v17 LibreELEC Testbuilds for RaspberryPi (Kodi 17.0)
(2016-04-26, 23:45)Milhouse Wrote:
(2016-04-26, 23:10)Kiralina Wrote: Here it is: http://xbmclogs.com/pquz55osi

Same behavior with #0423 and #0424

Thank you.

So quasar works with #0420 but not #0423 or #0424. Strange. The only obvious change in #0423 is the libressl change, possibly connman 1.32, but the quasar query isn't https, at least not to the local trakt server.

Quasar does however appear to be crashing due to an invalid/unexpected response from the local trakt server - maybe trakt is having a problem authenticating remotely? I think you need to get the log from the trakt server (if there is such a log), or speak with a trakt/quasar developer (pinging @Razze for trakt).

I've followed the steps in 2321749 (post) and with build LE #0401 I get the authorisation code. Great.

I also get the authorisation code by clicking "Addons" > "Settings" (context menu) > "Advanced" > "Authorize Quasar", and that's my current "test method".

Starting with build LE #0408 I get an HTTP Error. I get this error with all builds after #0408, including #0420.

Build LE #0408 is the first with PR:128 so unfortunately this looks like another certificate issue.

To see the issue, in LE #0407:
Code:
rpi22:~ # curl -v http://localhost:65251/trakt/authorize
*   Trying 127.0.0.1...
* Connected to localhost (127.0.0.1) port 65251 (#0)
> GET /trakt/authorize HTTP/1.1
> Host: localhost:65251
> User-Agent: curl/7.48.0
> Accept: */*
>
< HTTP/1.1 200 OK
< Content-Type: text/plain; charset=utf-8
< Date: Thu, 05 May 2016 17:57:27 GMT
< Content-Length: 0
<
* Connection #0 to host localhost left intact

but in LE #0408 there is an "internal server error":
Code:
rpi22:~ # curl -v http://localhost:65251/trakt/authorize
*   Trying 127.0.0.1...
* Connected to localhost (127.0.0.1) port 65251 (#0)
> GET /trakt/authorize HTTP/1.1
> Host: localhost:65251
> User-Agent: curl/7.48.0
> Accept: */*
>
< HTTP/1.1 500 Internal Server Error
< Date: Thu, 05 May 2016 17:54:53 GMT
< Content-Length: 0
< Content-Type: text/plain; charset=utf-8
<
* Connection #0 to host localhost left intact

Since Quasar is shipped with a pre-compiled binary it's not possible to tell what it's doing (maybe the code is on Github or Sourceforge, not looked) but it doesn't seem to like the CA bundle that is shipped with LibreELEC.

The nearest I can come to determining what Quasar is doing is that if I recreate "/etc/pki/tls/cacert.pem" (which is no longer present after PR:128) then Quasar works again even in the latest builds, so it would seem that Quasar has some hard dependency on /etc/pki/tls/cacert.pem (which is just a sym link to /etc/ssl/cacert.pem)

I've had a quick word with the LE team and we'll add back the "/etc/pki/tls/cacert.pm" sym link in tonight's build.
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.
  Thread Closed
 
Thread Rating:
  • 19 Vote(s) - 4.63 Average


Messages In This Thread
RE: LibreELEC Testbuilds for RaspberryPi (Kodi 17.0) - by Milhouse - 2016-05-05, 20:38
RPi2: no DV-codec? - by bubi - 2016-07-10, 10:30
DV-video not working - by bubi - 2016-07-15, 19:48


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