As I wrote in another thread I just uninstalled the SMB-Server.
Then after a reboot I get a popup telling me update failed and I should look at the logs:
We need apt logs. grab-logs -a
Do not use apt-get upgrade. If you are upgrading via command line always use apt-get dist-upgrade.
Also you purged the smb-app-osmc package but you must also purge the samba package to completely remove samba.
1 Like
Thanks for mentioning (again) to not using apt-get upgrade. Though it’s been a while I did that, only recently read that we should not do that, but doing updates over the GUI for almost a year now anyway.
But I definately did not manually purge smb, I did use the GUI to uninstall it! OSMC must be doing it wrong then.
EDIT:
Though I really do not want to remove Samba at all. As soon as there is a fix for the ‘freeze’ bug I want to install it all again.
PS: what about the error in the logs, should i be worried about this?
ERROR: EXCEPTION Thrown (PythonToCppException) : -->Python callback/script returned the following error<-- - NOTE: IGNORING THIS CAN LEAD TO MEMORY LEAKS!
That’s not an error per se
It means a data structure was referenced as a void pointer and passed to Python because it doesn’t have a compatible data type. The Python code is now responsible for freeing()
Ok, I put my trust in python then 