Kodi not starting since July update

Help and Support Raspberry Pi
1

Since the update on 29 July, Kodi no longer starts for me (it just shows the “sad face” screen).

This is on a Raspberry Pi 3.

The log includes:

2023-08-02 21:17:09.328 T:2202    debug <general>: CApplication::CreateGUI - trying to init gbm windowing system
2023-08-02 21:17:09.557 T:2214    debug <general>: Thread libinput start, auto delete: false
2023-08-02 21:17:09.558 T:2202     info <general>: RetroPlayer[RENDER]: Registering renderer factory for DMA
2023-08-02 21:17:09.558 T:2202     info <general>: RetroPlayer[RENDER]: Registering renderer factory for OpenGLES
2023-08-02 21:17:09.558 T:2202    error <general>: CDRMUtils::OpenDrm - no drm devices found: (No such file or directory)
2023-08-02 21:17:09.558 T:2202    error <general>: CWinSystemGbm::InitWindowSystem - failed to initialize Atomic DRM
2023-08-02 21:17:09.558 T:2202    error <general>: CDRMUtils::OpenDrm - no drm devices found: (No such file or directory)
2023-08-02 21:17:09.558 T:2202    error <general>: CWinSystemGbm::InitWindowSystem - failed to initialize Legacy DRM
2023-08-02 21:17:09.558 T:2202    error <general>: CDRMUtils::OpenDrm - no drm devices found: (No such file or directory)
2023-08-02 21:17:09.558 T:2202    error <general>: CWinSystemGbm::InitWindowSystem - failed to initialize off screen DRM
2023-08-02 21:17:09.558 T:2202    debug <general>: CApplication::CreateGUI - unable to init gbm windowing system

… so I wonder if it might be something DRM-related.

Full logs at https://paste.osmc.tv/egiposufig.

2

I would recommend to take a backup and do a clean reinstall. Issues that might had an impact

  1. Using full-upgrade instead of dist-upgrade
  2. Installation of X11
  3. Installation/Removal of pulseaudio
3

This will be the problem

I would suggest a reinstall of OSMC.

4

Well, that seems to have worked, thanks.

It’s a bit frustrating to have to go through and reconfigure everything though, and I’m a bit confused. I didn’t install X11 deliberately, and looking at the logs it looks like it had been hanging around for several years. Why would it suddenly have become a problem this week?

It seemed like the VC4 DRM device wasn’t being detected (no instances of vc4 in dmesg; /sys/class/drm empty). Doesn’t that point towards a devicetree problem or something else in kernel-land?

5

We have no other reports of a problem.

You installed pulseaudio
You also installed console-setup.
You overwrote the MESA libraries we supply

I could dive deeper in to your logs and find the exact cause of problem, but when you are manually installing packages like console-setup (that was not brought in as a dependency) you are creating problems.

6

To be clear, I wasn’t suggesting it was a general problem in OSMC. I’m more than prepared to believe
that something I did, at some point in the past, was the cause. I was just interested in what it might have been.

Anyway, I appreciate the answer might not be obvious and isn’t worth digging into. Thanks again for the help.