(2019-06-15, 20:24)KrX3D Wrote: so i tried it again. new system than updated to the newest lobreelec version, emby installed.
i started one episode and it was loading and loading for more than 10 minutes than i hit "back" and started another episode and kodi froze since i couldnt click anything etc so i rebooted the pi
here is the normal and the crash log i hope one of them helps
normal: http://ix.io/1LSi
crash: http://ix.io/1LSj
Your crash log doesn't include any evidence of a crash, so I'm guessing your system has never actually crashed, and is either busy or freezing.
Your log says you're still using #0605 but you said you were using "newest lobreelec version" which would be #0614 at the time of writing, did you try updating to a more recent version such as #0614?
If you are rebooting the RPi then uploading your current log won't include any relevant information - we'd need to see kodi.old.log which is only available from the ssh command line with
cat /storage/.kodi/temp/kodi.log | pastebinit.
That said, I missed the edit from your previous post:
(2019-06-06, 19:33)KrX3D Wrote: EDIT: i just tested on my "damaged" kodi if i could play those movies/series through smb and that work fine.
so it seems to be emby related. so i will still try an clean kodi enviourment, since if it is really emby i will need to stay on 604e because emby wont make changes to solve bugs for kodi19 until the end of 2019 or even 2020....
and while im writing this, the episode was trying to start since 5 minutes and it worked on 605. so it seems that after starting an episode it takes like 5 minutes to start, but when i hit any button during that start process my raspberry freezes
Yes, this does seem to be Emby related.
To a large extent it's understandable if third-party add-on maintainers don't want to get involved investigating issues with their add-ons and bleeding edge Kodi 19 builds, but they're only storing up problems for themselves and their users until just before Kodi 19 is released, or even once Kodi 19 is released. Which is unfortunate, IMHO.
There's not really very much I can do to help in this situation, as I don't have the bandwidth to support third-party addons that don't work with Kodi 19 alphas, particularly if the add-on maintainers don't want to help either.
This particular problem - which might need fixing in Emby, or maybe it is a Kodi issue, or even a bit of both - will just have to wait until the end of the Kodi 19 development cycle when someone from Emby is willing to investigate and help identify the problem. If you're very lucky, another add-on will be affected in a similar way and the add-on maintainer of the second add-on will be willing to investigate the Kodi 19 issue so that the underlying problem might be found - if that requires a fix in Kodi 19 then at some point Emby might work again with Kodi 19.
For the time being all I can suggest is that you don't use these bleeding edge test builds with Emby, and this Emby issue (and maybe other, as yet unknown, Emby issues) will have to be resolved at the last minute, or after Kodi 19 is released. And very little sympathy might be available to Emby from Kodi developers if the Emby add-on is now permanently broken.
