OSMC Updater not working after running apt autoremove

So I updated my Vero4K by running apt dist-upgrade and after that I thought it was a good idea to run apt autoremove since I got prompted to do so. Now it seems that it wasn’t such a good idea after all…
When starting KODI it throws an error in the GUI regarding the OSMC-addon and the kodi.log shows the following information:
Can I repair the damage by re-installing some of the packages that have been purged?
If so, which ones and how?

Thanks in advance.

2020-11-27 14:07:07.383 T:3434090720 WARNING: CPythonInvoker(24): Script invoked without an addon. Adding all addon modules installed to python path as fallback. This behaviour will be removed in future version.
    2020-11-27 14:07:07.507 T:3434090720   ERROR: EXCEPTION Thrown (PythonToCppException) : -->Python callback/script returned the following error<--
                                             - NOTE: IGNORING THIS CAN LEAD TO MEMORY LEAKS!
                                            Error Type: <class 'socket.error'>
                                            Error Contents: [Errno 2] No such file or directory
                                            Traceback (most recent call last):
                                              File "/usr/share/kodi/addons/script.module.osmcsetting.updates/resources/lib/call_parent.py", line 18, in <module>
                                              File "/usr/lib/python2.7/socket.py", line 228, in meth
                                                return getattr(self._sock,name)(*args)
                                            error: [Errno 2] No such file or directory
                                            -->End of Python script error report<--

Start-Date: 2020-11-27  09:26:23
Commandline: /usr/bin/apt-real autoremove
Requested-By: osmc (1000)
Remove: libisccfg140:armhf (1:9.10.3.dfsg.P4-12.3+deb9u7), python3-distutils:armhf (3.7.3-1), gnupg-agent:armhf (2.2.12-1+deb10u1), python-imaging:armhf (4.0.0-4+deb9u2), libcdio13:armhf (0.83-4.3+b1), libicu57:armhf (57.1-6+deb9u4), libdevmapper-event1.02.1:armhf (2:1.02.155-3), libncurses5:armhf (6.1+20181013-2+deb10u2), python3.5:armhf (3.5.3-1+deb9u2), python3.5-minimal:armhf (3.5.3-1+deb9u2), libisc160:armhf (1:9.10.3.dfsg.P4-12.3+deb9u7), libntfs-3g871:armhf (1:2016.2.22AR.1+dfsg-1+deb9u1), libprocps6:armhf (2:3.3.12-3+deb9u1), armv7-libnfs-osmc:armhf (1.10.0-2), libperl5.24:armhf (5.24.1-3+deb9u7), g++-6:armhf (6.3.0-18+deb9u1), liblvm2app2.2:armhf (2.02.168-2), samba-common:armhf (2:4.9.5+dfsg-5+deb10u1), libgdbm3:armhf (1.8.3-14), liblwres141:armhf (1:9.10.3.dfsg.P4-12.3+deb9u7), python3-lib2to3:armhf (3.7.3-1), dh-python:armhf (3.20190308), libcryptsetup4:armhf (2:1.7.3-4), libwebpmux2:armhf (0.5.2-1), libdns162:armhf (1:9.10.3.dfsg.P4-12.3+deb9u7), libiso9660-8:armhf (0.83-4.3+b1), libevent-2.0-5:armhf (2.0.21-stable-3), libenca0:armhf (1.19-1+b1), libunistring0:armhf (0.9.6+really0.9.3-0.1), libisccc140:armhf (1:9.10.3.dfsg.P4-12.3+deb9u7), libpython3.5-stdlib:armhf (3.5.3-1+deb9u2), armv7-libass-osmc:armhf (0.13.6), libbind9-140:armhf (1:9.10.3.dfsg.P4-12.3+deb9u7), libpython3.5-minimal:armhf (3.5.3-1+deb9u2), libssl1.0.2:armhf (1.0.2u-1~deb9u2), libstdc++-6-dev:armhf (6.3.0-18+deb9u1)
End-Date: 2020-11-27  09:26:29

We need to see full logs to see what’s going on here

I turned on debug logging but after doing that the updater is working again. I haven’t been able to reproduce the issue.

I’m glad to hear the issue is now resolved.
Let’s keep an eye on things and if they crop up again, do let us know.