Posts: 23,264
Joined: Aug 2011
Reputation:
1,074
fritsch
Team-Kodi Developer
Posts: 23,264
That dmesg shows nothing, but a clean boot.
The thread apply all bt needs to be done after you enter "CTRL C" (control c on the keyboard) - that biscally means kodi did not crash but is waiting for something.
Please disable UPNP server completely before retrying, there is a bug in 16.1 with upnp server.
First decide what functions / features you expect from a system. Then decide for the hardware. Don't waste your money on crap.
Posts: 23,264
Joined: Aug 2011
Reputation:
1,074
fritsch
Team-Kodi Developer
Posts: 23,264
Nope. Should be fixed. Most likely I looked at the wrong log.
First decide what functions / features you expect from a system. Then decide for the hardware. Don't waste your money on crap.
Posts: 52
Joined: Jan 2016
Reputation:
0
I do have a crash that seems the same on the git checkout I have. That's what the logs are from.
However I haven't had that crash since disabling UPnP.
Posts: 23,264
Joined: Aug 2011
Reputation:
1,074
fritsch
Team-Kodi Developer
Posts: 23,264
Are we talking about a "crash" or about a hang now?
First decide what functions / features you expect from a system. Then decide for the hardware. Don't waste your money on crap.
Posts: 52
Joined: Jan 2016
Reputation:
0
2016-09-15, 18:48
(This post was last modified: 2016-09-15, 18:49 by messers.)
Also I had been running Kodi in windowed mode. Within minutes of entering fullscreen the issue occurred. On the git version I notice audio stalls/skips during these events which I did not notice in Jarvis.
I hope I'm being useful and not difficult.
Posts: 52
Joined: Jan 2016
Reputation:
0
Thanks, fritsch. That answers my question