v16 Kodi GUI stuck during bootup
#1
To try LibreELEC I created a new sdcard with Kodi 16.1 (RPi3, LibreELEC 7.0.2), yesterday.

I restored a backup from Kodi 15 (OpenELEC 6.0.3)

After changing a number of settings yesterday, I'm not able to startup Kodi properly today.
The GUI is stuck with the following on screen:

Popup window in top richt:
Watchdog starting. Please wait... or
Loading guide from database


Popup window middle of the screen:
PVR manager is staring up
"No PVR clients have been started yet. Wait for the PVR clients to start up. Check the log for more information about this message."

Popup window bottom right:
Pulse-Eight CEC adapter
Connecting to: Pulse-Eight CEC adapter

Current Time (top right) is also stuck. (stuck at 17:17)


I can still ssh to the RPi.


Throughout the evening yesterday I have rebooted the system a few times, which worked normally.


last few changes where related to:
  • Channel logo's (channel icons)
  • EPG (just a change to allow caching) : System > Settings > TV > Guide > Don't cach in local database > DISABLE
  • Limit debuging to JSONRPC, CEC, Web in /storage/.kodi/userdata/advancedsettings.xml, but removed these to get all debug again.
  • Might have updated the TVHeadend client add-on.

I unplugged all USB devices, but still the same.

A tail -f /storage/.kodi/temp/kodi.log shows that there is not much activity from the moment the GUI is becoming in a stuck state.
But a keypress on the tv remote (CEC) is still recognized.

Code:
# tail -f -n30  /storage/.kodi/temp/kodi.log
17:18:06  27.046091 T:1857000352   DEBUG: CecLogMessage - >> TV (0) -> Broadcast (F): report physical address (84)
17:18:10  31.765108 T:1857000352   DEBUG: CecLogMessage - >> 41:83
17:18:10  31.765310 T:1857000352   DEBUG: CecLogMessage - << Recorder 1 (1) -> broadcast (F): physical adddress 3000
17:18:10  31.765385 T:1857000352   DEBUG: CecLogMessage - << 1f:84:30:00:01
17:18:10  31.765457 T:1857000352   DEBUG: CecLogMessage - >> Playback 1 (4) -> Recorder 1 (1): give physical address (83)
17:18:11  32.229256 T:1857000352   DEBUG: CecLogMessage - >> 4f:87:00:1a:11
17:18:11  32.229492 T:1857000352   DEBUG: CecLogMessage - Playback 1 (4): vendor = Google (001a11)
17:18:11  32.229565 T:1857000352   DEBUG: CecLogMessage - >> Playback 1 (4) -> Broadcast (F): device vendor id (87)
17:18:11  32.375755 T:1857000352   DEBUG: CecLogMessage - >> 4f:84:20:00:04
17:18:11  32.375874 T:1857000352   DEBUG: CecLogMessage - Playback 1 (4): physical address changed from ffff to 2000
17:18:11  32.375946 T:1857000352   DEBUG: CecLogMessage - >> Playback 1 (4) -> Broadcast (F): report physical address (84)
17:18:57  78.928665 T:1952445344   DEBUG: CAESinkPi:Drain delay:100ms now:0ms
17:19:07  88.928963 T:1952445344   DEBUG: CAESinkPi:Deinitialize
17:19:07  88.929474 T:1952445344   DEBUG: CAESinkPi:SetAudioProps hdmi_stream_channels 0 hdmi_channel_map 00000000
17:19:07  88.936089 T:1952445344   DEBUG: COMXCoreComponent::Deinitialize : OMX.broadcom.audio_render handle 0x73c022f8
17:24:59 440.566254 T:1857000352   DEBUG: CecLogMessage - >> 01:44:01
17:24:59 440.566528 T:1857000352   DEBUG: CecLogMessage - >> TV (0) -> Recorder 1 (1): user control pressed (44)
17:24:59 440.566711 T:1857000352   DEBUG: CecLogMessage - SetCurrentButton up (1) D:0ms cur:1
17:24:59 440.566864 T:1857000352   DEBUG: CecLogMessage - key pressed: up (1) current(ff) duration(0)
17:24:59 440.566986 T:1857000352   DEBUG: CecLogMessage - Changed key up (1) D:0ms cur:ff
17:24:59 440.567444 T:1857000352   DEBUG: CecLogMessage - key pressed: up (1, 0)
17:24:59 440.567596 T:1857000352   DEBUG: PushCecKeypress - received key a6 duration 0 (rep:0 size:0)
17:24:59 440.567657 T:1857000352   DEBUG: PushCecKeypress - added key a6
17:24:59 440.567719 T:1857000352   DEBUG: CecLogMessage - CheckKeypressTimeout T:440.567
17:24:59 440.567780 T:1857000352   DEBUG: CecLogMessage - Key up: idle (duration:0) (1) timeout:500ms (rel:500,rep:0,prs:1,rel:0)
17:24:59 440.874878 T:1857000352   DEBUG: CecLogMessage - >> 01:8b:01
17:24:59 440.875000 T:1857000352   DEBUG: CecLogMessage - key released: up (1) D:307ms
17:24:59 440.875061 T:1857000352   DEBUG: PushCecKeypress - received key a6 duration 307 (rep:0 size:1)
17:24:59 440.875122 T:1857000352   DEBUG: PushCecKeypress - replaced key a6
17:24:59 440.875214 T:1857000352   DEBUG: CecLogMessage - >> TV (0) -> Recorder 1 (1): vendor remote button up (8B)

Code:
# cat /storage/.kodi/temp/kodi.log | wc -l
1437

Full log at: http://pastebin.com/375bggic

Code:
# ls -la ~/.kodi/temp/kodi*
-rw-r--r--    1 root     root        149835 Dec 17 17:24 /storage/.kodi/temp/kodi.log
-rw-r--r--    1 root     root        147428 Dec 17 15:09 /storage/.kodi/temp/kodi.old.log
-rw-r--r--    1 root     root       5206504 Jul 14 03:06 /storage/.kodi/temp/kodi_crashlog_20160714030611.log
-rw-r--r--    1 root     root        251128 Jul 22 22:51 /storage/.kodi/temp/kodi_crashlog_20160722225140.log
-rw-r--r--    1 root     root        176601 Jul 22 22:57 /storage/.kodi/temp/kodi_crashlog_20160722225735.log
-rw-r--r--    1 root     root        965831 Aug 20 18:23 /storage/.kodi/temp/kodi_crashlog_20160820182354.log
-rw-r--r--    1 root     root        137617 Aug 20 18:26 /storage/.kodi/temp/kodi_crashlog_20160820182608.log
-rw-r--r--    1 root     root       7225749 Sep 21 11:18 /storage/.kodi/temp/kodi_crashlog_20160921111825.log
-rw-r--r--    1 root     root       4369629 Sep 29 15:56 /storage/.kodi/temp/kodi_crashlog_20160929155609.log
-rw-r--r--    1 root     root             0 Nov 19 22:15 /storage/.kodi/temp/kodi_crashlog_20161119221502.log
-rw-r--r--    1 root     root       1180465 Nov 29 21:47 /storage/.kodi/temp/kodi_crashlog_20161129214721.log
-rw-r--r--    1 root     root        199376 Dec 16 23:06 /storage/.kodi/temp/kodi_crashlog_20161216230626.log
(Not sure if the crash dump from yesterday is useful. No crashlogs are generated for this GUI stuck state.)



I didn't found similar issues on the forum (yet).

Any advice how I can further debug this?

Edit (2016-12-17): in guisettings.xml I see the old debug settings. If I remove them, they are back on the next reboot.

Code:
<debug>
        <extralogging default="true">true</extralogging>
        <screenshotpath default="true"></screenshotpath>
        <setextraloglevel>64,1024,16384</setextraloglevel>
        <showloginfo default="true">false</showloginfo>
    </debug>

Content of advancedsettings.xml:
Code:
# cat advancedsettings.xml
<?xml version="1.0" encoding="UTF-8"?>
<advancedsettings>
  <loglevel>2</loglevel> <!-- Change this to "1" to hide the on-screen debug log text -->
  <debug>
    <showloginfo>false</showloginfo> <!-- Change this to "false" to hide the on-screen debug log text -->
  </debug>
</advancedsettings>

I have backups of the files in the same directory e.g.:
Code:
# ls -la adv* g*
-rw-r--r--    1 root     root           295 Dec 17 12:15 advancedsettings.xml
-rw-r--r--    1 root     root           419 Dec 17 12:05 advancedsettings_20161216.xml.ron
-rw-r--r--    1 root     root         28479 Dec 17 22:07 guisettings.xml
-rw-r--r--    1 root     root         30038 Nov 20 12:43 guisettings_good_20161120_1237.xml
-rw-r--r--    1 root     root         28479 Dec 17 18:32 guisettings_stuck_at_startup_20161217_1832.xml

Is there a feature/ mechanism that merge these files in guisettings.xml?

moved the backup files to another directory, but still see the same behavior.

Edit (2016-12-21):
I will re-create the sd-card from scratch, and take smaller steps in changing the setup to my liking.
Hopefully I don't see this issue again.
Reply

Logout Mark Read Team Forum Stats Members Help
Kodi GUI stuck during bootup0