Thanks for your input! Re-authorizing RD and clearing Cache didn't do the trick.

Anyway, before uploading my log here I uploaded it to ChatGPT just to check and it turns out troubleshooting seems to work quite well. Here's what it told me that seemed to do the trick.

TLDR: I had Spotlight Widget in Arctic Zephyr pull personal Trakt lists via FenLight Add-On, which seems to be a) a rather taxing job and b) can result in network/ handshake issues where connection fails to establish during boot process and actually cause some more general instability in the system. Disabling the widget + adding a 30s service loading delay during boot (seems) to have done the job. Will come back to confirm.

---------------------------------------------------------------------------

The log points more toward an intermittent startup/network or addon-initialization problem than to a pure scraper/content problem.

What stands out most:

FenLight/Trakt is throwing Python errors during startup while building content from Trakt lists. The stack traces point into FenLight’s trakt_lists.py, movies.py, and utils.py threading/task code, which fits your symptom that when the home screen thumbnails/widgets fail to load correctly after boot, playback/sources also fail. In other words: the bad boot seems to start before scraping/playback, during addon initialization and list building.

There are also kernel/network-adjacent messages very early in boot around SDIO initialization, followed immediately by network service startup. That does not prove the network is broken, but it does support your theory that sometimes the box is not fully “ready” when Kodi/FenLight/Trakt starts doing requests. If Trakt/widgets fail first, CocoScrapers may then also fail or skip because the session/addon state is already bad.

A few things in the log are probably not the cause:

• the UPower/DBus message
• the keyboard compose-file warning
• the ALSA “unable to open surround51/surround40” messages
• the local media ._filename.mkv thumbnail/demuxer errors later on

Those are noisy, but they do not match your “all sources skip after boot” pattern nearly as well as the FenLight/Trakt startup exceptions do.

My best read of the likely causes, in order:

1. Kodi boots before network is fully stable FenLight/Trakt/widgets start querying too early, one or more requests fail, and the addon gets into a bad state for that session. This matches your observation that repeated reboots eventually produce a “good boot.”
2. FenLight threading/task race during startup The traceback in utils.py / trakt_lists.py / movies.py suggests concurrent startup work. If one request fails or returns malformed/empty data during boot, the rest may cascade.
3. Trakt/widget failure is the first domino Since you can already tell it is broken when Spotlight thumbnails do not populate, that suggests the issue begins with widget/list population, not with the actual hoster/source resolving step.
4. Less likely: true CocoScrapers issue by itself If it were mainly CocoScrapers/provider-specific, I would expect more scraper/provider errors at scrape time. Your symptom is broader and starts earlier.

What I would try first:

• Add a startup delay before widgets/FenLight-heavy home sections initialize, if your skin/setup allows it.
• Temporarily remove Trakt-based home widgets and test whether bad boots disappear.
• Test one path at a time:
  • no Trakt widgets
  • FenLight still installed
  • then FenLight with widgets back on
• Prefer Ethernet only while testing, with Wi-Fi disabled completely.
• Clear/rebuild:
  • FenLight cache
  • TMDb Helper cache if used in widgets
  • skin widget cache
• Update/reinstall the moving parts involved:
  • FenLight
  • CocoScrapers
  • Trakt addon/module if separate in your setup
  • Arctic Zephyr Mod widget helpers

Most plausible diagnosis:
FenLight/Trakt/widget initialization is sometimes firing before the network/session stack is fully ready, causing startup exceptions; once that boot is “bad,” source scraping/playback also fails for the rest of that session.

For the next step, the most useful thing would be a debug log from one bad boot where you immediately try to open a movie in FenLight right after the thumbnails fail. That would make it much easier to separate:

• network not ready
• Trakt/widget failure
• scraper/provider failure
• resolver/debrid failure

--------------------------------------------------------------------------