There is already a discussion thread for this issue and I have posted a workaround there: Update to /e/ 4.1.1 provokes authentication error with Murena
There is already a discussion thread for this issue and I have posted a workaround there: Update to /e/ 4.1.1 provokes authentication error with Murena