Sad face loop on rpi since Sept upgrade

After upgrding my rpi yesterday to Sept update (bullseye) getting continuous sad face reboot loop. OS overal is still working, just Kodi impacted. Tried reinstalling mediacenter and issue continues, albetit with cleaner looking logs. grab-logs -A found here: https://paste.osmc.tv/bunewopuzo

Let’s test with Kodi default settings. Enter the following commands with an SSH connection.

systemctl stop mediacenter
mv ~/.kodi ~/kodi.bak
systemctl start mediacenter

If needed you can restore:

systemctl stop mediacenter
mv ~/.kodi ~/kodi.bk2
mv ~/kodi.bak ~/.kodi
systemctl start mediacenter

If your original setup was restored as expected and you want get rid of the unneeded clean install you can delete that with the following command.

rm -r ~/kodi.bk2

Thanks for taking the time to review, Tom.

I gave a try with your instructions to rebuild the profile. Unfortunately still same end result. Latest logs now here: https://paste.osmc.tv/zejikimoti

Wonder if the python error is the cause?

Sep 21 20:49:00 pi3 mediacenter[3584]: Cannot connect to server socket err = No such file or directory
Sep 21 20:49:00 pi3 mediacenter[3584]: Cannot connect to server request channel
Sep 21 20:49:00 pi3 mediacenter[3584]: jack server is not running or cannot be started
Sep 21 20:49:00 pi3 mediacenter[3584]: JackShmReadWritePtr::~JackShmReadWritePtr - Init not done for -1, skipping unlock
Sep 21 20:49:00 pi3 mediacenter[3584]: JackShmReadWritePtr::~JackShmReadWritePtr - Init not done for -1, skipping unlock
Sep 21 20:49:12 pi3 mediacenter[3584]: Python path configuration:
Sep 21 20:49:12 pi3 mediacenter[3584]:   PYTHONHOME = (not set)
Sep 21 20:49:12 pi3 mediacenter[3584]:   PYTHONPATH = (not set)
Sep 21 20:49:12 pi3 mediacenter[3584]:   program name = 'python3'
Sep 21 20:49:12 pi3 mediacenter[3584]:   isolated = 0
Sep 21 20:49:12 pi3 mediacenter[3584]:   environment = 1
Sep 21 20:49:12 pi3 mediacenter[3584]:   user site = 1
Sep 21 20:49:12 pi3 kernel: Unhandled prefetch abort: unknown 1 (0x001) at 0x0000000a
Sep 21 20:49:12 pi3 mediacenter[3584]:   import site = 1
Sep 21 20:49:12 pi3 mediacenter[3584]:   sys._base_executable = '/usr/bin/python3'
Sep 21 20:49:12 pi3 mediacenter[3584]:   sys.base_prefix = '/usr'
Sep 21 20:49:12 pi3 mediacenter[3584]:   sys.base_exec_prefix = '/usr'
Sep 21 20:49:12 pi3 mediacenter[3584]:   sys.platlibdir = 'lib'
Sep 21 20:49:12 pi3 mediacenter[3584]:   sys.executable = '/usr/bin/python3'
Sep 21 20:49:12 pi3 mediacenter[3584]:   sys.prefix = '/usr'
Sep 21 20:49:12 pi3 mediacenter[3584]:   sys.exec_prefix = '/usr'
Sep 21 20:49:12 pi3 mediacenter[3584]:   sys.path = [
Sep 21 20:49:12 pi3 mediacenter[3584]:     '/usr/lib/python39.zip',
Sep 21 20:49:12 pi3 mediacenter[3584]:     '/usr/lib/python3.9',
Sep 21 20:49:12 pi3 mediacenter[3584]:     '/usr/lib/python3.9/lib-dynload',
Sep 21 20:49:12 pi3 mediacenter[3584]:   ]
Sep 21 20:49:12 pi3 mediacenter[3584]: Fatal Python error: init_fs_encoding: failed to get the Python codec of the filesystem encoding
Sep 21 20:49:12 pi3 mediacenter[3584]: Python runtime state: core initialized
Sep 21 20:49:12 pi3 mediacenter[3584]: ValueError: source code string cannot contain null bytes
Sep 21 20:49:12 pi3 mediacenter[3584]: Current thread 0x66fe7100 (most recent call first):
Sep 21 20:49:12 pi3 mediacenter[3584]: <no Python frame>
Sep 21 20:49:12 pi3 mediacenter[3567]: /usr/bin/mediacenter: line 149:  3583 Bus error               sudo -u osmc LIRC_SOCKET_PATH=/var/run/lirc/lircd $KODI --standalone -fs
Sep 21 20:49:12 pi3 mediacenter[3567]: Kodi exited with return code 135 after 0 hours, 0 minutes and 19 seconds

Thanks in advance for further assistance!
-Gary

Not sure where that jack server errors are coming from. Do you have a special audio setup?
As the usual suggestion for the Pi easiest put a new install on a second SD Card and see if that works. If all good copy over your .kodi folder to see if it still works.

The only audio changes I’ve made over the years was to install/enable bluetooth audio.

I’m thinking though the python errors might be the true underlying cause. (I THINK the system handles the jack scenario)
Ive had this OSMC rig going for a couple years at least now. And had no major issues with various updates along the way.
I wonder though if the default python change in bullseye ties to the errors Im seeing?

I do have a couple other services on this pi (still working) which I would hate to have to reinstall/configure. Any other ideas or suggestions other than to start from scratch?