Rollout of 1.3.3 temporarily put on hold (Patreon)

I got three reports about a (rare?) issue with the 1.3.3 release: After update and if "auto-connect on startup" was configured, the server doesn't start up anymore due to what appears to be a corrupted printer profile that is attempted to be used for the connection.

If you experienced the same problems since initial release yesterday, please provide details, either here or even better in the ticket. Best would be your config.yaml and if it exists your _default.profile. I want to solve this ideally today and push a hotfix.