@Solo0815:
Just looking at the "systemctl stop kodi" shutdown process on my system (latest build):
Code:
17:05:22 410.215088 T:3040694272 INFO: Received SIGTERM...
17:05:22 410.215363 T:3040694272 DEBUG: CAnnouncementManager - Announcement: OnQuit from xbmc
17:05:22 410.215668 T:3040694272 DEBUG: GOT ANNOUNCEMENT, type: 8, from xbmc, message OnQuit
17:05:22 410.216095 T:3040694272 NOTICE: Storing total System Uptime
17:05:22 410.216736 T:3040694272 NOTICE: Saving settings
17:05:22 410.225281 T:3040678976 INFO: Received SIGTERM...
17:05:22 410.225586 T:3040678976 DEBUG: CAnnouncementManager - Announcement: OnQuit from xbmc
17:05:22 410.225891 T:3040678976 DEBUG: GOT ANNOUNCEMENT, type: 8, from xbmc, message OnQuit
17:05:22 410.226379 T:3040678976 NOTICE: Storing total System Uptime
17:05:22 410.227173 T:3040678976 NOTICE: Saving settings
and the same from your system:
Code:
13:38:09 1768.387329 T:3041046528 INFO: Received SIGTERM...
13:38:09 1768.387573 T:3041046528 DEBUG: CAnnouncementManager - Announcement: OnQuit from xbmc
13:38:09 1768.422729 T:3041031232 INFO: Received SIGTERM...
13:38:09 1768.423218 T:3041031232 DEBUG: CAnnouncementManager - Announcement: OnQuit from xbmc
Two things that stand out:
1) Why are two separate threads both saving settings on shutdown?
2) Your system doesn't seem to handle the OnQuit announcement(s), so chances are the threads are simply hanging at that point
There is also a regression somewhere which results in settings being "lost" and reverting to defaults (guisettings.xml being trashed?) - I wonder if that is related somehow. Can't spend any more time on this today but if you can send me the archive maybe I can reproduce and investigate further tomorrow.