unable to reboot pi, shut down pi after updates on fluidd/moonraker/klipperscreen

[buikpijn]

What happened

After updating through the Fluidd webinterface klipperscreen, fluidd and klipper i am no longer able to perform the remaining update of the system ('error updating system') sudo apt update/upgrade perform fine through putty. But the update button keeps showing up for system. and the worse part is that it is unable to reboot or shutdown from the menu.

What did you expect to happen

I expect it to update the system through the Update button and be able to perform the upgrades.

How to reproduce

Click the system restart or system shutdown button. from the UI or through the webinterface

Additional information

The Host>shutdown feature for the Pi also doesn't work from the webinterface of Fluid and sudo reboot/shutdown work just fine through putty. Available update under the system update are

libpolkit-agent-1-0
libpolkit-backend-1-0
libpolkit-gobject-1-0
policykit-1
rpi-eeprom

I also noticed that in the passed updates where checked automatically, but it is now required to search for updates to see if any updates are present for the installed components.

[buikpijn]

I think i found something;

'Moonraker not authorized for PolicyKit action'

'Moonraker not authorized for PolicyKit action: [org.freedesktop.login1.reboot], The reboot API will be disabled'

How to correct this?

Tried reinstalling moonraker no luck.

Antyhing Linux based seems to turn against me sooner or later. I am slowly starting to hate the OS. It brings my incompetence to the surface, i normally like to cover that.. .

there was an error in the rights for moonraker to connect and there is an error it's FAQ.

https://docs.fluidd.xyz/faq

The ./moonraker/scripts/sudo-fix.sh is actually ./moonraker/scripts/sudo_fix.sh
and set-policy-rules.sh also needs to run to correct the issue. Updates work as intended too after correcting this. For the record; the updates broke it down. (again)

[Arksine]

FWIW, sudo_fix.sh can now be considered deprecated. That is one of the main goals of the changes that required policykit. For more information, see Arksine/moonraker#349

[Titaniser]

i had the same problem but with mainsailos.
ity a moonraker problem
i found a fix on https://moonraker.readthedocs.io/en/latest/installation/#policykit-permissions

[buikpijn]

To be honest, I discovered it was Moonraker after i installed mainsailos. (this OS gives a clear error on the first page of the control of the printer, unlike Fluidd).

In my experience every update involves the risk of loosing a working printer. All the tools need to coorporate perfectly, someone updates something somewhere in their policies or uses a different python version and you're screwed after simple updating all the items required to run your printer (in my case, klipper, Fluidd, moonraker, klipperscreen and the main distribution of the OS. It's not the first time that my printer broke down after an update. I admire all the hard work that has been put into this to make it work all together. I have this experience with everything running on a Pi /linux. Manuals that are outdated etc etc. It would be fair easy to re-install everything, but with an adxl345 with the required dependencies in the mix and a MCU that doesn't automatically updates (need to be done by hand through the SD card) it is easier said than done and should not be required after an update. All and all, it's the best running printer i've ever had, mainly thanks to Klipper and the additional packages. So i can't complain, but it's just not convenient to have to fix it after an update.