Once again, thank you for taking the time to report this @Marius!
This should now be fixed with 1.3.4.6:
Kindly let me know if this is the case on your end.
Thank you in advance.