Moonraker(?) update broke a python link

[viscid pasture]

This is odd -- I don't need assistance, as I resolved my issue, but posting this in case others see the same thing.

TL;DR - Did some upgrades, moonraker wouldn't start because it couldn't find python; did a fix-broken-install for python3, and that resolved my issue.

Long version:

I did a fresh install of MainSailOS 1.0.164-bit Bullseye on a Raspberry Pi 3B+ three days ago. All went well. Yesterday I used Update Manager within MainSail to upgrade moonraker (to v0.7.1-826-g1bad68c) and KlipperScreen (to v0.3.1-17-g059f1a8) shortly after that I noticed that KlipperScreen's display was constantly restarting. Poked around in the logs (didn't save whatever it was with KlipperScreen, and it didn't save old logs) but it pointed me to the moonraker log, and the first indication of problem was this:

    raise config.error(
confighelper.ConfigError: Invalid path for option `env` in section [klipper]: Path `/home/pi/klippy-env/bin/python` does not exist```

I tracked it back to this broken link:
```pi@klipcore:/usr/bin $ file python3
python3: broken symbolic link to python3.9```

I fixed that with ```sudo apt --fix-broken install``` which ended up re-installing `python3.9-minimal`

Anyway.  Just wanted to put this out there.  Moonraker log for the failure period attached.

[tawny escarp]

thx for the report. your log looks like it has an issue with teh klipperscreen update.

utils.ServerError: PACKAGE_FAILED_TO_INSTALL: Error while installing package: installed python3-numpy package pre-removal script subprocess returned error exit status 127
2023-01-29 21:06:19,973 [shell_command.py:_create_subprocess()] - shell_command: Command (/home/pi/.KlipperScreen-env/bin/pip install -r /home/pi/KlipperScreen/scripts/KlipperScreen-requirements.txt) failed

so maybe its more an klipperscreen update issue than a moonraker update issue.

[viscid pasture]

Yeah -- I was thinking KlipperScreen probably drove the issue -- because I did notice it attempting to update a lot of stuff as the window scrolled by. Sadly the KlipperScreen log was restarted, so I don't have evidence. I looked through the KlipperScreen commits yesterday, and while there were changes in install script and dependancies, nothing jumped out. https://github.com/jordanruthe/KlipperScreen

[lucid ocean]

Thanks for posting this like an idiot as I am reading on here clicked update and ended up in the same place. Glad there was a fix.

[patent tapir]

Had same issue after updating. This fixed it for me as well. Thanks @viscid pasture