Could you please check the upgrade logs and maybe tell which package upgrade broke kodi for you?
$ grep ^Upgrade /var/log/apt/history.log Upgrade: libdatetime-timezone-perl:amd64 (1:2.09-1+2018g, 1:2.09-1+2018i), tzdata:amd64 (2018g-0+deb9u1, 2018i-0+deb9u1) Upgrade: flatpak:amd64 (0.8.9-0+deb9u1, 1.0.4-1~bpo9+1), bubblewrap:amd64 (0.1.7-1, 0.3.1-2~bpo9+1), flatpak-builder:amd64 (0.8.9-0+deb9u1, 1.0.1-1~bpo9+1), libostree-1-1:amd64 (2016.15-5, 2018.9.1-1~bpo9+1), xdg-desktop-portal:amd64 (0.5-1, 1.0.3-1~bpo9+1) Upgrade: libgles2-mesa:amd64 (13.0.6-1+b2, 18.2.6-1~bpo9+1), libdrm-nouveau2:amd64 (2.4.74-1, 2.4.95-1~bpo9+1), libdrm-nouveau2:i386 (2.4.74-1, 2.4.95-1~bpo9+1), libegl1-mesa-dev:amd64 (13.0.6-1+b2, 18.2.6-1~bpo9+1), libglapi-mesa:amd64 (13.0.6-1+b2, 18.2.6-1~bpo9+1), libglapi-mesa:i386 (13.0.6-1+b2, 18.2.6-1~bpo9+1), mesa-common-dev:amd64 (13.0.6-1+b2, 18.2.6-1~bpo9+1), libegl1-mesa:amd64 (13.0.6-1+b2, 18.2.6-1~bpo9+1), libgbm1:amd64 (13.0.6-1+b2, 18.2.6-1~bpo9+1), libwayland-client0:amd64 (1.12.0-1, 1.16.0-1~bpo9+1), libwayland-bin:amd64 (1.12.0-1, 1.16.0-1~bpo9+1), libdrm-amdgpu1:amd64 (2.4.74-1, 2.4.95-1~bpo9+1), libdrm-amdgpu1:i386 (2.4.74-1, 2.4.95-1~bpo9+1), libwayland-dev:amd64 (1.12.0-1, 1.16.0-1~bpo9+1), libwayland-egl1-mesa:amd64 (13.0.6-1+b2, 18.2.6-1~bpo9+1), libgles2-mesa-dev:amd64 (13.0.6-1+b2, 18.2.6-1~bpo9+1), libdrm2:amd64 (2.4.74-1, 2.4.95-1~bpo9+1), libdrm2:i386 (2.4.74-1, 2.4.95-1~bpo9+1), libgl1-mesa-dev:amd64 (13.0.6-1+b2, 18.2.6-1~bpo9+1), libgl1-mesa-glx:amd64 (13.0.6-1+b2, 18.2.6-1~bpo9+1), libgl1-mesa-glx:i386 (13.0.6-1+b2, 18.2.6-1~bpo9+1), libdrm-intel1:amd64 (2.4.74-1, 2.4.95-1~bpo9+1), libdrm-intel1:i386 (2.4.74-1, 2.4.95-1~bpo9+1), libdrm-radeon1:amd64 (2.4.74-1, 2.4.95-1~bpo9+1), libdrm-radeon1:i386 (2.4.74-1, 2.4.95-1~bpo9+1), libdrm-dev:amd64 (2.4.74-1, 2.4.95-1~bpo9+1), libwayland-server0:amd64 (1.12.0-1, 1.16.0-1~bpo9+1), libwayland-cursor0:amd64 (1.12.0-1, 1.16.0-1~bpo9+1) Upgrade: fdroidserver:amd64 (0.7.0-2, 1.0.6-1~bpo9+1) Upgrade: vlc-bin:amd64 (3.0.3-1-0+deb9u1, 3.0.6-0+deb9u1), vlc-plugin-video-output:amd64 (3.0.3-1-0+deb9u1, 3.0.6-0+deb9u1), vlc-plugin-samba:amd64 (3.0.3-1-0+deb9u1, 3.0.6-0+deb9u1), vlc-plugin-qt:amd64 (3.0.3-1-0+deb9u1, 3.0.6-0+deb9u1), libsystemd0:amd64 (232-25+deb9u6, 232-25+deb9u8), libzmq5:amd64 (4.2.1-4, 4.2.1-4+deb9u1), vlc-plugin-skins2:amd64 (3.0.3-1-0+deb9u1, 3.0.6-0+deb9u1), vlc-plugin-visualization:amd64 (3.0.3-1-0+deb9u1, 3.0.6-0+deb9u1), vlc-l10n:amd64 (3.0.3-1-0+deb9u1, 3.0.6-0+deb9u1), vlc-plugin-notify:amd64 (3.0.3-1-0+deb9u1, 3.0.6-0+deb9u1), libvlc5:amd64 (3.0.3-1-0+deb9u1, 3.0.6-0+deb9u1), udev:amd64 (232-25+deb9u6, 232-25+deb9u8), libvlccore9:amd64 (3.0.3-1-0+deb9u1, 3.0.6-0+deb9u1), libudev1:amd64 (232-25+deb9u6, 232-25+deb9u8), libvlc-bin:amd64 (3.0.3-1-0+deb9u1, 3.0.6-0+deb9u1), libudev-dev:amd64 (232-25+deb9u6, 232-25+deb9u8), systemd-sysv:amd64 (232-25+deb9u6, 232-25+deb9u8), vlc:amd64 (3.0.3-1-0+deb9u1, 3.0.6-0+deb9u1), libpam-systemd:amd64 (232-25+deb9u6, 232-25+deb9u8), vlc-data:amd64 (3.0.3-1-0+deb9u1, 3.0.6-0+deb9u1), systemd:amd64 (232-25+deb9u6, 232-25+deb9u8), vlc-plugin-video-splitter:amd64 (3.0.3-1-0+deb9u1, 3.0.6-0+deb9u1), vlc-plugin-base:amd64 (3.0.3-1-0+deb9u1, 3.0.6-0+deb9u1)I believe that last one (with vlc etc) was executed *after* I observed the problem. The libdrm-nouveau2 and related seem suspect, especially coming from backports.
signature.asc
Description: PGP signature
