From: nospam.Travis.Mehrer@f303.n134.z1.fidonet.org   
      
    g0> I don't know if this would be a factor in your case, but in the past I   
    g0> have struggled having multiple Python installations in the same Linux   
    g0> VMware, and I have completed destroyed installations by trying to   
    g0> install different versions of Python on top of or to replace what the OS   
    g0> ships with.   
    g0>   
    g0> I wouldn't consider myself an expert in that area though, but I have   
    g0> found it to be tricky to touch Python's default installations without   
    g0> blowing up things badly enough that I end up completely reinstalling   
    g0> Ubuntu.   
      
   Thank you again, for your reply g00r00! So, FINALLY after a little pulling out   
   of hair, I managed to figure out what is going on.   
      
   After a new install on the same Pi started out working, and then failed after I   
   started migrating my menus to the new board; it struck me.   
      
   In my prelogin menu I have a simple python2 script running. And it was the   
   mixture of Python2 and 3 that was breaking things for me. After fixing a text   
   file my script was importing (had some sort of broken UTF-8 enconding in it) I   
   was able to run this script as Python3 and then continue to use Python 3.   
      
   TL;DR: Mixing Python2 and Python3 in Mystic (RPi OS Bullseye) can break things.   
   Lesson learned, now I can finally move on with Python3 and Mystic.   
      
   blade   
      
   ... User Error: Replace user and hit any key to continue...   
      
   --- SoupGate-Win32 v1.05   
    * Origin: you cannot sedate... all the things you hate (1:229/2)