Closed CurlyMoo closed 9 years ago
The issue is that somehow the xbmc-loaded event doesn't get emitted by your patch inside XBMC.
@CurlyMoo
you have to find one more factor in that as look here :+1: (tailf on event log and start xbmc started at the same time, both outputing to screen. logs starts with event "starting xbmc", in 6s xbmc has home screen, comnmand "start xbmc" returns to console as "xbmc-loadeded event was emited by job xbmc-loaded"
root@sona ~ # tailf /var/log/upstart/upstart-ev.log | awk -F' ' '{print $1}' & start xbmc
[2] 3231
Wed Dec 31 06:51:42 CET 2014 325.96 148534580.97 starting xbmc
Wed Dec 31 06:51:42 CET 2014 326.01 148534580.97 started xbian-xbmc-cpufreq
Wed Dec 31 06:51:42 CET 2014 326.43 148534580.97 started wait-for-state xbmc-loaded
Wed Dec 31 06:51:48 CET 2014 331.86 148534583.69 started xbmc-loaded
Wed Dec 31 06:51:48 CET 2014 331.94 148534583.69 stopped wait-for-state xbmc-loaded
xbmc start/running, process 3282
root@sona ~ # Wed Dec 31 06:51:48 CET 2014 332.05 148534583.69 started xbmc
Wed Dec 31 06:51:48 CET 2014 332.20 148534583.69 stopped tvonoff-xbmc
Wed Dec 31 06:51:55 CET 2014 338.85 148534585.25 stopped xbmc-loaded
tailf /var/log/upstart/upstart-ev.log | awk -F' ' '{print $1}' & start xbmcWed Dec 31 06:52:02 CET 2014 346.73 148534586.32 stopped xbian-xbmc-cpufreq
Wed Dec 31 06:52:02 CET 2014 346.75 148534586.32 started xbmc-screensaver
Wed Dec 31 06:52:03 CET 2014 346.99 148534586.32 started xbmc-priority
Wed Dec 31 06:52:03 CET 2014 347.14 148534586.32 stopped xbmc-priority
this is the last img with xbmc-6q updated to 14.0RC3 on HB1. but the same happens with CBi with root originally installed as wheezy (and being like very old rootfs
what to check quick --if /etc/sudoers.d/xbian is proper file and contains beside others also
/sbin/start
We know it's working again.
Somehow XBMC is entering a reboot loop recently. Seems to be related to the init scripts.
Temporary workaround is commenting in /etc/init/xbmc.conf