keep having crashes constantly on the 2 latest revisions
http://paste.osmc.io/equvazipux
cant even enable debug, sry
did delete .kodi to see if that would help but sadly it didnt
keep having crashes constantly on the 2 latest revisions
http://paste.osmc.io/equvazipux
cant even enable debug, sry
did delete .kodi to see if that would help but sadly it didnt
ct 11 19:03:35 Bedroom mediacenter[843]: terminate called after throwing an instance of 'std::logic_error'
Oct 11 19:03:35 Bedroom mediacenter[843]: what(): basic_string::_S_construct null not valid
Looks like bad exception handling somewhere, so debug log wonāt help. But you can enable debug logging by editing /usr/bin/mediacenter and adding --debug to the $KODI line (might be helpful for the future)
Also now having problems with a boot loop on 167. Seems this version is busted. Gone back to a 166 and 165 and it still crashes.
Iāve removed 167 from the repo. Doing some more testingā¦
added the debug line
sudo -u osmc $KODI --debug --standalone -fs --lircdev /var/run/lirc/lir
http://paste.osmc.io/apasujiget
tnx Sam
although it doesnt generate a new .kodi directory it just crashes
Not sure why I tried this, but running
sudo /usr/bin/mediacenter
Gets osmc up and running without the boot loop.
hmm that doesnt make a whole lot of sense, but it worksā¦ for 2 secs then crash.
tried a second time and then it didnt crash.
I think this patch fixes it.
Tried it on one of my piās and it seems to have solved the problem.
awesome, posting another build in a while then ?
Its on the go Each build takes 4-5 hours.
hehe not expect a rush build aslong as its in the works im ok
plus i can use the workaround until the new build
Oddly enough Iāve done back 3-4 builds and they all fail now until I update /usr/bin/mediacenter.
The above patch will only be useful if youāre on staging repo as well as @gmcās.
@gmc if you build with this patch it will break it for non staging users. Will resolve this soon, but for now staging users can manually edit /usr/bin/mediacenter.
on staging been that for a long time still failed today after the 2 latest revisions
Thanks - Iāll add a note to the top in the meantime.
Still having the problem with Kodi not starting in version 166, even with the manual fix of the start script. Running a RBP1.
Any suggestions?
sudo service mediacenter stop
sudo /usr/bin/mediacenter &
simple crude workaround while gmc and sam are working out a proper patch
plus are you on staging @haegg78?
How do I verify if Iām on staging, have done the steps defined at the top? @Toast
Been running the Kodi 17 builds since the start of this thread.
When running your provided workaround, Kodi exits after ~20 secs with return code 139.
There will be no issue if you are not on staging repository.
I have a proposed solution for those that are, but need a tester first. I have spoken to @gmc about this.
Whatās in your /etc/apt/sources.list
If you are on staging and applied the fix it could be a different issue. Can you post debug logs?
Does renaming the .kodi folder make any difference?
deb http://mirrordirector.raspbian.org/raspbian jessie main contrib non-free
deb http://apt.osmc.tv jessie main
deb http://download.osmc.tv/dev/gmc ./
Is the contents of /etc/apt/sources.list.
I will try and create a debug log tomorrow morning.