Crash on Ubuntu

[crackulator]

Testing knewc 2.7.2 on Ubuntu 18.04 client with remote v5 NextPVR Server. When I select the add-on icon, it appears to start, and then bails back to kodi. No message or anything. Log enclosed.

I note that this is in "Autostart UI Client" (box is checked). If I try it in native kodi (box not checked), it gives me a partially-rendered screen and the UI is non-functional.

Server is up and I can hit it with web browser and everything looks fine.

[mvallevand]

skin.aura is not supported maybe setup classic skin in knewc. Also try local lan with local ip before dns.

Martin

[crackulator]

Does the same in Estuary on local network. Here's a log.

[crackulator]

Classic skin in knewc settings, same result.

[mvallevand]

There may be a file predating my involvement with x-newa missing. Does adding any file as fanart.jpg to the base folder for knewc help?

Martin

[crackulator]

Doesn't seem to. I can see the fanart image in the kodi background when the "cursor" is parked on the knewc icon, but it still exits as soon as it starts.

[mvallevand]

There is a server side 500 are you sure there is a crash or is knewc just exiting back to Kodi? Does this knewc install connect to your v4 server?

Martin

[crackulator]

knewc is just exiting back to kodi.
That knewc install works fine in Autostart UI Client with v4 server.
And it works fine in native UI with v5 server.
The problem seems to be only Autostart UI and v5 server.

[mvallevand]

Ok so configuring the skin properly fixed the python UI issue. Sub might need the server logs to address the 500 return in v5.

Martin

[crackulator]

Yeah the UI is fine if I use Estuary with Estuary. Haven't tried others, though I can if it's of interest to you. Not sure what the underlying story is there, if it requires explicit support for each skin, that's pretty unfortunate.

Here are both sides of the logs for the disappearing-knewc-probably-500-error issue, incident at 11:27p.