[@enaijo Participant 10 years, 5 months ago]

Patch #8, as mentioned from danbp, solved the problem for me.

[@enaijo Participant 10 years, 5 months ago]

For me, the problem is introduced with 2.2.2, not solved …